Hi Scott,
I've just modified the serialisation code to serialise the full 32-bit
signed int instead of casting to an unsigned chararacter.
This means that the internal serialisation format will be slightly less
efficient but I suspect the difference will be immeasurable. Note that
recently I
Brett, do you have any advice?
In OsmosisBinaryParser, I'm using NOCHANGESET and NOVERSION when
there's omitted metadata. Currently both are -1. The bug is because
another serializer in osmosis is complaining that the version number
is negative. We can set NOVERSION to 0, make that code more
Can you give me more of the stack trace?
Scott
Here you go:
SEVERE: Thread for task 1-read-pbf failed
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Cannot represent
-1 as a char.
at
org.openstreetmap.osmosis.core.util.IntAsChar.intToChar(IntAsChar.java:35)
at
then I get the exception:
SEVERE: Thread for task 1-read-pbf failed
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Cannot represent -1
as a char.
at
org.openstreetmap.osmosis.core.util.IntAsChar.intToChar(IntAsChar.java:35)
at
