Problems with custom tiles
I am adding a custom tile using a static map image file on my pc and loading with AddTileSource & AddLayer. The file loads but not only is it not scaled or positioned correctly, but it also gets tiled across the whole background VE image? The image is correctly georeferenced in the bounds clause and is based in the northern hemisphere - in the UK. I've tried bmp, png and gif formats - but same result.
Is there a minimum bit map image size or lat/long precision issue that might cause this?
[511 byte] By [
TomNash] at [2007-12-26]
Are you using Map cruncher to produce the tiles?
I haven't had too many issues with layers, ther are others on the forum that have done quite a bit with them.
Maybe if you have a link or some basic example of the code that causes the problem we may be able to help.
John.
The Bounds clause is not for georeferencing the tiles. It is for describing the extent of where you have data.
Each tile must be for the geographic extent of just one tile. In the request string, the %4 parameter is replaced with the quadcode for the tile being requested. If you don't have the %4 parameter in your request string, you will request the same image for each tile. You can use MapCruncher to break up source imagery to individual tiles.
OK, thanks for the responses. No I was not using Mapcruncher - I've misinterpreted how the tiling works. I'll do some more homework!
The SDK has a couple of examples and a conceptual topic on using the tiles. Let me know if that information isn't complete enough or is confusing.
Thanks,
Caleb
Caleb,
I come from the world of GIS and raster registration - so I was expecting too much from raw VE. Perhaps the SDK text is a bit confusing. Getting my head round MapCruncher now, using 2.1.1, it seems very flakey? Do I need an update. It saves the project as a.yum file, but it crashes on reload and will not browse.
Tom
Hi Tom,
I'm Jeremy, from the MapCruncher team. Can you describe in a little more detail the problem you're having? The .yum file is basically a MapCruncher configuration file; it's not supposed to be directly browseable in a web browser. After you select pushpins with MapCruncher, go to the Render tab and it'll emit both map tiles and a sample .HTML file that you can view in the browser.
Cheers,
Jeremy
Jeremy,
I'm still experiencing problems with Mapcruncher, running under XP and dot net v2 and am unable to produce any rendered tiles. Three immediate problems:
The Maximum (closest) zoom box which should be displayed on the render page (as per tutorial) is not visible
On running "Start estimate" - message appears 'Not all layers could be opened. Please ensure all source maps can be locked and then return to this tab to render' - the source file is a single bitmap file on my local PC.
On saving the mashup, (just after defining the referencing points but before generating render), and then attempting to reload the saved mashup - gives - 'unhandled exception .... Value of '-2147483633' is not valid for value' - examining contents of .yum file indicates a value of -214748363 against the sourcemaprenderoptions maxzoom parameter.
Any ideas what I'm doing wrong?
Tom
Can you try manually removing the "MaxZoom" parameter from your .yum file (just edit it out with Notepad or another text editor) and see if that works better? Not sure how your .yum file got into that state -- odd.
We have a new beta coming out soon that should be more robust, generally.
Tried that - no difference. Here is the message I get when I press start estimate -
Skipping layer New Layer: System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MSR.CVE.BackMaker.RenderProgressPanel.ConstructRenderList(Layer layer, Dictionary`2 credits, Boolean& allLayersOpened, Int32& tileSanityCount, List`1& boundsList)
at MSR.CVE.BackMaker.RenderProgressPanel.ConstructRenderListThread()
How can I email you the yum file and offending raster map?
Tom
Sure, if they're relatively small (1-2MB) please mail me the files, cruncher at microsoft dot com. Thanks!
Jeremy,
Did you get my email?
Tom
Hi Tom,
Thanks for the bug report. Based on the files you sent we found a MapCruncher bug that was causing the behavior you saw. We just released v3.02 which has a fix.
Jeremy
Jeremy & Jon,
Great v3.02 sorted it out - thanks.
Tom
