JSON support for /changeset/:id/download #5970
Description
Problem
- As a developer of web-based tools,
- I want to avoid bundling a massive xml-parsing library just for a single API endpoint (since almost all others support JSON now)
- so that the page loads faster, we avoid unnecessary library, avoid boilerplate code, etc. etc.
Description
Over the years, JSON support has gradually been added to most APIs.
Uploading & downloading changesets are one of the few APIs that are still XML-only.
- JSON support for changeset upload zerebubuth/openstreetmap-cgimap#407 tracks uploading changesets as JSON
- In this issue tracks downloading changesets in JSON
I imagine we could just create /changeset/:id/download.json to match /changeset/:id/download. The JSON format would be the same as what zerebubuth/openstreetmap-cgimap#407 is proposing1
Screenshots
No response
Footnotes
-
specially, a single array with
"action": "create" | "modify" | "delete"instead of the 3 arrays forcreate,modify,deletewhich is more similar to the current XML format. ↩