Brett, thank you for your comment. The issue is not an urgent one for me since workarounds exist, and on the many osmosis-based OSM updating machines I've been running continuously for years, this is only the second time I run into it. So it is a rare quirk, but of course I would feel better if I knew where it came from.
I've re-built osmosis with Xerces 2.11.0 and this doesn't change the situation. Should I perhaps try and build a minimal "use Xerces to parse this XML file" program, and if I can replicate the problem with that, file a bug with Xerces? Or is the way in which Osmosis uses Xerces somehow special so that a simple program like that would be very unlikely to trigger the bug? Bye Frederik -- Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" _______________________________________________ osmosis-dev mailing list [email protected] https://lists.openstreetmap.org/listinfo/osmosis-dev
