[OSM-dev] Can't get osmosis to work

[Brett Henderson]

The real error message is at the bottom of the snippet below where it's complaining about broken xml.  However the top of the snippet is providing a warning that the file is a 0.3 version of the planet.  So, a few things to note:
* Osmosis only supports 0.5 versions of planet files.  I should change the warning to an error because nobody takes notice of warnings anyway.
* Old versions of planet files are likely to have utf-8 encoding issues which I suspect has caused the final terminal error.
* Newer planet files are going to be much bigger so I'd suggest using compressed planet files (ideally gzip because bzip2 is slow under java).  Alternatively pipe the output of a bzip2 command into osmosis.

Hope that helps,
Brett

**** Error Message Snippet ***
WARNING: Expected version 0.5 but received 0.3.
Feb 27, 2009 8:29:00 AM
com.bretth.osmosis.core.pipeline.common.ActiveTaskManage
r waitForCompletion
SEVERE: Thread for task 1-read-xml failed
com.bretth.osmosis.core.OsmosisRuntimeException: Unable to parse xml file
planet
.osm.  publicId=(null), systemId=(null), lineNumber=103649741,
columnNumber=25.
        at
com.bretth.osmosis.core.xml.v0_5.XmlReader.run(XmlReader.java:114)
        at java.lang.Thread.run(Unknown Source)
Caused by: org.xml.sax.SAXParseException: An invalid XML character (Unicode:
0x{
2}) was found in the value of attribute "{1}" and element is "13".
        at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
ParseException(Unknown Source)



A. Stice wrote:
> I've been trying to import this planet file into my MySQL database using
> Osmosis, but it isn't working. I've tried several different commands as well
> as downloaded a few different planet files to see if that was the problem
> but nothing has worked. I've been searching around the forum and internet
> for a couple days trying to find out why it isn't working right, but I cant
> seem to find out, so I was hoping one of you guys would be able to help me.
> This is my most recent output, and it ran for a good 20 minutes before
> crashing.
>