Geodatabase Editing Workflows

1、Esri UC2010 | Tech WorkshopsTechnical WorkshopsEsri UC2010 | Tech WorkshopsGeodatabase Editing WorkflowsJack Horton (ESRI Olympia)Shawn Thorne (ESRI Redlands)Tony Wakim (ESRI Redlands)Esri UC2010 | Tech WorkshopsOutline Geodatabase overview Editing environments in Multi-user Geodatabases Non-version

2、ed editing Versioned editingDefine versioningFeature class tables & ArcSDE repository Reconcile & conflict detectionPostCompress Versioned editing with move to base SummaryPlease turn off cellphonesEsri UC2010 | Tech WorkshopsDefining the GeodatabaseContainer of spatial & attribute data-

3、Collection of geographic datasetsNative data structure for ArcGISProvides the ability to:-Leverage data relationships-Enforce data integrity-Create intelligent featuresGeodatabaseEsri UC2010 | Tech WorkshopsTypes of Geodatabases MS Access-based Personal Geodatabase File Geodatabase Multi-user Geodat

4、abases 3 Editions: Desktop, Workgroup : SQL Server Express Enterprise : DB2, Informix, Oracle, PostgreSQL & SQL ServerArcGIS ServerEnterpriseFileArcGIS DesktopEnterpriseWorkgroupDesktopPersonalFileEsri UC2010 | Tech WorkshopsEnterprise GeodatabaseEnterpriseGeodatabaseOperating SystemDBMSArcSDEAr

5、cObjectsA2 Required software environmentEsri UC2010 | Tech WorkshopsOutline Geodatabase overview Editing environments in Multi-user Geodatabases Non-versioned editing Versioned editingDefine versioningFeature class tables & ArcSDE repository Reconcile & conflict detectionPostCompress Version

6、ed editing with move to base SummaryEsri UC2010 | Tech WorkshopsMulti-user geodatabase editing environmentsNon-versioned editing-Directly edit the base tables-Supports short transaction workflows-Edits immediately available upon saveVersioned editing-Available since initial ArcGIS release-Supports l

7、ong transaction workflows-Lineage of change maintained by SDE tablesVersioned editing (with move to base)-Option of versioned editing-If editing non-DEFAULT version, stores edits in delta tables-Upon save or post to DEFAULT, edits are moved to the base tablesEsri UC2010 | Tech WorkshopsNonversioned

8、editingPreserves last set of edits on a datasetEditing option for data that is used with non-ESRI clientsUses the underlying DBMS transaction model-Edits immediately available upon saveSimple data only-Points, lines, polygons, annotation, & relationship classes-NO topology & geometric networ

9、ksNo archiving, geodatabase replicationNo conflict detectionA0Esri UC2010 | Tech WorkshopsNon-versioned editing provides better geodatabase integration with IT/Enterprise SystemsNon-ESRI applications see edits in base tablesEdits are applied base tables-No delta tables are used, i.e., no A & D t

10、ablesDBMS behavior is easy to implementSupport for information technology (IT) systemsArcGIS editingapplications3rd party applicationsBase tableBase & delta tables:Can read & editversioned dataOnly see the base table:Do not understand contents of A & D tablesEsri UC2010 | Tech WorkshopsU

11、ser 2Versioning tab - uncheck undo/redo capabilityStart Edit SessionExclusive lock when updating feature(s)-Lock held until edit session is saved or rolled back -Hourglass lingers; does not time outEditing in a Non-versioned environmentA1User 1BlockedEsri UC2010 | Tech WorkshopsNo Undo/Redo in Non-v

12、ersioned editingEdits between save operations are a single DBMS transaction-Save changes - commit to the database-Stop editing with unsaved edits - rollback changes3 edits in current edit sessionUndo/Redo not available during edit sessionEsri UC2010 | Tech WorkshopsWorkflow considerationsConcurrency

13、 issues must be identified-Design workflow to prevent/minimize blocking-Spatially distribute your editors (e.g., edit different areas)-Blocking related to DBMS isolation levelsNo conflict detection-Prevent/minimize lost edits by designing appropriate workflowIntegrating non-ESRI applications-Edits i

14、mmediately available upon save-Can use DBMS behavior to enforce integrityGeodatabase compress not necessaryEsri UC2010 | Tech WorkshopsOutline Geodatabase overview Editing environments in Multi-user Geodatabases Non-versioned editing Versioned editingDefine versioningFeature class tables & ArcSD

15、E repository Reconcile & conflict detectionPostCompress Versioned editing with move to base SummaryEsri UC2010 | Tech WorkshopsWhat is versioning?Storing edits without affecting the original dataA version is a specific “view” of the geodatabase-Persistent record of changes-Applies to the entire

16、geodatabase, NOT on a Feature Class-All multi-user geodatabases have a DEFAULT versionVersions are not affected by changes occurring in other versions of the geodatabaseArcSDEtechnologyEsri UC2010 | Tech Workshops Concept of VersioningA4 Allows multiuser editing without locking data or blocking othe

17、r editors Isolates edits without changing the original base dataEsri UC2010 | Tech WorkshopsVersioned editingBasis for multiple users editing data simultaneouslySupports GIS editing workflowswith long transactions-Edits stored in delta tablesSimple & complex data-Points, lines, polygons, annotat

18、ion,& relationship classes-Topology & geometric networksFacilitates archiving, geodatabase replicationConflict detection available during reconcileEsri UC2010 | Tech WorkshopsVersioning workflows applications Model what-if scenarioso Simulate situations with versions E.g., Disaster event pla

19、nningAnalystPublicFarmlandResidential Editing with Long Transactionso Isolate work across multiple sessionso Edits do not impact othersE.g., Parcel editingFloodPublic Workflow managemento Create versions for project stagesE.g., Land developmentA2Esri UC2010 | Tech WorkshopsVersioning - getting start

20、edBefore editing, must register a Feature Class or a Feature Dataset as Versioned in ArcCatalog-Creates delta tables for each Feature ClassMust register the entire Feature Dataset-Registers ALL Feature Classes contained within itVersion Manager: create versionsthat support business workflow-In ArcCa

21、talog or ArcMapSet properties for each version-E.g., owner, permissions, descriptionEvery version has a parent, except for DEFAULTEsri UC2010 | Tech WorkshopsFeature Class tables in the GeodatabaseArcObjectsEnterprisegeodatabaseA2DBMSEsri UC2010 | Tech WorkshopsRepository tables in the GeodatabaseGe

22、odatabase System Tables Tables directly associated with VersioningA1Esri UC2010 | Tech Workshops Demo 1Register a Feature Class as Versioned Add the Editor Toolbar to ArcMapPerform some edits to a versionEsri UC2010 | Tech WorkshopsVersioning TerminologyState -Unit of work-A number per edit-Made up

23、of multiple transactions at the DBMS level Lineage-Set of states belonging to a versionState tree-Logical map of states-Visualization of a lineage-State_Lineages tableVersion-Textual pointer to a state-Represents entire lineage of editsState (base)0State1State2LINEAGEVERSION_NAMEA4Esri UC2010 | Tech

24、 WorkshopsVersioning - putting it all togetherDefaultBusinessFSA TableD TableTonyJack12343A7Esri UC2010 | Tech WorkshopsVersion managementBusinessFSD Table23A Table1434321DEFAULT0JacksLineage4, 2, 0TonysLineage3, 1, 0A5TonysversionJacksversionEsri UC2010 | Tech WorkshopsVersion hierarchiesSelect wor

25、kflow combination that best matches business practices A3Esri UC2010 | Tech WorkshopsMerging changes - Reconcile & PostArcMap includes methods for merging versions-Tools available to resolve conflictsEdit (child) version Target (parent) versionReconcile pulls changesfrom target into edit version

26、Edit (child) versionTarget (parent) versionPost pushes changesfrom edit into target versionA5 Can only Post after a ReconcileEsri UC2010 | Tech WorkshopsVersion change detectionVersion Changes viewer tool-Enables users to compare a version with an ancestor version-Shows differences between two versi

27、onsEsri UC2010 | Tech WorkshopsReconcile Incorporates edits from parent (target) version into the child (edit) version Can reconcile against any ancestor version Performed in an edit session Can undo changes Must be done before a post operation Detects differences & discovers conflicts Must be t

28、he only user currentlyediting version to executeA2Esri UC2010 | Tech WorkshopsReconciling conflictsConflicts detected if edit(s) occurred to same object2 scenarios:-UPDATE/UPDATE-UPDATE/DELETEConflicts require resolution by reconciling userMessage notifies of conflict-Choose to abort or resolve conf

29、licts1.Followed by a resolution dialog boxEsri UC2010 | Tech WorkshopsUser experience for conflict detection- By Object ID (row)-A feature is in conflict when 2 users edit any part of the same feature (ie: edit the same row). -Editor 1 changes Name to “Jane”; Editor 2 changes Color to “Blue” - confl

30、ict detected-By Attribute (column)-A feature is in conflict only when 2 users edit the same attribute (ie: edit the same column). -Editor 1 changes Name to “Jane”; Editor 2 changes Color to “Blue” - no conflict Object IDNameColor88SamRedObject IDNameColor88JaneRedObject IDNameColor88SamBlueObject ID

31、NameColor88JaneRedObject IDNameColor88SamBlueA2When a Reconcile is performed, there are 2 options available for detecting conflicts:Esri UC2010 | Tech WorkshopsConflict resolution dialog Provides ability to visualize & manage conflicts from both the target & edit versions Interactive dynamic

32、 display of each version Common ancestor state is also viewableEsri UC2010 | Tech WorkshopsMerge geometries optionEnhances conflict resolution managementAllows users to resolve geometry conflicts by merging representations from both versionsApplicable for editing large polyline & polygon feature

33、s-E.g., water mains, coastlinesmergeA1Esri UC2010 | Tech WorkshopsPostSynchronizes current edit session with target version-Modifications saved to target; 2 versions are now identical-Must be done in an edit session-Performed after reconciling with another version-Cannot be undone-Applying changes t

34、o target version-Not necessary to post optional-Depends on workflowA2Esri UC2010 | Tech Workshops Demo 2Add the Versioning toolbar to ArcMapView the Version Changes ToolReconcile & Post a versionEsri UC2010 | Tech WorkshopsMaintains performance-Removes unreferenced rowsfrom delta tables-Reduces

35、depth of state treeRun periodically, based on editing activity-Must compress as “SDE” user-Update statistics before & afterDepends on editing activity-Not unreasonable to compressevery nightCompressing the geodatabaseA2Before06158605962After60590Esri UC2010 | Tech WorkshopsOutline Geodatabase ov

36、erview Editing environments in Multi-user Geodatabases Non-versioned editing Versioned editingDefine versioningFeature class tables & ArcSDE repository Reconcile & conflict detectionPostCompress Versioned editing with move to base SummaryEsri UC2010 | Tech WorkshopsVersioned editing with mov

37、e to baseVersioned behavior if editing dataset in non-DEFAULT versionIf editing DEFAULT, edits are applied to base tablesSuggested for non-ESRI client interactionSimple data only-Points, lines, polygons, annotation, & relationship classesNo archiving, geodatabase replicationSupports undo/redo A0

38、Esri UC2010 | Tech WorkshopsEditing DEFAULT versionStart editing DEFAULTEdits stored in A & D tables-Each edit receives a state ID-Enables Undo/Redo capabilityZIP_CODESA40D40A1Esri UC2010 | Tech WorkshopsEdits are moved to base tableDEFAULT version references new state-Last state of edit session

39、Edits on DEFAULT version moved to base table upon save-Edits now at state 0A40D40ZIP_CODESEsri UC2010 | Tech WorkshopsWorkflow considerationsIT integration-Uses DBMS behavior to enforce data integrity-Use geodatabase behavior for ArcGIS editingVersioning behavior on non-DEFAULT versions-Edits are stored in the delta tablesNo conflict detection on DEFAULT-Option: Use surrogate for conflicts before posting to DEF