wheelmap-frontend
wheelmap-frontend copied to clipboard
Changeset bounding box area
Describe the bug
Since it was never resolved before the wheelmap-classic repo was retired: #29: “Split your OSM-changesets by wheelmap_visitor into much smaller areas”.
To Reproduce
Steps to reproduce the behavior:
- See changesets by wheelmap_visitor for plenty of examples of excessively large bounding boxes.
- See comments on wheelmap_visitor's changesets for examples of other mappers adversely affected by this misbehaviour.
Expected behavior
Compliance with OSM Wiki § Changesets § Geographical size of changesets.
Software in use:
- rosemary v0.4.4
https://github.com/sozialhelden/wheelmap-frontend/issues/329#issuecomment-988260543
I just want to emphasize that it is an urgent issue. The history tool of the primary website www.openstreetmap.org is hardly usable any more because at any place there is an overlap with lots of wheelmap_visitor changesets, that are distributed all over the world!
The PR mentioned above will create small, atomic changesets. It's not in a deployable state yet, but will be soon. There will be a public beta deployment to test this feature soon. I'm sorry that all this took so long already.
Just a little update: we have implemented writing atomic changesets (= one edit per changeset) in the new branch.
Will post an update again when this is deployed as a beta.
Here is an update on this: Our beta release at https://feature-attach-osm-api.wheelmap.tech/ writes changesets with one edit per changeset. The deployment still contains some known UX issues – when they are fixed, this change will go into production.
(See also https://github.com/sozialhelden/wheelmap-frontend/issues/329, https://github.com/sozialhelden/wheelmap-frontend/issues/389)
The beta deployment is online (blog post, beta.wheelmap.org). Waiting for community feedback, then this will go into production.
This seems to work reliably. Please reopen if you see something that I might have missed.