I'm trying to find a practical way to limit the spatial extent of features that individual editors can modify in a replicated database architecture. We currently have a central database that is being edited by people in field offices - ideally those editors would only be able to edit features within their geographic area(s) of responsibility. We can create parent/child replicas and use permissions to limit data access, but the well-meaning, more adventurous editors could still load data outside their area (which they do need to be able to see), edit it in their version, and then post erroneous changes. We've had issues with inexperienced users processing widespread, unintended changes that had to be reversed.
I'd also like to be able to have the users only have to pull the data they really need to increase load speed. I think that this would also allow us to more easily pinpoint where we have data quality challenges (though the feature-level editing tracking should help there).
Ideas welcome....
Laura
