Java Exception: nodes ids are not in ascending order

Diskussionen zu dem Werkzeug hinter der Karte und für eigene Garminkarten
Antworten
Gast

Java Exception: nodes ids are not in ascending order

Beitrag von Gast » Fr Jan 11, 2019 10:02 pm

[johnassel schrieb am 23.02.14 09:16]
Hallo,
ich versuche gerade für Frankreich OSM-Karten zu generieren. Allerdings bricht
der Vorgang nach einiger Zeit mit "java.lang.IllegalArgumentException: nodes
ids are not in ascending order" ab. Das gleiche Profil hat vor längerer Zeit
problemlos funktioniert, auch die Karte für Deutschland mit fast den gleichen
Einstellungen läuft problemlos durch.
Das Log der Konsole:

Code: Alles auswählen

Exception in thread "PBF Reader" java.lang.RuntimeException: 
Unable to read PBF file.
 at nop.osm.pbf.PbfReader.run(PbfReader.java:59)
 at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.RuntimeException: Unable to get next blob from PBF stream.
 at nop.osm.pbf.PbfStreamSplitter.getNextBlob(PbfStreamSplitter.java:94)
 at nop.osm.pbf.PbfStreamSplitter.hasNext(PbfStreamSplitter.java:102)
 at nop.osm.pbf.PbfDecoder.processBlobs(PbfDecoder.java:123)
 at nop.osm.pbf.PbfDecoder.run(PbfDecoder.java:187)
 at nop.osm.pbf.PbfReader.run(PbfReader.java:52)
 ... 1 more
Caused by: java.io.IOException: Stream closed
 at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:162)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:258)
 at java.io.DataInputStream.readInt(DataInputStream.java:387)
 at nop.osm.pbf.PbfStreamSplitter.getNextBlob(PbfStreamSplitter.java:69)
 ... 5 more
Exception in thread "PBF Reader" java.lang.RuntimeException: Unable to read 
PBF file.
 at nop.osm.pbf.PbfReader.run(PbfReader.java:59)
 at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.RuntimeException: Unable to get next blob from PBF stream.
 at nop.osm.pbf.PbfStreamSplitter.getNextBlob(PbfStreamSplitter.java:94)
 at nop.osm.pbf.PbfStreamSplitter.hasNext(PbfStreamSplitter.java:102)
 at nop.osm.pbf.PbfDecoder.processBlobs(PbfDecoder.java:123)
 at nop.osm.pbf.PbfDecoder.run(PbfDecoder.java:187)
 at nop.osm.pbf.PbfReader.run(PbfReader.java:52)
 ... 1 more
Caused by: java.io.IOException: Stream closed
 at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:162)
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:206)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
 at java.io.DataInputStream.readInt(DataInputStream.java:387)
 at nop.osm.pbf.PbfStreamSplitter.getNextBlob(PbfStreamSplitter.java:69)
 ... 5 more
2/22/14 6:55 PM java.lang.IllegalArgumentException: nodes ids are not in 
ascending order
2/22/14 6:55 PM Exception analyzing data for Frankreich_1
java.lang.IllegalArgumentException: nodes ids are not in ascending order
 at nop.osm.nodeindex.NodeIndex.storeNode(NodeIndex.java:83)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:302)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:309)
 at nop.osm.nodetree.NodeTree.copy(NodeTree.java:297)
 at nop.osm.nodetree.NodeTree.copyTo(NodeTree.java:285)
 at nop.osmc.generator.Analyzer.standardAnalysis(Analyzer.java:143)
 at nop.osmc.generator.Analyzer.analyze(Analyzer.java:72)
 at nop.osmc.generator.Mapper.generate(Mapper.java:200)
 at nop.osmc.MapComposer$12.act(MapComposer.java:407)
 at nop.gui.MenuThreadAction.run(MenuThreadAction.java:27)
 at java.lang.Thread.run(Thread.java:744)
Time for analysis 888 sec
Gast

Re: Java Exception: nodes ids are not in ascending order

Beitrag von Gast » Fr Jan 11, 2019 10:02 pm

[johnassel schrieb am 23.02.14 09:18]
commands.log:

Code: Alles auswählen

rem Cutting data with osmosis

java -Xmx4096M -cp 
/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-core-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-pgsnapshot-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/commons-compress-1.4.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/spring-jdbc-3.1.2.RELEASE.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-tagfilter-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-replication-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-areafilter-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/commons-codec-1.7.jar:/home/garmin-osm/map_composer/osmosis/lib/default/spring-expression-3.1.2.RELEASE.jar:/home/garmin-osm/map_composer/osmosis/lib/default/woodstox-core-lgpl-4.1.4.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-replication-http-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/spring-context-3.1.2.RELEASE.jar:/home/garmin-osm/map_composer/osmosis/lib/default/jpf-1.5.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-core-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-set-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-osm-binary-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-xml-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/spring-core-3.1.2.RELEASE.jar:/home/garmin-osm/map_composer/osmosis/lib/default/postgresql-9.1-901-1.jdbc4.jar:/home/garmin-osm/map_composer/osmosis/lib/default/plexus-classworlds-2.4.jar:/home/garmin-osm/map_composer/osmosis/lib/default/commons-dbcp-1.4.jar:/home/garmin-osm/map_composer/osmosis/lib/default/commons-logging-1.1.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/spring-beans-3.1.2.RELEASE.jar:/home/garmin-osm/map_composer/osmosis/lib/default/postgis-jdbc-1.3.3.jar:/home/garmin-osm/map_composer/osmosis/lib/default/stax2-api-3.1.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/spring-tx-3.1.2.RELEASE.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-pgsimple-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-pbf-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/commons-pool-1.5.4.jar:/home/garmin-osm/map_composer/osmosis/lib/default/protobuf-java-2.4.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-extract-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/xz-1.0.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-apidb-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-pbf2-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-tagtransform-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-dataset-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/aopalliance-1.0.jar:/home/garmin-osm/map_composer/osmosis/lib/default/spring-aop-3.1.2.RELEASE.jar:/home/garmin-osm/map_composer/osmosis/lib/default/osmosis-hstore-jdbc-0.43.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/netty-3.2.7.Final.jar:/home/garmin-osm/map_composer/osmosis/lib/default/xercesImpl-2.9.1.jar:/home/garmin-osm/map_composer/osmosis/lib/default/spring-asm-3.1.2.RELEASE.jar:/home/garmin-osm/map_composer/osmosis/lib/default/mysql-connector-java-5.1.21.jar 
org.openstreetmap.osmosis.core.Osmosis --read-bin 
file=/home/garmin-osm/map_composer/temp_files/in/france.osm.pbf --bounding-box 
bottom=46.0 left=-5.3 top=52.0 right=2.0 clipIncompleteEntities=yes --write-pbf 
file=/home/garmin-osm/map_composer/temp_files/in/Frankreich_1_input.osm.pbf 
omitmetadata=true

Feb 22, 2014 5:50:59 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.43.1
Feb 22, 2014 5:51:03 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Preparing pipeline.
Feb 22, 2014 5:51:03 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Launching pipeline execution.
Feb 22, 2014 5:51:03 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Pipeline executing, waiting for completion.
Feb 22, 2014 6:12:30 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Pipeline complete.
Feb 22, 2014 6:12:30 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Total execution time: 1291354 milliseconds.
Logfenster:

Code: Alles auswählen

Starting map generation
Testing Mapsource
java.io.IOException: Cannot run program 
"/home/garmin-osm/map_composer/MapSourceTest.exe": error=13, Permission denied
Saving table Settings
Saving table ConvertRule
Saving table ConvertAction
Saving table IDManager
Checking for local data files.
Cutting data with osmosis
calling osmosis
osmosis done
Starting region Frankreich_1
Newer input file detected
java.lang.IllegalArgumentException: nodes ids are not in ascending order
Finished region Frankreich_1
Generation finished
Saving table Settings
Saving table Outline
Saving table Route
Saving table IDManager
Kann man da irgendwas machen oder liegt es an der Kartendatei?
Gast

Re: Java Exception: nodes ids are not in ascending order

Beitrag von Gast » Fr Jan 11, 2019 10:02 pm

[Nop schrieb am 23.02.14 13:44]
Die genaue Ursache kann ich nicht erkennen. Die entscheidende Zeile ist

Code: Alles auswählen

Caused by: java.lang.RuntimeException: Unable to get next blob 
from PBF stream.
Das PBF-File, das Osmosis ausgespuckt hat, ist nicht lesbar. Am einfachsten
nochmal alle PBF zwischendateien löschen, auf genügend Plattenplatz achten und
erneut probieren. Falls das nichts bringt einen Tag warten bis die Geofabrik
eine neue Eingangsdatei hat und damit erneut laufen lassen.

bye, Nop
Antworten