[OSM-dev] [OSM-talk] osmosis Problem with bounding-polygon and v0.6?

Marco Lechner - FOSSGIS e.V. marco.lechner at fossgis.de
Fri Apr 24 13:03:12 BST 2009


An interesting additional behavior:

If I use
bzcat ../planet-090421.osm.bz2 | ./bin/osmosis --read-xml-0.6 file=-
--bounding-polygon-0.6 file=../aoi.pff --write-xml-0.6
file=../aoi_2009-04-21_v06.osm
instead of
./bin/osmosis --read-xml-0.6 file=path/planet-090421.osm.bz2
compressionMethod=bzip2 --bounding-polygon-0.6 file=path/aoi.pff
--write-xml-0.6 file=path/aoi_2009-04-21_v06.osm
it seems to work (still running).
Although using bzcat has a better performance, the build-in function
should work, shouldn't it? But there seems to be a bug. Is this a bug?
Can anybody reproduce this?

Marco

Marco Lechner - FOSSGIS e.V. schrieb:
> Hi,
>
> I checked the md5sum before processing anything - and it was correct.
> Also the *.bz2 unpacks without problems (of course just piping using
> bzcat). Therefore I assume the planetfile is o.k. (besides the errors
> posted in thread "osmosis cutting the planet").
>
> I just want to find out what causes my error:
>
> SCHWERWIEGEND: Thread for task 1-read-xml-0.6 failed
> com.bretth.osmosis.core.OsmosisRuntimeException: Unable to parse xml
> file path/planet-090421.osm.bz2.  publicId=(null), systemId=(null),
> lineNumber=6663, columnNumber=34.
>     at com.bretth.osmosis.core.xml.v0_6.XmlReader.run(XmlReader.java:114)
>     at java.lang.Thread.run(Thread.java:636)
> Caused by: org.xml.sax.SAXParseException: XML document structures must
> start and end within the same entity.
>
> Using bzcat ./planet-090421.osm.bz2 |less -N to go to the referenced
> line (6663) I get:
>
>    6661   <node id="102226" lat="60.2182655" lon="9.6330175"
> timestamp="2008-10-17T14:33:31Z" version="2" changeset="406212"
> user="crazykangaroo" uid="71766"/>
>    6662   <node id="102227" lat="60.2174492" lon="9.6330175"
> timestamp="2008-10-17T14:33:31Z" version="2" changeset="406212"
> user="crazykangaroo" uid="71766"/>
>    6663   <node id="102228" lat="60.2163811" lon="9.6328650"
> timestamp="2008-10-17T14:33:31Z" version="2" changeset="406212"
> user="crazykangaroo" uid="71766"/>
>    6664   <node id="102229" lat="60.2153778" lon="9.6332092"
> timestamp="2008-10-17T14:33:32Z" version="2" changeset="406212"
> user="crazykangaroo" uid="71766"/>
>
> This looks to me like valid xml (the line number is produced by less -N)
>
> For testing I also tried to use --bounding-box or tried to use no
> bounding at all (which in fact should produce a copy of the whole
> planet-file):
> the error-message is the same.
>
> Any other ideas what causes the problem or how to find out? And what
> does the "publicId=(null), systemId=(null)" in the error-message mean
> could this be a hint to the cause?
>
> Marco
>
>
>
> Karl Newman schrieb:
>   
>> On Thu, Apr 23, 2009 at 12:39 PM, Marco Lechner - FOSSGIS e.V.
>> <marco.lechner at fossgis.de <mailto:marco.lechner at fossgis.de>> wrote:
>>
>>     hi karl,
>>
>>      ./bin/osmosis --read-xml-0.6 file="path/planet-090421.osm.bz2"
>>     compressionMethod=bzip2 --bounding-polygon-0.6 file=path/aoi.pff
>>     --write-xml-0.6 file=path/aoi_2009-04-21_v06.osm
>>
>>     gives (almost) the same error as pure v0.5:
>>
>>      Unable to parse xml file path/planet-090421.osm.bz2.
>>      publicId=(null),
>>     systemId=(null), lineNumber=6663, columnNumber=34.
>>        at
>>     com.bretth.osmosis.core.xml.v0_6.XmlReader.run(XmlReader.java:114)
>>        at java.lang.Thread.run(Thread.java:636)
>>     Caused by: org.xml.sax.SAXParseException: XML document structures must
>>     start and end within the same entity.
>>
>>
>>     Marco
>>
>>
>> So, it sounds like you had multiple problems. Probably your planet
>> file is corrupt. You could try to look at the referenced line (6663)
>> in the unpacked file and see if it is valid XML. Most likely you will
>> need to re-download the planet file.
>>
>> Karl
>>     
>
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev
>   





More information about the dev mailing list