On Mon, Sep 6, 2010 at 11:41, OpenStreetMap <[email protected]> wrote: > #2620: osmosis can't parse un-uploaded 0.6 .osm files (from JOSM, other > tools) due > to requiring version="" > -------------------------------+-------------------------------------------- > Reporter: ava...@… | Owner: br...@… > Type: defect | Status: closed > Priority: blocker | Milestone: > Component: osmosis | Version: > Resolution: wontfix | Keywords: > -------------------------------+-------------------------------------------- > Changes (by br...@…): > > * status: new => closed > * resolution: => wontfix > > Comment: > > Osmosis is not compatible with JOSM format OSM files. JOSM OSM files are > editor oriented and deviate from Osmosis in a number of ways (version and > action attributes at least ...) If you wish to discuss this in more > detail please post to the osmosis-dev mailing list, but for now there are > no plans to rectify this. > > Ticket URL: <http://trac.openstreetmap.org/ticket/2620#comment:1>
Taking this up on osmosis-dev as suggested. I've only submitted one very minor patch to osmosis so I'm not at all familiar with its architecture, but is it really so hard to just ignore version fields if they're negative integers? I understand that osmosis isn't targeted at JOSM-generated files, but it's a very useful tool, and it would be much more useful it was more tolerant of non-standard input so that you could parse not only XML files coming from the official OSM API, but also files like the JOSM XML which use a slightly altered XML schema. Be forgiving on input and strict on output, and all that good stuff :) _______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
