Multi-user Geodatabase Editing Workflows · Multi-user geodatabase editing environments 1....

Copyright 2006 Copyright 2006 ©© ESRI All Rights Reserved.ESRI All Rights Reserved.Copyright 2006 Copyright 2006 ©© ESRI All Rights Reserved.ESRI All Rights Reserved.

MultiMulti--user Geodatabaseuser GeodatabaseEditing WorkflowsEditing Workflows

Derek LawDerek LawESRI ESRI –– RedlandsRedlands

Feb 19, 2009Feb 19, 2009

Copyright 2006 Copyright 2006 ©© ESRI All Rights Reserved.ESRI All Rights Reserved.

OutlineOutline

•• Geodatabase overviewGeodatabase overview•• Editing environments in multiEditing environments in multi--user geodatabasesuser geodatabases

–– NonNon--versioned editingversioned editing–– Versioned editingVersioned editing

•• Versioned editing with move to baseVersioned editing with move to base

•• SummarySummary

Fed UC 2009 Tech SessionFed UC 2009 Tech Session 22


Defining the geodatabase (GDB)Defining the geodatabase (GDB)

•• Container of spatial & attribute dataContainer of spatial & attribute data–– Collection of geographic datasetsCollection of geographic datasets

•• Native data structure for ArcGISNative data structure for ArcGIS•• Provides the ability to:Provides the ability to:

–– Leverage data relationshipsLeverage data relationships–– Enforce data integrityEnforce data integrity–– Create intelligent featuresCreate intelligent features


DimensionsDimensions

CadastralCadastral

NetworksNetworksSurveysSurveys

AddressesAddresses

AnnotationAnnotationVectorsVectors

3D Objects3D Objects

TopologyTopology

CADCAD

ImagesImages

TerrainTerrain

AttributeAttribute

CartographyCartography

Geodatabase

Copyright 2006 Copyright 2006 ©© ESRI All Rights Reserved.ESRI All Rights Reserved. Fed UC 2009 Tech SessionFed UC 2009 Tech Session 44

Types of geodatabases Types of geodatabases

•• MS AccessMS Access--based personal GDBbased personal GDB•• File GDBFile GDB•• MultiMulti--user GDB user GDB (ArcSDE technology) (ArcSDE technology) –– 3 editions:3 editions:

–– Desktop, Workgroup: SQL Server ExpressDesktop, Workgroup: SQL Server Express–– EnterpriseEnterprise: : DB2, Informix,DB2, Informix,

Oracle, PostgreSQL, & SQL ServerOracle, PostgreSQL, & SQL Server

CapacityCapacity

Number of usersNumber of users

File

ArcGIS Desktop

Personal File Desktop

ArcGIS Server

WorkgroupEnterprise


MultiMulti--user geodatabase (a.k.a. ArcSDE geodatabase)user geodatabase (a.k.a. ArcSDE geodatabase)Required software environmentRequired software environment


Operating system

DBMS

ArcSDEtechnology

ArcObjects

A

Multi-userGeodatabase


OutlineOutline







MultiMulti--user geodatabase editing environmentsuser geodatabase editing environments

1.1. NonNon--versioned editingversioned editing–– Directly edit the base tables (since 9.2 release)Directly edit the base tables (since 9.2 release)–– Supports short transaction workflowsSupports short transaction workflows–– Edits immediately available upon saveEdits immediately available upon save

2.2. Versioned editingVersioned editing–– Available since initial ArcGIS 8.0 releaseAvailable since initial ArcGIS 8.0 release–– Supports long transaction workflowsSupports long transaction workflows–– Lineage of change maintained by Lineage of change maintained by SDESDE tablestables

3.3. Versioned editing (with move to base)Versioned editing (with move to base)–– Option of versioned editing (since 9.2 release)Option of versioned editing (since 9.2 release)–– If editing nonIf editing non--DEFAULTDEFAULT version, stores edits in delta tablesversion, stores edits in delta tables–– Upon save or post to Upon save or post to DEFAULTDEFAULT, edits are moved to the base tables, edits are moved to the base tables



NonNon––versioned editingversioned editing

•• Preserves last set of edits on a datasetPreserves last set of edits on a dataset

•• Editing option for data that is used with nonEditing option for data that is used with non--ESRI clientsESRI clients•• Uses the underlying DBMS transaction modelUses the underlying DBMS transaction model

–– Edits immediately available upon saveEdits immediately available upon save•• Simple data onlySimple data only

–– Points, lines, polygons, annotation, & relationship classesPoints, lines, polygons, annotation, & relationship classes–– NO topology & geometric networksNO topology & geometric networks

•• No archiving, geodatabase replicationNo archiving, geodatabase replication•• No conflict detectionNo conflict detection



Support for information technology (IT) systemsSupport for information technology (IT) systems

•• NonNon--versioned editing provides better geodatabase integration versioned editing provides better geodatabase integration with IT/enterprise systemswith IT/enterprise systems

•• NonNon--ESRI applications see edits in base tablesESRI applications see edits in base tables•• Edits are applied base tablesEdits are applied base tables

–– No delta tables are used, i.e., no A & D tablesNo delta tables are used, i.e., no A & D tables•• DBMS behavior is easy to implementDBMS behavior is easy to implement


ArcGIS editingapplications

3rd party applications Base table

Base & delta tables:Can read & editversioned data

Only see the base table:Do not understand contents

of A & D tables


Editing in a nonEditing in a non--versioned environmentversioned environment

•• Versioning tab Versioning tab -- uncheck undo/redo capabilityuncheck undo/redo capability•• Start Edit SessionStart Edit Session•• Exclusive database lock when updating feature(s)Exclusive database lock when updating feature(s)

–– Lock held until edit session is saved or rolled back Lock held until edit session is saved or rolled back •• Hourglass lingers; does not time outHourglass lingers; does not time out


User 2User 2

A

User 1User 1

Blocked


No undo/redo in nonNo undo/redo in non--versioned editingversioned editing

•• Edits between Edits between save operations are a single DBMS transactionsave operations are a single DBMS transaction–– Save changes Save changes →→ commitcommit in databasein database–– Stop editing with unsaved edits Stop editing with unsaved edits →→ rollbackrollback changeschanges


3 edits in current edit session

3 edits in current edit session

Undo/redo not available during edit session

Undo/redo not available during edit session

Stop editing:Stop editing:commit or rollbackcommit or rollback


Workflow considerationsWorkflow considerations

•• Concurrency issues must be identifiedConcurrency issues must be identified–– Design workflow to prevent/minimize blockingDesign workflow to prevent/minimize blocking

•• Spatially distribute your editors (e.g., edit different areas)Spatially distribute your editors (e.g., edit different areas)–– Blocking related to DBMS isolation levelsBlocking related to DBMS isolation levels

•• No conflict detectionNo conflict detection–– Prevent/minimize lost edits by designing appropriate workflowPrevent/minimize lost edits by designing appropriate workflow

•• Integrating nonIntegrating non--ESRI applicationsESRI applications–– Edits immediately available upon saveEdits immediately available upon save–– Can use DBMS behavior to enforce integrityCan use DBMS behavior to enforce integrity

•• Geodatabase compress not necessaryGeodatabase compress not necessary



OutlineOutline



––Define versioningDefine versioning––Feature class tables & ArcSDE repository Feature class tables & ArcSDE repository ––Reconcile & conflict detectionReconcile & conflict detection––PostPost––CompressCompress





Versioned editingVersioned editing

•• Basis for multiple users editing data simultaneouslyBasis for multiple users editing data simultaneously•• Supports GIS editing workflowsSupports GIS editing workflows

with long transactionswith long transactions–– Edits stored in delta tablesEdits stored in delta tables

•• SimpleSimple & complex data& complex data–– Points, lines, polygons, annotation,Points, lines, polygons, annotation,

& relationship classes& relationship classes–– Topology & geometric networksTopology & geometric networks

•• Facilitates archiving, geodatabase replicationFacilitates archiving, geodatabase replication•• Conflict detection available during reconcileConflict detection available during reconcile


Editor 1Editor 1versionversion

Editor 2Editor 2versionversion

DEFAULTDEFAULT


Versioning workflows Versioning workflows –– applicationsapplications

AnalystPublic

•• Editing with Long TransactionsEditing with Long Transactions–– Isolate work across multiple sessionsIsolate work across multiple sessions

•• Edits do not impact othersEdits do not impact others•• E.g., Parcel editingE.g., Parcel editing

Farmland Residential•• Workflow managementWorkflow management–– Create versions for project stagesCreate versions for project stages

•• E.g., Land developmentE.g., Land development

A

FloodPublic

•• Model whatModel what--if scenariosif scenarios–– Simulate situations with versionsSimulate situations with versions

–– E.g., Disaster event planningE.g., Disaster event planning


ArcSDEtechnology

What is versioning?What is versioning?

•• Storing edits without affecting the original dataStoring edits without affecting the original data

•• A version isA version is a specific a specific ““viewview”” of the geodatabaseof the geodatabase–– Persistent record of changesPersistent record of changes–– Applies to the entire geodatabase, NOT on a feature classApplies to the entire geodatabase, NOT on a feature class–– All multiAll multi--user geodatabases have a user geodatabases have a DEFAULTDEFAULT versionversion

•• Versions are not affected by changes occurring in other Versions are not affected by changes occurring in other versions of the geodatabaseversions of the geodatabase


ParcelsParcelsversionversion

ZoningZoningversionversion


Concept of versioningConcept of versioning


Sample tableSample table

A

2 editors make changes2 editors make changes

User 1User 1

User 2User 2

User 1User 1

Another table records changesAnother table records changes

User 1User 1 User 2User 2


Versioning Versioning -- getting startedgetting started

•• Before editing, must Before editing, must register a dataset as versionedregister a dataset as versionedin ArcCatalogin ArcCatalog

–– Creates the delta tables for an individualCreates the delta tables for an individualdatasetdataset

•• Must register entire feature datasetMust register entire feature dataset–– Registers Registers ALLALL feature classesfeature classes

•• Version managerVersion manager: create versions: create versionsthat support business workflowthat support business workflow

–– In ArcCatalog or ArcMapIn ArcCatalog or ArcMap•• Set properties for each versionSet properties for each version

–– E.g., owner, permissions, descriptionE.g., owner, permissions, description•• Every version has a parent, except for Every version has a parent, except for DEFAULTDEFAULT



Multi-userGeodatabase

Feature class tables in the geodatabaseFeature class tables in the geodatabase


ArcObjects

A

Delta tablesDelta tables

DBMS

Base tablesBase tables

** Spatial type storagewill not have “F” table **


ArcSDE repository tables in the geodatabaseArcSDE repository tables in the geodatabase


DBMS

Geodatabase Geodatabase system tablessystem tables

Feature class tablesFeature class tables

A

VersioningVersioningrelated tablesrelated tables


Register a feature class as versioned;Register a feature class as versioned;create versions, & perform editscreate versions, & perform edits


Demo 1Demo 1


Versioning terminologyVersioning terminology

•• State State –– Unit of workUnit of work–– A A numbernumber per editper edit–– Made up of multiple transactions Made up of multiple transactions

at the DBMS levelat the DBMS level

•• LineageLineage–– Set of states belonging to a versionSet of states belonging to a version

•• State treeState tree–– Logical map of statesLogical map of states

•• Visualization of a Visualization of a lineagelineage••State_LineagesState_Lineages tabletable

•• VersionVersion–– Textual pointer to a stateTextual pointer to a state–– Represents entire lineage of editsRepresents entire lineage of edits


State (base)

0

State

1

State

2

LINEAGE

VERSION_NAME

A


Versioning Versioning -- putting it all togetherputting it all together


Default

Business F S

Parcels feature classParcels feature class

A

D

A

User 1 User 2

State 1State 1(add)(add) 1

State 2State 2(delete)(delete)

2

State 3State 3(merge)(merge)

3

3

State 4State 4(add)(add)

4

User 1User 1’’ssversionversion

User 2User 2’’ssversionversion


Version managementVersion management


Business F S

Parcels feature classParcels feature classD

2 3

A

1 43

43

User 2version

2

User 1version

1

DEFAULT

0

A

User 2versionLineage4, 2, 0

User 1versionLineage3, 1, 0


Version hierarchiesVersion hierarchies

•• Select workflow combination that best matches business Select workflow combination that best matches business practicespractices


A

SDE.DEFAULTSDE.DEFAULT

Editing childrenEditing childrenof of SDE.DEFAULTSDE.DEFAULT


Editing childrenEditing childrenof surrogateof surrogateSDE.DEFAULTSDE.DEFAULT


Multiple tierMultiple tierSDE.DEFAULT:SDE.DEFAULT:

versioning hierarchyversioning hierarchy


Direct editing ofDirect editing ofSDE.DEFAULTSDE.DEFAULT

Represents a versionRepresents a version


Merging changes Merging changes -- reconcile & postreconcile & post

•• ArcMap includes methods for ArcMap includes methods for mergingmerging versionsversions–– Tools available to resolve Tools available to resolve conflictsconflicts


Edit (child) version Target (parent) version

Reconcile pulls changesReconcile pulls changesfrom target into edit versionfrom target into edit version

Edit (child) version Target (parent) version

Post pushes changesPost pushes changesfrom edit into target versionfrom edit into target version

A

ReconcileReconcile

PostPost

Post ALWAYS follows reconcilePost ALWAYS follows reconcile


Version change detectionVersion change detection

•• New version changes viewer toolNew version changes viewer tool–– Enables users to compare a version with an Enables users to compare a version with an ancestor versionancestor version, ,

without performing a reconcilewithout performing a reconcile–– Shows all inserts, deletes, & updates made to the version since Shows all inserts, deletes, & updates made to the version since the the

last time it and the selected version were identicallast time it and the selected version were identical–– Total # of changes shown,Total # of changes shown,

per feature classper feature class–– Do not have to be inDo not have to be in

an edit sessionan edit session


9.3


ReconcileReconcile

•• Incorporates edits from parent (target) Incorporates edits from parent (target) version to child (edit) versionversion to child (edit) version

–– Can reconcile against any Can reconcile against any ancestorancestor versionversion–– Performed in an edit sessionPerformed in an edit session–– Can undo changesCan undo changes–– Must be done Must be done beforebefore a post operationa post operation

•• Detects differences &Detects differences &discovers discovers conflictsconflicts

•• Must be the only user currentlyMust be the only user currentlyediting version to executeediting version to execute

CurrentCurrentParentParent

Plan1Plan1ChildChild

A


Reconciling conflictsReconciling conflicts

•• Conflicts detected if edit(s) occurred to same objectConflicts detected if edit(s) occurred to same object•• 2 scenarios:2 scenarios:

1.1. UPDATE/UPDATEUPDATE/UPDATE2.2. UPDATE/DELETEUPDATE/DELETE

•• Conflicts require Conflicts require resolutionresolution by by reconciling userreconciling user•• Message Message notifies of conflictnotifies of conflict

–– Choose to abort or resolve conflictsChoose to abort or resolve conflicts–– Followed by a resolution dialog boxFollowed by a resolution dialog box



User experience for conflict detectionUser experience for conflict detection

•• When reconcile is performed, 2 options for detecting conflicts:When reconcile is performed, 2 options for detecting conflicts:1.1. By object IDBy object ID

•• A feature is in conflict when 2 users edit any part of the same A feature is in conflict when 2 users edit any part of the same featurefeature

2.2. By attributeBy attribute•• A feature is in conflict only if 2 users edit the same attributeA feature is in conflict only if 2 users edit the same attribute

Object ID Name Color

88 Sam Red


Sam


88 Jane RedJane

Editor 1Object ID Name Color

88 Sam BlueSam

Editor 2


88 Jane RedJane

Editor 1Object ID Name Color

88 Sam BlueSam

Editor 2

A


Conflict resolution dialogConflict resolution dialog

•• Provides ability to visualize & manage conflicts from Provides ability to visualize & manage conflicts from both the target & edit versionsboth the target & edit versions

–– Interactive dynamic display of each versionInteractive dynamic display of each version–– Common ancestor state is also viewableCommon ancestor state is also viewable


Merge geometries optionMerge geometries option

•• Enhances conflict resolution managementEnhances conflict resolution management•• Allows users to resolve geometry conflicts by merging Allows users to resolve geometry conflicts by merging

representations from both versionsrepresentations from both versions•• Applicable for editing large polyline & polygon featuresApplicable for editing large polyline & polygon features

–– E.g., water mains, coastlinesE.g., water mains, coastlines


Edit versionEdit version Target versionTarget version Edit versionEdit version

merge

A

9.3


PostPost

•• SynchronizesSynchronizes current edit session with target versioncurrent edit session with target version–– Modifications saved to target; 2 versions now identicalModifications saved to target; 2 versions now identical–– Must be done in an edit sessionMust be done in an edit session–– Performed after reconciling with another versionPerformed after reconciling with another version–– CannotCannot be undonebe undone

•• ApplyingApplying changes to target versionchanges to target version–– Not necessary to post Not necessary to post –– optionaloptional

•• Depends on workflowDepends on workflow


CurrentCurrentParentParent

Plan1Plan1ChildChild

A


Compressing the geodatabaseCompressing the geodatabase

•• Maintains performanceMaintains performance–– Removes unreferenced rowsRemoves unreferenced rows

from delta tablesfrom delta tables–– Reduces depth of state treeReduces depth of state tree

•• Run periodically, based on Run periodically, based on editing activityediting activity

–– Must Must compress as compress as ““SDESDE”” useruser

–– Update statistics before & afterUpdate statistics before & after•• Depends on editing activityDepends on editing activity

–– Not unreasonable to compressNot unreasonable to compressevery nightevery night


A

AfterAfter

6059

0

WILSON.EDITWILSON.EDIT


RALEIGH.EDITRALEIGH.EDIT

BeforeBefore

HELPER.STUDYHELPER.STUDY(deleted)(deleted)

0

61

58 60

59

62


Reconcile & post versionsReconcile & post versions


Demo 2Demo 2


OutlineOutline







Versioned editing with move to baseVersioned editing with move to base

•• Versioned behavior if editing dataset in nonVersioned behavior if editing dataset in non--DEFAULTDEFAULT versionversion•• If editing If editing DEFAULTDEFAULT, edits are applied to base tables, edits are applied to base tables•• Suggested for nonSuggested for non--ESRI client interactionESRI client interaction•• Simple data onlySimple data only

–– Points, lines, polygons, annotation, & relationship classesPoints, lines, polygons, annotation, & relationship classes•• No archiving, geodatabase replicationNo archiving, geodatabase replication•• Supports undo/redo Supports undo/redo



Workflow considerationsWorkflow considerations

•• IT integrationIT integration–– Uses DBMS behavior to enforce data integrityUses DBMS behavior to enforce data integrity–– Use geodatabase behavior for ArcGIS editingUse geodatabase behavior for ArcGIS editing

•• Versioning behavior on nonVersioning behavior on non--DEFAULT DEFAULT versionsversions–– Edits are stored in the delta tablesEdits are stored in the delta tables

•• No conflict detection on No conflict detection on DEFAULTDEFAULT–– Option: Use surrogate for conflicts before posting to Option: Use surrogate for conflicts before posting to DEFAULTDEFAULT

•• Geodatabase compress necessaryGeodatabase compress necessary



Editing Editing DEFAULT DEFAULT versionversion

•• Start editing Start editing DEFAULTDEFAULT•• Edits stored in A & D tablesEdits stored in A & D tables

–– Each edit receives state IDEach edit receives state ID–– EnablesEnables undo/redo capabilityundo/redo capability


ZIP_CODES

Base tableBase table(state 0)(state 0)

No edits have occurredNo edits have occurred(state 0)(state 0)

A40

D40During edit sessionDuring edit session(edits in A & D tables)(edits in A & D tables)

A


Save Save -- edits are moved to base tableedits are moved to base table

••DEFAULTDEFAULT version references new stateversion references new state–– Last state of edit sessionLast state of edit session

•• Edits referenced by Edits referenced by DEFAULTDEFAULT moved to base tablemoved to base table–– Edits now at state 0Edits now at state 0


Save edit sessionSave edit session(edits now in base tables)(edits now in base tables)

A40

D40

ZIP_CODES

OID 11 OID 11 -- new feature, no attributenew feature, no attributeOID 5 OID 5 -- updated feature geometryupdated feature geometryOID 12 OID 12 -- new feature, new attributenew feature, new attribute

OID 2 OID 2 -- deleteddeleted


Summary: MultiSummary: Multi--user geodatabase editing optionsuser geodatabase editing options

Non-versionedediting

Versionedediting with

move to base

Versionedediting

Editabledata types

Simplefeature classes

Simplefeature classes

All data types

Supportedworkflows

Simple Simple & advancedwith versions

Archiving /replicationnot supported

Simple & advancedwith versions

Archiving & replicationsupported

DBMStransaction “type”

Short(single edit session)

Long(multiple edit session)

Long(multiple edit session)

Supportsundo/redo

No Yes Yes

Feature classtables involved

Base table Base & possiblydelta tables

Delta tables

Supportsarchiving & replication

No No Yes

Supports DBMSdata integrity

features

Yes Yes - when editingDEFAULT version;after save

No – when editingother versions

No



SummarySummary



––Define versioningDefine versioning––Feature class tables & ArcSDE repository Feature class tables & ArcSDE repository ––Reconcile & conflict detectionReconcile & conflict detection––PostPost––CompressCompress


•• Please complete review surveyPlease complete review survey



Feedback on the geodatabase/ArcSDE:Feedback on the geodatabase/ArcSDE:Derek Law (Derek Law ([email protected]@esri.com))


Questions?Questions?

Multi-user Geodatabase Editing Workflows · Multi-user geodatabase editing environments 1....

Documents

Transcript of Multi-user Geodatabase Editing Workflows · Multi-user geodatabase editing environments 1....