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
I have got an error while trying to merge two osm data files as follows:
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Cannot represent 89962 as a char. at org.openstreetmap.osmosis.core.util.IntAsChar.intToChar(IntAsChar.java:32) at org.openstreetmap.osmosis.core.domain.v0_6.Way.store(Way.java:200)
Osmosis stores the number of way nodes as a char which has a maximum size of 64K. This is not an issue unless broken data is entered into the OSM database.
If this becomes a common issue, Osmosis can be patched to treat the way node count (and relation member count) as a 32-bit integer but I'm hesitant to make this change for what appears to be a one-off (or perhaps two-off ...) incident.
Hello
I have got an error while trying to merge two osm data files as follows:
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Cannot represent 89962 as a char. at org.openstreetmap.osmosis.core.util.IntAsChar.intToChar(IntAsChar.java:32) at org.openstreetmap.osmosis.core.domain.v0_6.Way.store(Way.java:200)
In the mail archive of openstreetmaps stored similar issues, but link to patches is broken and last osmosis build 0.40.1 and build from github sources reproduce error as well
http://www.mail-archive.com/dev@openstreetmap.org/msg09679.html
http://lists.openstreetmap.org/pipermail/osmosis-dev/2011-March/000961.html
command line for merging is
D:\temp\osmosis_latest\osmosis_src\package\bin\osmosis.bat --read-xml enableDateParsing=no file=map_track_klimec.osm outPipe.0=1 --read-xml enableDateParsing=no file=strm_klimec.osm outPipe.0=2 --sort type="TypeThenId" inPipe.0=1 outPipe.0=3 --sort type="TypeThenId" inPipe.0=2 outPipe.0=4 --merge conflictResolutionMethod=version inPipe.0=3 inPipe.1=4 outPipe.0=5 --write-xml file=all_klimec.osm inPipe.0=5
first file is osm part of country map and second osm, that represent rtsm data
The text was updated successfully, but these errors were encountered: