Open talllguy opened 4 months ago
This is not actionable at this time, since we're not exposing the maximum permitted bounding box size through an API. You would need to raise another issue/enhancement request on osm-website repo.
I wonder about an alternative that's not directly tied to OSM's limits then, but which is common sense for a new user? E.g. prevent (or heavily guard against) a user with fewer than 10 changesets from adding edits that span more than 1 degree of latitude or longitude? My thinking is I imagine users trying to make small changes in a few distant locations they know. That's just a gut amount on my part though and not based in observing user behavior on first changesets.
Naturally doesn't need to be what I've suggested, but the general approach I'm suggesting is that iD could set limits of its own to help guide new users anyway.
Related: #10286.
I wonder about an alternative that's not directly tied to OSM's limits then, but which is common sense for a new user?
This is being tracked in #8590.
Now that https://github.com/openstreetmap/openstreetmap-website/pull/4908 is merged, new users will have difficulty publishing edits when the changeset exceeds that threshold. I propose a UX improvement that will gradually warn the user that their edits are nearing the maximum changeset size.
One possibility would be to draw a pink geojson around the maximum edit area that would adjust as the editor works. The upload button could also show a warning color or glyph as the limit is neared.