Sewer Utility Network - redundant feature classes getting created when creating utility network

1257
1
Jump to solution
12-07-2020 10:50 AM
Labels (1)
Haritha
New Contributor

Hello,

We are trying to build a sewer utility network. We followed instructions from:

https://solutions.arcgis.com/water/help/sewer-utility-network-foundation/get-started/get-started-ove...

We are using ArcGIS Pro 2.6.3, untools package 2.6.0, and dltsolutions package 2.6.0.

We downloaded all required components, including the asset package.

We created a template geodatabase (schema only asset package) from the Sewer Asset package – in file Geodatabase.

We migrated the sewer data using the DLT solutions. The original layers (SewerDevice, SewerLine, Service Territory etc.) from the schema only asset package were populated with our sewer data.

We skipped the step of creating enterprise geodatabase.

When we created utility network in file geodatabase (Using “Create Utility Network” tool), specifying the right data set, and service territory, the tool generated layers with “_1” in the end that participated in the network – e.g. SewerDevice_1, SewerLine_1…

The original layers that consisted of our data, are not part of the network.

In the end, we are not able to use the feature classes that were populated with the data to be part of the Utility network.

Please let us know if there is anything that is wrong or missing in the above workflow, or if this is an expected behavior?

Thanks for your input.

Sincerely,

Haritha

0 Kudos
1 Solution

Accepted Solutions
PaulLeBlanc1
Esri Contributor

Did you create the Utility Network in the asset package? You need to create the UN in a separate file geodatabase and then apply the asset package to that.

https://solutions.arcgis.com/utilities/help/utility-network-automation/tool-reference/asset-package-...

This will help you configure it.

View solution in original post

1 Reply
PaulLeBlanc1
Esri Contributor

Did you create the Utility Network in the asset package? You need to create the UN in a separate file geodatabase and then apply the asset package to that.

https://solutions.arcgis.com/utilities/help/utility-network-automation/tool-reference/asset-package-...

This will help you configure it.