An organization has ArcGIS Enterprise. A new project requires versioned editing with the ability to show which user deleted a feature from the default version.
The organization hasArcGIS Enterpriseand requires versioned editing.
The project mandates tracking which user deleted a feature from thedefault version.
Why Branch Versioned Editing?
Branch versioningsupports versioned editing workflows and integrates seamlessly witheditor tracking, including operations like tracking who deleted a feature.
It is ideal for web-based workflows inArcGIS Enterpriseand allows for direct interaction with feature services.
The default version remains accessible for analysis while enabling the organization to track user edits, including feature deletions.(ArcGIS Documentation: Branch Versioning)
Alternative Options:
Option B: Traditional versioned editingsupports versioned workflows but does not inherently track who deletes features unless additional workflows are implemented (e.g., custom fields or triggers).
Option C: Nonversioned editingdoes not support versioning workflows or user tracking.
Thus,branch versioned editingis the best workflow to support versioned editing while tracking deleted features.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit