If the file is valid then perhaps it's a bug in the Xerces parser bundled
with Osmosis. The JDK version you use shouldn't matter because I don't use
its XML parser (Java bundles an ancient version of Xerces with more serious
unicode bugs).
I don't have any suggestions other than to check if there
Hi,
On 01/11/2017 10:30 AM, Frederik Ramm wrote:
> SEVERE: Thread for task 1-read-xml-change failed
I was a bit over-eager in shortening the stack trace. Full detail:
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Unable to parse
xml file x.osc. publicId=(null), systemId=(null), lineNu
Hi,
I have recently had osmosis in --rri mode refuse to apply an update
it had downloaded from OSM, claiming there was an UTF8 error in the
file. I looked and looked but the file was fine, passed UTF8 and XML
validity checks.
I tried to isolate the line that gave me the "error" but isolating i
