Modify ↓
#2644 closed defect (worksforme)
Rev 1604 stops JOSM editing XAPI data that lacks version attributes
| Reported by: | anonymous | Owned by: | team |
|---|---|---|---|
| Priority: | major | Component: | Core |
| Version: | Keywords: | ||
| Cc: | karl.guggisberg@… |
Description
Since 1604, I can no longer edit data downloaded using XAPI because I get:
org.xml.sax.SAXException: Missing attribute "version" on OSM primitive with id 289544998
at org.openstreetmap.josm.io.OsmReader.readCommon(OsmReader.java:314)
This is because some of the nodes downloaded using XAPI don't appear to have a version attribute.
What needs fixing here, JOSM or XAPI?
Thanks
Attachments (0)
Change History (3)
comment:1 Changed 4 years ago by Gubaer
- Cc karl.guggisberg@… added
comment:2 Changed 4 years ago by stoecker
- Resolution set to worksforme
- Status changed from new to closed
JOSM and XAPI 0.6 work fine now.
comment:3 Changed 19 months ago by anonymous
This again stopped working!
Note: See
TracTickets for help on using
tickets.



I'd say XAPI. If XAPI files have a "0.6" api header they should provide a version attribute on all primitives. JOSM rejects "0.6"-files with missing versions.
You can change the version in the file to "0.5". In this case, JOSM will accept missing versions. It will also prevent you from uploading 0.5-data to the 0.6-API.