Just to add another option to the discussion, OGC has a Geosynchronization specification getting close to being finalize. It uses XML requests from the Web Feature Service - Transactional spec to describe actions on a spatial database such as add, modify, delete. Like CouchDB, it also doesn't specify what to do about conflict resolution. This has to be done with your software smarts.
OGC® Loosely Coupled Synchronization of Geographic Databases in the Canadian Geospatial Data Infrastructure Pilot http://portal.opengeospatial.org/files/?artifact_id=26609 --- Raj On Sep 20, at 7:46 PM, Volker Mische wrote: > On 20.09.2010 11:48, maning sambale wrote: >> Hi, >> >> Just something for brainstorming. >> >> Use case: >> 1. I get a subset of the data for field work for a couple of days. >> Coming back from field work, I "sync" the edits to the main data >> server. An application takes care of the merge like git does. >> >> 2. Two field workers, edit the same data on a different area. An >> application manages the conflict before merging to main data server. >> >> > > Hi, > > for the sync part you should have a look at CouchDB [1]. Though it doesn't do > the hard part of resolving conflicts. This part would need to be coded. > > [1] http://couchdb.apache.org/ > > Cheers, > Volker > _______________________________________________ > Discuss mailing list > Discuss@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/discuss _______________________________________________ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
