1 / 21

Implementing Versioned Editing in ArcGIS SDE

Implementing Versioned Editing in ArcGIS SDE. What is Versioned Editing?. Versioned Editing. Workflow that manages concurrent multiuser editors on a single ArcSDE data source Versions represent states or views of the geodatabase Edits are maintained in delta tables until compression.

karlyn
Download Presentation

Implementing Versioned Editing in ArcGIS SDE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementing Versioned Editing in ArcGIS SDE

  2. What is Versioned Editing?

  3. Versioned Editing • Workflow that manages concurrent multiuser editors on a single ArcSDE data source • Versions represent states or views of the geodatabase • Edits are maintained in delta tables until compression

  4. Comparing Past and Present • Before: • Have single editor in each file geodatabase • Notify editors when to disconnect from database • Copy edits from the file geodatabases to a staging file geodatabase, then push those to SDE • Repeat process for each database • After: • Multiple editors in same source • Run maintenance when all users disconnected

  5. Benefits of Versioned Editing • Eliminating dataset duplicates • Faster processing times for dataset edits • Version control • Collaboration

  6. Implementation

  7. The To-Do List • Register data as versioned • Create versions and grant privileges • Provide training to editors

  8. Default QAQC Named Version Named Version Named Version Built Environment Version Tree

  9. Default Default Named Version Named Version Named Version User Other Version Trees Edit Default Directly User User 2-Level

  10. Workflows

  11. Lessons Learned

  12. Tips • Reconcile edits before beginning an edit session • Database administration • Everyone has to be out of database in order to perform full compression • Checking the process_information table was cumbersome (fixed in 10.1) • Need elevated permissions to disconnect users

  13. Troubleshooting • Resolving conflicts • Do not reach full compression • Locks on the database • Deleting tables from the back end • Transaction logs become full

  14. The Road Ahead • Implement versioned editing to more SDE databases • Need a more automated QA process • Work on automating maintenance scripts as scheduled tasks

  15. Tools

  16. Tools • Administration tools in ArcGIS • Python scripts • ArcGIS Diagrammer • GDBT for 10.0/10.1 • Troubleshoot, monitor, and investigate databases • Show Edits Since Reconcile Tool • Generates feature class of all edits between versions • Edit tracking tool

  17. Questions?

More Related