logo separator

[mkgmap-dev] Splitter doesn't process pbf data created with osmosis 0.39

From Michael Prinzing mipri at gmx.net on Mon Sep 19 16:53:03 BST 2011

Hello,

there seems to be a problem with the latest splitter and data in pbf
format if it was created with osmosis 0.39.

When I am converting a xml file to pbf by callig osmosis 0.39 just with
--read-xml and --write pbf parameters, the splitter (called without
parameters) says:

------------------------------------------------
Processing data_039.osm.pbf
Bounding box 0.0 0.0 0.0 0.0
in 1 file
Time: Sun Sep 18 15:45:48 CEST 2011
Exact map coverage is (0.0,0.0) to (2.1457672119140625E-5,2.1457672119140625E-5)
Trimmed and rounded map coverage is (0.0,0.0) to (2.1457672119140625E-5,2.1457672119140625E-5)
Splitting nodes into areas containing a maximum of 1.600.000 nodes each...
0 areas:
------------------------------------------------

The output is empty, of course.


When I am doing exactly the same but with osmosis 0.38, the splitter
doesn't print a Bounding Box, the map coverage is right, and 
everything works fine:

------------------------------------------------
Processing data_038.osm.pbf
in 1 file
Time: Sun Sep 18 15:45:32 CEST 2011
Exact map coverage is (48.318986892700195,8.87244701385498) to (48.47125053405762,9.23452377319336)
Trimmed and rounded map coverage is (48.2958984375,8.8330078125) to (48.4716796875,9.2724609375)
Splitting nodes into areas containing a maximum of 1.600.000 nodes each...
Area (48.2958984375,8.8330078125) to (48.4716796875,9.2724609375) contains 6.073 nodes. DONE!
1 areas:
Area 63240001 covers (0x225800,0x64800) to (0x227800,0x69800)
------------------------------------------------

The file osmosis 0.39 produces is always 64 bytes larger than the one
from osmosis 0.38, independent of the input data.

Is this an issue with osmosis 0.39 or with the splitter?


Thanks,

Michael







More information about the mkgmap-dev mailing list