[osmosis-dev] Problem creating pbf data with osmosis 0.39

[Michael Prinzing]

Hello,

there seems to be a problem with the conversion of xml data to pbf in
osmosis 0.39 that did not exist in version 0.38.

I've tried to convert a file containing data from strm2osm (converted
to osm 0.6 before) by calling osmosis 0.39 with

osmosis --read-xml file="strm.osm" --write-pbf omitmetadata=true file="strm_039.osm.pbf"


The beginning of the original xml data before conversion was:

-----------------------------------------
<?xml version='1.0' encoding='UTF-8'?>
<osm version="0.6" generator="Osmosis 0.35">
  <node id="0000004406" version="1" timestamp="2011-09-11T03:07:14Z" lat="51.6325833" lon="6.2575833"/>
  <node id="0000004407" version="1" timestamp="2011-09-11T03:07:14Z" lat="51.6334167" lon="6.2584167"/>
-----------------------------------------

Please note there is no bounding box and the timestamps are from the
creation of the data.



If I am converting the resulting pbf file back to xml, the new xml file
begins like this:

-----------------------------------------
<?xml version='1.0' encoding='UTF-8'?>
<osm version="0.6" generator="Osmosis 0.39">
  <bound box="0.00000,0.00000,0.00000,0.00000" origin="0.39"/>
  <node id="4406" version="-1" timestamp="1969-12-31T23:59:59Z" changeset="-1" lat="51.6325833" lon="6.2575833"/>
  <node id="4407" version="-1" timestamp="1969-12-31T23:59:59Z" changeset="-1" lat="51.6334167" lon="6.2584167"/>
-----------------------------------------

Now, there is an "empty" bounding box, and the timestamps are far in
the past (looks like an integer of -1 converted to a timestamp to me).



If I am doing exactly the same, but with osmosis 0.38, everything works
fine. The resulting xml file begins like this:

-----------------------------------------
<?xml version='1.0' encoding='UTF-8'?>
<osm version="0.6" generator="Osmosis 0.38">
  <node id="4406" version="-1" timestamp="2011-09-20T19:48:24Z" changeset="-1" lat="51.6325833" lon="6.2575833"/>
  <node id="4407" version="-1" timestamp="2011-09-20T19:48:24Z" changeset="-1" lat="51.6334167" lon="6.2584167"/>
-----------------------------------------

No bounding box, and the timestamps are from now.


The pbf file created by osmosis 0.39 is always 64 bytes larger than the
one created with osmosis 0.38 from the same data.



The problem with the empty bounding box is with the conversion
xml->pbf, because if I am trying to process the pbf file with the
splitter from mkgmap, if says

-----------------------------------------
Processing srtm_039.osm.pbf
Bounding box 0.0 0.0 0.0 0.0
in 1 file
Time: Sun Sep 20 22:25:38 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. This does not happen if the pbf data
was created with osmosis 0.38.



I've also tried to convert data saved from josm (with a reasonable
bounding box set) to pbf and back to xml. After doing this with osmosis
0.39, there again is an empty bounding box in the pbf data as well as
in the new xml file. Here again the pbf file created with osmosis 0.39
is exactly 64 bytes larger than a file created with version 0.38 from
the same data.


I am running the binary distribution of osmosis with Java 1.7 and
Windows XP, but there is at least one report on mkgmap-dev
(http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q3/012358.html)
confirming this also happens with Java 1.6 and Debian.


Thank you,

Michael