Add an option for splitting large bbox changesets into smaller ones

[Dimitar155]

Currently it is possible to upload changesets that cover the whole globe which creates problems for users who want to review local changesets. A possible solution is to allow splitting changesets into squares with user defined maximum dimensions. For example, if I edit 1500 hydrant nodes over the globe, I would be able to define a max bbox of each changeset of 5*5 km. JOSM should be able to split all changes so that the bounding boxes of each changeset isn't larger than that maximum.

[mkoniecz]

JOSM already warns you about oversized changesets.

For example, if I edit 1500 hydrant nodes over the globe, I would be able to define a max bbox of each changeset of 5*5 km.

Are you aware of ​https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct ?

I worry that primary use of such feature would be more efficient hiding of undiscussed automated edits.

[skyper]

Just use upload selection.
Modifications on relations and their members still can lead to big BBoxes but that is caused by the current design of the server api.

[Dimitar155]

Are you aware of ​https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct ?

I worry that primary use of such feature would be more efficient hiding of undiscussed automated edits.

Yes, I'm aware of it. All changesets are public so nothing can be hidden. If you really wanted to monitor such changes there are other more effective ways to do it.

Replying to skyper:

Just use upload selection.
Modifications on relations and their members still can lead to big BBoxes but that is caused by the current design of the server api.

I'm mainly talking about modifications on ways and nodes. The upload selection doesn't help since you have to manually select the bbox which can cover large territories due to the way that JOSM renders elements that are too small to render fully.

[skyper]

Replying to Dimitar155 <osm.dimitar155@…>:

Replying to skyper:

Just use upload selection.
Modifications on relations and their members still can lead to big BBoxes but that is caused by the current design of the server api.

I'm mainly talking about modifications on ways and nodes. The upload selection doesn't help since you have to manually select the bbox which can cover large territories due to the way that JOSM renders elements that are too small to render fully.

Well, if no big relations are involved, you should be fine defining your Bbox by selecting objects with rectangle selection and its modifiers. If you have only a few modified objects but lots of data a filter modified can help.