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

[Kyℓe Hensel]

k-yle left a comment (openstreetmap/openstreetmap-website#5973)

If we decide to get rid of the `create`/`update`/`delete` blocks, then there are two options (broadly speaking):

1. allow attributes to be specified some some elements only. Requires a nested array:

```jsonc
{
  "osmChange": [
    { "elements": [a, b, c, d] },
    { "elements": [e, f], "ifUnused": true },
  ],
  // extra properties for 'options' or 'changesetTags' or whatever could go here
}
```

2. require all attributes to specified per-changeset:

```jsonc
{
  "osmChange": [a, b, c, d, e, f],
  "ifUnused": true,
  // extra properties for 'options' or 'changesetTags' or whatever could go here
}
```

---

I know that iD specifies `if-unused` for *all* elements, and I'm struggling to think of a use-case where you would want `if-unused` to only apply to some items

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

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