Best Practices for Storing data outside of the Utility Network

Question

Hello everyone,

We are in the process of migrating to the Utility Network, and while we have successfully mapped all network classes to their respective asset groups and asset types, we still need to determine the best approach for storing non-network data.

In our current setup (ArcGIS 10.8.1 with geometric network), we store non-network data such as special property rights (polygons), landbase datasets, cadastral data, non-spatial tables for maintenance reports etc. All this in the same enterprise geodatabase but within separate datasets. As we transition to the Utility Network, we want to follow best practices for storing this type of data in the new environment.

Specifically, we are looking for guidance on:

* Database structure: Should non-network data be stored in the same database as the Utility Network but in a separate dataset, or is it better to use a separate database?
* Versioning: We plan to use branch versioning for all data, not just Utility Network feature classes. However, some of these non-network datasets require versioning, while others do not. What is the recommended approach for handling versioning in such cases?

Any insights or best practices from those who have handled similar migrations would be greatly appreciated.

Thanks in advance!

RPGIS · Answer

You can make edits to them simultaneously because the features are in different datasets using different versions.

To clarify, if a feature class in a dataset is versioned using traditional then the other feature classes in the same dataset cannot be set to batch. If there are feature classes in the same database but in separate datasets with one using traditional versioning methods and another using batch then both features can still be edited.

CherylTrine · Answer

I want to make sure I understand.  I know all feature classes within a dataset must use the same type of versioning.  Suppose I have a utility network which uses branch versioning, another dataset in the same database which uses traditional versioning (e.g., building info containing feature classes for footprint, levels, spaces, etc.) , and a feature class that is not within a feature dataset that uses traditional versioning.  Can I edit features from the utility network and building info simultaneously?

RPGIS · Answer

It is possible to use both branch and traditional but it mostly depends of how the datasets and/or feature classes are set up. You can have one set of features outside a dataset use a different editing version than features within a dataset. You can't edit simultaneous features within a dataset using different versioning methods.