You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: stephankn [Submitted to the original trac issue database at 1.21pm, Tuesday, 17th February 2009]
Downloading data in slices seams to corrupt the data. Later osmosis fails on the data with the following exception:
[#220 100% ] Tileset (12,2204,1370) around 51.04,13.75
[#220 0% Download] Trying smaller slices for map data from ROMA
[#220 0% tile] Running area-center... ERROR
The following command produced an error message:
"c:\Program Files\Java\jre6\bin\java.exe" -Xmx5G -cp java/osmosis/osmosis.jar;java/area-center.jar com.bretth.osmosis.core.Osmosis -q -p o
rg.tah.areaCenter.AreaCenterPlugin --read-xml D:\TilesAtHome\tmp\12_2204_1370_tib7m\dataclose-areas.osm --area-center --write-xml D:\TilesAt
Home\tmp\12_2204_1370_tib7m\dataclose-areas-area-center.osm
Debug output follows:
| 17.02.2009 17:19:33 com.bretth.osmosis.core.pipeline.common.ActiveTaskManager waitForCompletion
| SCHWERWIEGEND: Thread for task 1-read-xml failed
| com.bretth.osmosis.core.OsmosisRuntimeException: Bound element must come before any entities.
| at com.bretth.osmosis.core.xml.v0_5.impl.OsmElementProcessor.getChild(OsmElementProcessor.java:93)
| at com.bretth.osmosis.core.xml.v0_5.impl.OsmHandler.startElement(OsmHandler.java:79)
| at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(Unknown Source)
| at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
| at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
| at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
| at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
| at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
| at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
| at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
| at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
| at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
| at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at javax.xml.parsers.SAXParser.parse(Unknown Source)
| at javax.xml.parsers.SAXParser.parse(Unknown Source)
| at com.bretth.osmosis.core.xml.v0_5.XmlReader.run(XmlReader.java:109)
| at java.lang.Thread.run(Unknown Source)
| 17.02.2009 17:19:33 com.bretth.osmosis.core.Osmosis main
| SCHWERWIEGEND: Execution aborted.
| com.bretth.osmosis.core.OsmosisRuntimeException: One or more tasks failed.
| at com.bretth.osmosis.core.pipeline.common.Pipeline.waitForCompletion(Pipeline.java:141)
| at com.bretth.osmosis.core.Osmosis.main(Osmosis.java:55)
The text was updated successfully, but these errors were encountered:
Author: bob[at]cakebox.net [Added to the original trac issue at 11.28pm, Tuesday, 17th February 2009]
Osmosis shouldn't die just because there's something before the bound element. I believe you will also get such a thing if you download a couple of areas in josm and save it, since it will output and for every downoaded area.
Author: brett[at]bretth.com [Added to the original trac issue at 10.49am, Saturday, 27th October 2012]
Osmosis has for some time now supported the new bounds element.
However, the bounds element still must exist prior to node, way and relation elements. This is not going to change. Osmosis processes data as a stream so it needs access to the bounds element first. It can't load the entire file into memory first and sort before beginning processing.
Reporter: stephankn
[Submitted to the original trac issue database at 1.21pm, Tuesday, 17th February 2009]
Downloading data in slices seams to corrupt the data. Later osmosis fails on the data with the following exception:
The text was updated successfully, but these errors were encountered: