Prevent huge area uploads

[SafetyIng]

Streetcomplete generates massively huge changesets (geographical expansion), so that urgent countermeasures must be taken here. It massively complicates the QM of OSM. Especially such large areas should be avoided. Examples can be found in the following CS:

https://www.openstreetmap.org/changeset/124041687
https://www.openstreetmap.org/changeset/124047734

[matkoniecz]

See https://wiki.openstreetmap.org/wiki/StreetComplete/FAQ#A_changeset_made_with_StreetComplete_covers_a_massive_area%2C_why_is_this%3F_How_can_it_be_prevented%3F

It is not covering your answer, please explain why. And confirm that problem is not caused by user error.

[SafetyIng]

And confirm that problem is not caused by user error.

Sorry, that is a problem, that SC has to handle, if their users missuse the software. I don't write to all users now. SC has to handle big areas! And really: I don't care, how. But when an option of your system makes a problem wich is anounced so much often, then you should handle it ;)

[matkoniecz]

that SC has to handle, if their users missuse the software

Not really. Any OSM editor can be misused in ways not preventable in feasible ways.

It would make sense to do something only if it is typically happening due to edits which are not invalid or wrong.

Making wrong edits more visible for reviewers is a good thing.

[SafetyIng]

Making wrong edits more visible for reviewers is a good thing.

Only when it is able to find this edits. When I get 100 edits in a area and 50 are not really in this area, because SC has so big bboxes created, so this edits show up in my search area; then this is a problem.

[BalooUriza]

I'd suggest getting in touch with the user you're having trouble with, and ask that they upload their StreetComplete changes before moving a large distance away

…

On Wed, Jul 27, 2022 at 11:57 AM SafetyIng ***@***.***> wrote: Making wrong edits more visible for reviewers is a good thing. Only when it is able to find this edits. When I get 100 edits in a area and 50 are not really in this area, because SC has so big bboxes created, so this edits show up in my search area; then this is a problem. — Reply to this email directly, view it on GitHub <#4245 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWDFBROUGJKE67W6GXHGBDVWFTBJANCNFSM54ZWED7A> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[SafetyIng]

with the user you're having trouble with, and ask that they upload their StreetComplete changes before moving a large distance away

When Streetcomplete would have a maximum bbox or other options to prevent this happening, than you don't need to get intouch with other users. Technical solutions are always preferable to a level 3 solution (personal behaviour).

[matkoniecz]

It would make sense to do something only if it is typically happening due to edits which are not invalid or wrong.

If large bbox happen due to user "mapping" places which they have not visited then it is misuse of SC.

If there is indicator that large (most?) of large bboxes is caused by people mapping places they visited then some action from SC side may make sense. Until it happens: see FAQ.

If and only if such indicator will happen (based on say review of say continuous list of 100 very large bboxes made by SC mappers) then new issue should be opened.