[QUOTE=gnuite;36919]The "latitude" and "longitude" that are used in the directory hierarchy are not measured in degrees - it is measured in tile numbers, where 0, 0 represents the "upper-left corner" of the world.

In the mercator projection, the world is a square. Maemo Mapper divides the world into pixels, each pixel of which represents a pixel at zoom level 0. The world is 2^25 (33554432) pixels wide and high.

"Tiles" are 256x256 wide, so at zoom level 0, the world is 2^17 (131072) tiles wide and high. You're near the prime meridian.......QUOTE]

Right, thanks for that Gniute - does that 'handle' translate as Geo-Knight, if so you deserve a place at the round table!

I've done some more research ref MapCruncher.

It turns out that the xml it produces to point the mash up/preview to an html page has everything needed to put the tiles into the correct folders for MM to read them. It uses a QuadTree method to reference directly over the VE tiles for the area of your 'mashed' map (the one you begged/borrowed/stole then scanned or downloaded!) For example, the file starts thus:

"<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<CrunchUp xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" Version="1.6" RenderDate="23/02/2007 15:41:07">
<BoundsList>
<Bounds zoom="16" X0="32534" Y0="21789" X1="32562" Y1="21817" /> the bounding box of your mash at max (specified in render process) in VE X, Y tile position.
</BoundsList>
<CrunchedFileIdentifier>
<SearchFodder>MSRMapCruncherOutputGUID</SearchFodder>
</CrunchedFileIdentifier>
<MapCruncherAppVersion version="3.0.2">
<SearchFodder>MSRMapCruncherOutputGUIDVersionDAC </SearchFodder>
</MapCruncherAppVersion>
<LayerList>
<Layer DisplayName="New Layer">
<TileNamingScheme Type="VE" FilePath="" FilePrefix="Layer_NewLayer" FileSuffix=".png" />[I]path to you local mashed tiles[/I]
<DefaultView lat="51.4712408228935" lon="-1.20940700487637" zoom="12" />
<SourceMapRecordList>
<SourceMapRecord DisplayName="Test" MaxZoom="16">
<SourceMapInfo>
<MapFileURL url="" />
<MapHomePage url="" />
<MapDescription />
</SourceMapInfo>
<MapRectangle>
<LatLon lat="51.4258096996177" lon="-1.28220415252848" />Bounding box in deg.dec
<LatLon lat="51.5166719461693" lon="-1.13660985722426" />
</MapRectangle>
</SourceMapRecord>
</SourceMapRecordList>
<RangeDescriptors>
<RangeDescriptor TileX="0" TileY="0" Zoom="1" QuadTreeLocation="0">
<SearchFodder>MSRMapCruncherOutputGUIDA</SearchFodder> Reference for the view at zoom 1, ie in MM = folder '0'/'0'/0.png
</RangeDescriptor>
<RangeDescriptor TileX="1" TileY="1" Zoom="2" QuadTreeLocation="03">
<SearchFodder>MSRMapCruncherOutputGUIDAD</SearchFodder>
</RangeDescriptor>
<RangeDescriptor TileX="3" TileY="2" Zoom="3" QuadTreeLocation="031">
<SearchFodder>MSRMapCruncherOutputGUIDADB</SearchFodder>
</RangeDescriptor>
<RangeDescriptor TileX="7" TileY="5" Zoom="4" QuadTreeLocation="0313">
<SearchFodder>MSRMapCruncherOutputGUIDADBD</SearchFodder>
</RangeDescriptor>
<RangeDescriptor TileX="15" TileY="10" Zoom="5" QuadTreeLocation="03131">
<SearchFodder>MSRMapCruncherOutputGUIDADBDB</SearchFodder>
</RangeDescriptor>
<RangeDescriptor TileX="31" TileY="21" Zoom="6" QuadTreeLocation="031313">
<SearchFodder>MSRMapCruncherOutputGUIDADBDBD</SearchFodder>
</RangeDescriptor>
<RangeDescriptor TileX="63" TileY="42" Zoom="7" QuadTreeLocation="0313131">
equates to MM as folder /'7'/'63'/42.png
and so on to zoom level 17

So now all that needs to be done is write a script to rename the QuadTree files and put them in the correct, MM expected, folders.

I will have to get studying......

kempja