Modify

Opened 2 years ago

Closed 21 months ago

#22942 closed enhancement (worksforme)

Feature request: Offer to mappers information and options on uploading

Reported by: mrgenie Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: upload max bbox Cc:

Description

Reason, problem:

I noticed quite often OSMCha reports about edits in my city - but there's none.

Someone mapped something in Cuba & the Malaysia
or in the USA and Indonesia
or in Bhutan and Australia

and then this is uploaded in a single row!

What happens now - is the bounding box of the changeset includes also all the other areas which can be thousands of km away.

So someone changing a street name in Melbourne, and at the same time changing the access tag in Bhutan - results in the actual area that's being mapped just a few hundred meters, but over an area of > 30 Million Square Km everyone using QA assurance tools to verify changes in their area is being flagged.

This is an unwanted situation.

And I don't wanna judge any mapper for committing such changesets, being myself one who made the mistake in the past as well, unintentional.

But the thing is - quite often I map something in Itogon (a neighboring municipality) and then back to my own city..

So maybe JOSM could offer here some new feature.

A setting where a user can set, and this just for instance:

  • max uploading bounding box 10sq km (the user can change this) - otherwise give warning
  • allow user to set checkboxes about this warning for "editing inside and outside of admin_level boundaries (again the user can select here then the min/max admin_level boundaries where the warning should be given)

For instance, if I map on both sides of the admin_level=6 boundary then flag the warning, as I'm uploading edits in 2 different cities/municipalities

Now I understand there might be valid reasons sometimes to edit over wider areas - that's why it should be a warning and not mandatory to split them.

Anyway - if the warning is given - then offer the user/mapper to split the upload.

For splitting we can use the user settings - for instance if the user sets the admin_level option for the warning - then we can split uploads based on that .

Again - optionally so the user/mapper can chose from it.

if the admin_level is not set, but instead the max sq km warning comes up and the user clicks:"yes" to split the upload,

then offer a small window with the changes visible, and the user can draw one or multiple polygons how he wishes to split the data to be uploaded.

This way - a user if he edited things in Cuba and then in South Africa - if he chooses to upload with the warning set at admin_level 1 to 6.. it's offered to him to split into both countries, 2 uploads..

Or if I did edits, without actually noticing it, in my city and the neighboring municipality - i have the choice as well to split the upload, and thus significantly reduce these bounding boxes on OSM - more to the area where the edits actually were made.

Thank you for your consideration - ps I'm bad at wording so any questions feel free to contact me at hikeandmap on telegram

Attachments (0)

Change History (2)

comment:1 by skyper, 2 years ago

Keywords: upload max bbox added
Milestone: Longterm
Version: tested

Note, we already have a warning about big bboxes in upload dialog and the advanced preference upload.max-area to set a customized size.

comment:2 by stoecker, 21 months ago

Resolution: worksforme
Status: newclosed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.