Using a server with 64GB ram I was able split the latest planet dump with Splitter in about an hour. In the results however are some weird tiles: The first tile is 644 MB gzip compressed, clearly not something that Mkgmap is going to like much: 63240001: -4196352,-10010624 to 598016,-4046848 # : -90.043945,-214.804688 to 12.832031,-86.835938 There are also quite some tiles that go outside the expected -180 to +180 and -90 to +90 degree bounding box, like: 63240002: -4196352,-4046848 to -1943552,-2555904 # : -90.043945,-86.835938 to -41.704102,-54.843750 63240006: 598016,-10010624 to 1796096,-6334464 # : 12.832031,-214.804688 to 38.540039,-135.922852
Hi On Tue, Mar 24, 2009 at 09:56:29AM +0100, Lambertus wrote:
Using a server with 64GB ram I was able split the latest planet dump with Splitter in about an hour. In the results however are some weird tiles:
Wow!
The first tile is 644 MB gzip compressed, clearly not something that Mkgmap is going to like much:
I think we need to limit the areas to 85deg and then make sure they do not wrap around, and then limit with a max size too. On the other hand I don't really understand how out of range values can occur, unless they exist in the planet file. Perhaps they do... ..Steve
I created a contour map using the following lines in mkgmap java -Xmx512m -jar mkgmap.jar --tdbfile --gmapsupp --latin1 --country-abbr=PHI --country-name=PHILIPPINES --family-id=439 --product-id=478 --overview-mapname=30000001 --mapname=20000001 --gmapsupp --transparent --description="Contour Elevation" *.osm.gz To view it in mapsource I need to make a registry, I found a sample registry which I then modified like this: REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Garmin\MapSource\Families\30000001] "ID"=hex:7f,02 [HKEY_LOCAL_MACHINE\SOFTWARE\Garmin\MapSource\Families\30000001\2a6] "LOC"="C:\\CONTOUR\\" "BMAP"="C:\\CONTOUR\\30000001.img" "TDB"="C:\\CONTOUR\\30000001.tdb" Looking at the sample registry here: http://wiki.openstreetmap.org/wiki/OSM_Map_On_MapSource#Tech_stuff It looks different. And I don't what the hex here means: [HKEY_LOCAL_MACHINE\SOFTWARE\Garmin\MapSource\Families\30000001] "ID"=hex:7f,02 [HKEY_LOCAL_MACHINE\SOFTWARE\Garmin\MapSource\Families\30000001\2a6] What would be the minimum registry entries and what values should I place? -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------
Is there a size-limit, what splitter can handle? I created an OSM file with SRTM2OSM for an extended Germany in a rather high resolution. The resulting OSM-file is uncompressed more than 26GB large. I start splitter with 6GB memory. It is quite some time buzy, but in the end I get only a single, very small tile, or the whole area as one big tyle. Gruss Torsten
participants (4)
-
Lambertus -
Maning Sambale -
Steve Ratcliffe -
Torsten Leistikow