Ability to split changesets by location

[nickswalker]

I frequently check/edit the map while traveling... and then forget to upload my changes. I usually only notice once I've already made changes in different location, and then have to export the changeset to split it in some other less friendly editor. Having the ability to split changesets by region in the app would be very useful on the go. Using meaningful geographic boundaries might be nice, but even just clustering changes to try get changesets to just nodes within e.g. 100mi of each other would solve the problem.

I saw a mention of this idea is in this comment: #725 (comment)

[GA-Kevin-Codes]

I am sure this is technically possible, but may fly in the face of general OSM feelings against QA tool avoidance and "automated edits" if you're doing too much too quick to the database. Perhaps instead there could be a notification if you haven't uploaded a saved changeset in X time or a popup when you place a node a great distance from the rest of your changeset? Sort of a "hey, you may want to tap upload before you add this!"

[bryceco]

We already have a check that warns the user that "better imagery" is available if the move to a new location. We could add a pop-up warning to the same check if they have edits pending.