[mkgmap-dev] Tile splitter and merged maps?

Wed Apr 27 08:14:14 BST 2011

Hi Marko, Charlie,

>> So looks like the tile splitter took into account only the first part of the merged .osm map.
>> Am I doing something wrong here? Or is this an incompatibility or a possible problem with the tile splitter?

> Would you use to use the --mixed option to splitter or does osmosis 
> automatically sort files when it merges them?

Not sure whether osmosis sorts automatically. Now, I did a sort run before:

$ ./osmosis --rx DE_FI_USW.osm  --sort --wb DE_FI_USW.osm.pbf omitmetadata=true

then tried splitting again.

From Marko's mail: 

> Side note: why not --wb DE_FI_USW.osm.pbf? Splitter can process osm.pbf.

Thanks, I didn't know that. I had read posts about older versions of splitter that couldn't deal with pbf.

> What kind of coordinates do you see in the areas.list? Could it be that 
> splitter is misinterpreting the bounding box?

Areas only cover Finland :-(
http://maps.google.com/maps?q=roettsches.de%2Fdominik%2Fareas.kml

In the splitter output [1], the following bounding box is printed:
"Bounding box 19.02427 59.287829999 31.600889999000003 70.09959"
how to interpret these values to check whether the map bounding box is right? If I use 19.02427 59.287829999 in Google Maps, it shows a place in the Arabian Sea, the other coordinate is somewhere in Pakistan...

Can I tell the splitter to ignore the map's bounding box altogether and find its own? Any other ideas how to make it take into account the whole merged map?

Dominik

[1] Splitter output:

$ java -Xmx5000M -jar ../splitter.jar --mapid=63240345 --max-nodes=1000000 --write-kml=areas.kml ../DE_FI_USW.osm
.pbf
cache=
description=
geonames-file=
legacy-mode=false
mapid=63240345
max-areas=255
max-nodes=1000000
max-threads=8 (auto)
mixed=false
no-trim=false
output-dir=
overlap=2000
resolution=13
split-file=
status-freq=120
write-kml=areas.kml
Elapsed time: 0s   Memory: Current 119MB (2MB used, 117MB free) Max 4444MB  
Time started: Wed Apr 27 08:58:57 CEST 2011
Map is being split for resolution 13:
 - area boundaries are aligned to 0x800 map units
 - areas are multiples of 0x1000 map units wide and high
Processing ../DE_FI_USW.osm.pbf
Bounding box 19.02427 59.287829999 31.600889999000003 70.09959