Trace Networks and Replicas

441
1
Jump to solution
09-14-2023 01:02 PM
AmyRoust
Occasional Contributor III

I've been away from mapping utility data for several years but have returned to a local government with the typical water, sewer, and storm system datasets. I understand that geometric networks are / will be deprecated and that we can now choose from Utility Networks and Trace Networks. Based on what I've read, Utility Networks and the feature classes involved cannot be included in a replica.  However, I cannot find any documentation on the impact of Trace Networks on replication. Can you set up a Trace Network on a parent database and then create a child replica from it?

0 Kudos
1 Solution

Accepted Solutions
MarceloMarques
Esri Regular Contributor

Short Answer:

  • Geodatabase replication is built on top of traditional versioning and uses versioning functionality to synchronize data in most scenarios.
  • Branch versioning is not supported for any data source in any geodatabase replica type.
  • The Trace Network works only with Branch Versioning.
  • Thus, Trace Network does not support Traditional Versioning.
  • Therefore Trace Network does not support Geodatabase Replication.
  • The alternative is to use feature service sync with Trace Network 

Detailed Answer:

Introduction to distributed data—ArcGIS Pro | Documentation

  • Geodatabase replication is built on top of traditional versioning and uses versioning functionality to synchronize data in most scenarios.
  • For a list of supported datasets and limitations of geodatabase replication in ArcGIS Pro, see Replication and geodatabase compatibility.
  • Branch versioning is not supported for any data source in any geodatabase replica type.

MarceloMarques_1-1694726705940.png

  • ArcGIS Desktop (ArcMap / ArcCatalog) Geometric Network is deprecated in ArcGIS Pro.
  • In ArcGIS Pro you need to migrate to Trace Network or the new Utility Network.
  • Trace Network / Utility Network is the modern technology and only works with Branch Versioning.
  • Trace Network / Utility Network is not supported with Geodatabase Replication.

Geodatabase Replication with advanced geodatabase datasets—ArcGIS Pro | Documentation

  • Geometric networks are read-only and are not supported in a replica created in ArcGIS Pro; this includes any feature classes that participate within the geometric network.

  • When replicating network datasets and terrains, only the feature classes used to build these data structures can be replicated. The actual terrain data structures, terrain, and network datasets are not replicated. For feature classes that participate in a network dataset or terrain to be replicated, they must be registered as versioned and meet data requirements for replication. You can rebuild the terrain or network dataset in the child replica's geodatabase after replica creation.

Trace network dataset administration—ArcGIS Pro | Documentation

          ArcGIS platform compatibility

  • It is important to be aware of the compatibility between ArcGIS clients, the geodatabase, and the trace network dataset when working with various versions. Trace networks in an enterprise geodatabase use a services-based architecture and are dependent on both the ArcGIS Pro and ArcGIS Enterprise client versions to enable new functionality.

Create a trace network—ArcGIS Pro | Documentation

Publish and consume services with a trace network—ArcGIS Pro | Documentation

  • The Trace Network works only with Branch Versioning.
  • Thus, Trace Network does not support Traditional Versioning.
  • Therefore Trace Network does not support Geodatabase Replication.
  • The alternative is to use feature service sync with Trace Network 

In ArcGIS Pro you can use feature service sync.

Feature service sync vs. geodatabase replication

  • Taking a map offline using the feature service sync capability copies data from a web service (feature service) to a local mobile geodatabase, whereas geodatabase replication uses enterprise and file geodatabases. The key benefit of taking a map offline using feature service sync capabilities is the ability to synchronize data multiple times versus the checkout geodatabase replica type, where changes can be synchronized only once.

Read more under Introduction to distributed data—ArcGIS Pro | Documentation

You can take a map offline with feature service sync.

--------------------------------------------------------------------------------------------------------------

Take a map offline with feature service sync capability

The sync capability available for ArcGIS Server feature services and hosted feature layers allows you to take feature layers offline in a web map that is configured for offline use. When the data is taken offline, the layers reference a local copy of the data. This allows you to make edits and complete your work without the requirement to be connected to the network. Once network availability is restored, you can upload your local edits.

When you enable sync on a feature service (feature layer), you can also use it in a distributed collaboration.

Before you publish an ArcGIS Server feature service to be used offline, you must configure the data to meet offline requirements.

Feature service replicas

Feature service replicas provide the mechanism that allows you to synchronize offline feature layers with the source data. The feature service replica receives edits made offline that are subsequently synchronized to the source feature layer. During synchronization, the feature service replica also receives the edits made in the source feature layer and makes them available to the feature layer that was taken offline.

When you take ArcGIS Server feature service data offline, a feature service replica is always created.

Tip:

Depending on the data present in the feature service and the options used when you publish the service, a replica version may also be created and associated with the feature service replica. To learn more about scenarios when a replica version is created, see Prepare data for use in offline feature services.

-----------------------------------------------------------------------------------------
What is a trace network?—ArcGIS Pro | Documentation

What is a utility network?—ArcGIS Pro | Documentation

-----------------------------------------------------------------------------------------

Helpful Utility Network Links (esri.com)

Getting started with ArcGIS Utility Network

Journey to the Utility Network: First Steps (esri.com)

Learning about the ArcGIS Utility Network

-----------------------------------------------------------------------------------------
Configuring Branch Versioning in ArcGIS | Esri Training Instructor-Led Course

Configuring Utility Networks in ArcGIS | Esri Training Instructor-Led Course

Working with Utility Networks in ArcGIS | Esri Training Instructor-Led Course
-----------------------------------------------------------------------------------------
I hope this answers your question.

| Marcelo Marques | Principal Product Engineer | Esri |
| Cloud & Database Administrator | OCP - Oracle Certified Professional |
I work with Enterprise Geodatabases since 1997.
“ I do not fear computers. I fear the lack of them." Isaac Isimov

View solution in original post

1 Reply
MarceloMarques
Esri Regular Contributor

Short Answer:

  • Geodatabase replication is built on top of traditional versioning and uses versioning functionality to synchronize data in most scenarios.
  • Branch versioning is not supported for any data source in any geodatabase replica type.
  • The Trace Network works only with Branch Versioning.
  • Thus, Trace Network does not support Traditional Versioning.
  • Therefore Trace Network does not support Geodatabase Replication.
  • The alternative is to use feature service sync with Trace Network 

Detailed Answer:

Introduction to distributed data—ArcGIS Pro | Documentation

  • Geodatabase replication is built on top of traditional versioning and uses versioning functionality to synchronize data in most scenarios.
  • For a list of supported datasets and limitations of geodatabase replication in ArcGIS Pro, see Replication and geodatabase compatibility.
  • Branch versioning is not supported for any data source in any geodatabase replica type.

MarceloMarques_1-1694726705940.png

  • ArcGIS Desktop (ArcMap / ArcCatalog) Geometric Network is deprecated in ArcGIS Pro.
  • In ArcGIS Pro you need to migrate to Trace Network or the new Utility Network.
  • Trace Network / Utility Network is the modern technology and only works with Branch Versioning.
  • Trace Network / Utility Network is not supported with Geodatabase Replication.

Geodatabase Replication with advanced geodatabase datasets—ArcGIS Pro | Documentation

  • Geometric networks are read-only and are not supported in a replica created in ArcGIS Pro; this includes any feature classes that participate within the geometric network.

  • When replicating network datasets and terrains, only the feature classes used to build these data structures can be replicated. The actual terrain data structures, terrain, and network datasets are not replicated. For feature classes that participate in a network dataset or terrain to be replicated, they must be registered as versioned and meet data requirements for replication. You can rebuild the terrain or network dataset in the child replica's geodatabase after replica creation.

Trace network dataset administration—ArcGIS Pro | Documentation

          ArcGIS platform compatibility

  • It is important to be aware of the compatibility between ArcGIS clients, the geodatabase, and the trace network dataset when working with various versions. Trace networks in an enterprise geodatabase use a services-based architecture and are dependent on both the ArcGIS Pro and ArcGIS Enterprise client versions to enable new functionality.

Create a trace network—ArcGIS Pro | Documentation

Publish and consume services with a trace network—ArcGIS Pro | Documentation

  • The Trace Network works only with Branch Versioning.
  • Thus, Trace Network does not support Traditional Versioning.
  • Therefore Trace Network does not support Geodatabase Replication.
  • The alternative is to use feature service sync with Trace Network 

In ArcGIS Pro you can use feature service sync.

Feature service sync vs. geodatabase replication

  • Taking a map offline using the feature service sync capability copies data from a web service (feature service) to a local mobile geodatabase, whereas geodatabase replication uses enterprise and file geodatabases. The key benefit of taking a map offline using feature service sync capabilities is the ability to synchronize data multiple times versus the checkout geodatabase replica type, where changes can be synchronized only once.

Read more under Introduction to distributed data—ArcGIS Pro | Documentation

You can take a map offline with feature service sync.

--------------------------------------------------------------------------------------------------------------

Take a map offline with feature service sync capability

The sync capability available for ArcGIS Server feature services and hosted feature layers allows you to take feature layers offline in a web map that is configured for offline use. When the data is taken offline, the layers reference a local copy of the data. This allows you to make edits and complete your work without the requirement to be connected to the network. Once network availability is restored, you can upload your local edits.

When you enable sync on a feature service (feature layer), you can also use it in a distributed collaboration.

Before you publish an ArcGIS Server feature service to be used offline, you must configure the data to meet offline requirements.

Feature service replicas

Feature service replicas provide the mechanism that allows you to synchronize offline feature layers with the source data. The feature service replica receives edits made offline that are subsequently synchronized to the source feature layer. During synchronization, the feature service replica also receives the edits made in the source feature layer and makes them available to the feature layer that was taken offline.

When you take ArcGIS Server feature service data offline, a feature service replica is always created.

Tip:

Depending on the data present in the feature service and the options used when you publish the service, a replica version may also be created and associated with the feature service replica. To learn more about scenarios when a replica version is created, see Prepare data for use in offline feature services.

-----------------------------------------------------------------------------------------
What is a trace network?—ArcGIS Pro | Documentation

What is a utility network?—ArcGIS Pro | Documentation

-----------------------------------------------------------------------------------------

Helpful Utility Network Links (esri.com)

Getting started with ArcGIS Utility Network

Journey to the Utility Network: First Steps (esri.com)

Learning about the ArcGIS Utility Network

-----------------------------------------------------------------------------------------
Configuring Branch Versioning in ArcGIS | Esri Training Instructor-Led Course

Configuring Utility Networks in ArcGIS | Esri Training Instructor-Led Course

Working with Utility Networks in ArcGIS | Esri Training Instructor-Led Course
-----------------------------------------------------------------------------------------
I hope this answers your question.

| Marcelo Marques | Principal Product Engineer | Esri |
| Cloud & Database Administrator | OCP - Oracle Certified Professional |
I work with Enterprise Geodatabases since 1997.
“ I do not fear computers. I fear the lack of them." Isaac Isimov