topic Limit features that can be added to a dataset through the spatial extent? in Data Management Questions https://community.esri.com/t5/data-management-questions/limit-features-that-can-be-added-to-a-dataset/m-p/739652#M41737 <HTML><HEAD></HEAD><BODY><SPAN>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.&nbsp; We've had issues with inexperienced users processing widespread, unintended changes that had to be reversed. </SPAN><BR /><BR /><SPAN>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).</SPAN><BR /><BR /><SPAN>Ideas welcome....</SPAN><BR /><BR /><SPAN>Laura</SPAN></BODY></HTML> Mon, 03 Dec 2012 23:33:17 GMT LauraSilsbee1 2012-12-03T23:33:17Z Limit features that can be added to a dataset through the spatial extent? https://community.esri.com/t5/data-management-questions/limit-features-that-can-be-added-to-a-dataset/m-p/739652#M41737 <HTML><HEAD></HEAD><BODY><SPAN>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.&nbsp; We've had issues with inexperienced users processing widespread, unintended changes that had to be reversed. </SPAN><BR /><BR /><SPAN>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).</SPAN><BR /><BR /><SPAN>Ideas welcome....</SPAN><BR /><BR /><SPAN>Laura</SPAN></BODY></HTML> Mon, 03 Dec 2012 23:33:17 GMT https://community.esri.com/t5/data-management-questions/limit-features-that-can-be-added-to-a-dataset/m-p/739652#M41737 LauraSilsbee1 2012-12-03T23:33:17Z