Modify

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#19712 closed enhancement (wontfix)

Feature Request: Split large number of edits into smaller changesets

Reported by: anonymous Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: feature request, enhancement, upload, changeset Cc:

Description

Uploading large changesets with 500+ edits can make them difficult for other OSM Mappers to review. It would be great if under the advanced tab in the upload window the number of edits to include in one changeset could be limited - similar to how an upload can currently be split into chunks when uploading. An option in the same tab to limit the number of edits in a changeset (thus uploading more than one) would be helpful.

Attachments (1)

Upload.PNG (310.4 KB ) - added by anonymous 4 years ago.
In the advanced tab of the upload window this proposed option would fit well.

Download all attachments as: .zip

Change History (7)

by anonymous, 4 years ago

Attachment: Upload.PNG added

In the advanced tab of the upload window this proposed option would fit well.

comment:1 by anonymous, 4 years ago

Keywords: feature request enhancement upload changeset added

comment:2 by Klumbumbus, 4 years ago

I'm not sure if this is a good idea. If changes which belong together are spread over several changesets it is even harder to review or revert the changes.

comment:3 by anonymous, 4 years ago

This would prevent larger edits being tagged as possible imports.

in reply to:  2 ; comment:4 by anonymous, 4 years ago

Replying to Klumbumbus:

I'm not sure if this is a good idea. If changes which belong together are spread over several changesets it is even harder to review or revert the changes.

It would prevent changsets being tagged as possible imports. Changesets with 700+ edits are cumbersome to review as it is, an option to reduce their size to something manageable would ease review.

in reply to:  4 comment:5 by Klumbumbus, 4 years ago

Replying to anonym:

It would prevent changsets being tagged as possible imports.

If the maximum changes per changeset would be mandatory/fixed then you couldn't distinguish possible imports from normal edits as all have then e.g. max. 100 changes.
Making the maximum changes per changeset optional makes no sense either, because if mappers are too lazy to upload more often then they are also too lazy to set/adjust the maximum changes per changset-value.

comment:6 by stoecker, 4 years ago

Resolution: wontfix
Status: newclosed

I also see no sense in a technical workaround for a human behaviour. If somebody does large changesets, then they should also be large changesets. Hidding this makes no sense.

Last edited 4 years ago by stoecker (previous) (diff)

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.