This request sounds very similar to a kind of a "session saver" I thought about recently. Personally I prefer doing a series of edits then I upload them in one single batch - probably because I am too lazy to add comments with every upload. The other scenario is that e.g. you lose your network connection while editing and obviously you don't want to lose your edits by closing JOSM down. It would be really handy to be able to "continue" later on. A similar third scenario: you are surveying for several days with your laptop and you don't have network access. You don't want to keep JOSM open for the entire period of time as you want to shut your system down when not working to save battery.
By the way, will JOSM detect conflicts when uploading, right?, i.e. when somebody else has edited the same primitives while being offline. Attila On 23 June 2010 23:12, Ævar Arnfjörð Bjarmason <[email protected]> wrote: > On Wed, Jun 23, 2010 at 20:51, MP <[email protected]> wrote: > > On my old computer JOSM was quite a favorite target for OOM killer (1 > > gb java heap) or prone to OutOfMemory exceptions (500-600 mb java > > heap). I think neither of these can be fixed in JOSM. > > Well, JOSM could use on-disk storage (like SQLite or PostgreSQL), but > that would be a pretty major change. Although perhaps it's easier now > with more encapsulated access to the storage backends. > > But a feature like this sounds useful, although personally I just get > into the habit of making very quick and granular uploads. > > _______________________________________________ > josm-dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/josm-dev > _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
