Hunter Ray- GIS Analyst
Excerpt
Enterprise geodatabase versioning is an integral part of Enterprise GIS workflows and allows for flexible and manageable workflows for multiuser editing scenarios. Branch versioning is a new type of geodatabase versioning available to Esri users. This new type of versioning has been reconfigured to alleviate some of the pain-points when using traditional versioning and relies on a services-based platform for version use and management. The branch versioning configuration also provides the backbone needed to extend available add-ons/usability of GIS data. Certain solutions like the Utility Network, Trace Network, Parcel Fabric, and Indoors within ArcGIS Enterprise all require data to be branch versioned. Another immensely powerful add-on for branch versioned data is the Validation and Batch Calculation Attribute Rules. Branch versioning may be a great solution when evaluating current and anticipated workflows and can open the door to a new age of capabilities for Enterprise GIS data.
What is Branch Versioning?
Geodatabase versioning is a configuration option for enterprise geodatabases that stabilizes and manages simultaneous edits by multiple users in isolated environments. Branch versioning is a modern Web GIS approach to multiuser enterprise data management. This new type of database versioning is not a replacement for the original type of versioning (now known as traditional versioning), but was built upon the base of its predecessor with some major improvements.
In general, branch versioning is much less confusing and labor-intensive for data managers. The creation, management, and consumption of user versions is centered around Portal for ArcGIS and ArcGIS Pro, with versions being built on feature services. Editors connect to feature layers using Portal for ArcGIS within ArcGIS Pro to create and use versions. This new services-based platform alleviates the need for editors to directly connect to enterprise databases as they do with traditional versioning. Another big change is that the version tree in branch versioning is limited to one level below Default (Parent) version.
Benefits of Branch Versioning
In general, the overall performance is improved with branch versioning. The way branch versioning harnesses the editor tracking fields, Global IDs and a two-level version tree is the biggest contributor to the improved performance. For those familiar with management of traditional versioning, the Delta and Repo tables are no longer present with branch versioning due to the change in background configuration of version management. Ultimately, this eliminates the tedious task of compressing database tables as seen in traditional versioning.
The management of user versions along with the management of individual edits and conflicts between versions is much easier using the ArcGIS Pro Versioning ribbon and its array of tools. Sharing of layers and tables to editors is simplified using the sharing model within Portal for ArcGIS by harnessing an organization’s members and groups to allow access to individual users.
The branch versioning configuration also provides the backbone needed to extend available add-ons/usability of GIS data. Certain solutions like the Utility Network, Trace Network, Parcel Fabric, and Indoors when deployed within ArcGIS Enterprise all require data to be branch versioned. Another immensely powerful add-on for branch versioned data is the Validation and Batch Calculation Attribute Rules.
Considerations
The following are a few considerations for working with branch versioned data:
Once registered as versioned, layers and tables are no longer editable at the local level through a direct database connection.
All edits must be done through the feature service. Data can only be published using the Default version.
Versions are relative to the Feature Service they are created for. Multiple Feature Services published from the same data in a geodatabase allows for partitioned versions.
A custom role can be created for members in Portal for ArcGIS allowing certain users elevated privileges to manage (reconcile/post) user versions
Each user version can be set to Public, Private or Protected, allowing for different view/edit abilities for other users aside from the creator of the version.
Conclusion
Geodatabase versioning is an important part of an Enterprise GIS system. Branch versioning is a modern take on the traditional versioning framework allowing for a Web GIS workflow with ArcGIS Enterprise. Harnessing branch versioning and the services-based platform for multiuser editing workflows can greatly simplify the editing process for both users and database managers and open the doors to new capabilities in the world of ArcGIS.