I'm about to start writing a Go module for the OSM API v0.6 write side: opening and uploading changesets, element CRUD, posting and closing notes, changeset comments, the user inbox, and preferences. Right now there's no Go equivalent of Python's osmapi for any of this, and OAuth 2.0 has been mandatory since June 2024 so anything new also needs to handle that.
Before I go and build it as a separate module, I wanted to check whether you'd want this in osmapi itself. The auth plumbing (PKCE flow + token storage) is application code and would stay outside in any case, but the request/response layer feels like a natural extension of what's already there, and it would all reuse the existing osm.Node/Way/Relation/Change types.
Happy to split a PR into small reviewable pieces. If you'd rather keep osmapi read-only, that's a totally fair scope call and I'll just build it next door.
I'm about to start writing a Go module for the OSM API v0.6 write side: opening and uploading changesets, element CRUD, posting and closing notes, changeset comments, the user inbox, and preferences. Right now there's no Go equivalent of Python's osmapi for any of this, and OAuth 2.0 has been mandatory since June 2024 so anything new also needs to handle that.
Before I go and build it as a separate module, I wanted to check whether you'd want this in osmapi itself. The auth plumbing (PKCE flow + token storage) is application code and would stay outside in any case, but the request/response layer feels like a natural extension of what's already there, and it would all reuse the existing osm.Node/Way/Relation/Change types.
Happy to split a PR into small reviewable pieces. If you'd rather keep osmapi read-only, that's a totally fair scope call and I'll just build it next door.