On Wed, 2010-09-22 at 12:10 +0800, maning sambale wrote:
> Any real world cases for this?
Imagine the following scenario:
* 50 ~ 70 digitizers
* 5 QA
* 1 Manager
Each QA has 10 digitizers assigned. After all the data is validated, the
manager merges it and generates the geodb.
All users work a
Any real world cases for this?
>>>
>>> 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 sam
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 sp
There is also discussion in Spatialite google group about
synchronizing - Interaction and syncing between PostGIS and
SpatiaLite.
http://groups.google.com/group/spatialite-users/browse_thread/thread/737ba2c600b0a204
Noli
On 9/21/10, Paolo Corti wrote:
>>> Use case:
>>> 1. I get a subset of t
>> 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
>> applica
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 f
Quite possible. What you want there is operation transformation (OT) -
the same system google wave uses to do concurrent editing.
Its an active research area, though to my knowledge nobody has
implemented OT for geospacial data. (Though I haven't looked).
Should be very doable - couple months if
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 differe
