This is how StreetComplete does it. Good thing is that the OSM server automatically closes changesets where nothing was added after one hour, so one does not need to worry that a changeset gets "stuck" if the user exits the application without closing the changeset.
On 17/01/2018 18:47, Rory McCann wrote: > On 17/01/18 15:13, Michał Brzozowski wrote: >> Certainly not: >> - one changeset per building, repeated 20 times > > Couldn't this be done with the "upload" vs "new changeset" feature of > the OSM API? A technical solution. Multiple uploads in a single changeset? > > Users want to save/upload frequently (because computers), so we'll never > stop them pressing the button often. Maybe iD could keep a changeset > open and an upload rather than open a new changeset? There would have to > be an option to "close current changeset and open a new one" (& close > current changeset), and to word that in a more friendly way for people > who don't know the terminology. > > I don't think linking to documentation will solve this issue. Too many > users don't read things like that, no matter how much we'd want them to. > > Yes, I know I'm suggesting a software change without offering a patch. > > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
