[openstreetmap/openstreetmap-website] Implement JSON support for the changeset download API (PR #5973)

mmd notifications at github.com
Thu May 1 13:58:24 UTC 2025


mmd-osm left a comment (openstreetmap/openstreetmap-website#5973)

I think we can keep the sorting of objects (per action) as is, regardless of the format.

Obviously we would have to define in which sequence create/modified/delete actions need to be processed, b/c JSON properties don't have a defined sequence (as opposed to json array elements).

I agree that the action attribute doesn't add much value, the information is anyway available in version and visible attributes. I guess there are historical reasons which I'm not familiar with in detail.

However, for the upload there's an additional 'if-unused' attribute, that wouldn't fit in a pure play osm format. Some sort of extension seems unavoidable in this case.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5973#issuecomment-2844895260
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/5973/c2844895260 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20250501/3cb3bca0/attachment-0001.htm>


More information about the rails-dev mailing list