Based on recommendations from ESRI, when deploying a Utility Network it's recommended to use the pipeline line as the centerline. Conceptually, I agree with this approach as editing the centerline to match the geometry of your recently created pipeline edits is a bit redundant. However, I have not been able to successfully deploy LRS in an enterprise geodatabase using the pipeline line as the centerline.
I was able to create the LRS and create the LRS network in the EGDB successfully, but the process fell apart when I tried to append the routes.
I followed the steps outlined by ESRI
- Applied an Asset Package
- Create LRS from Existing Dataset using UPDM feature classes and P_PipelineLine as the centerline
- Configure Utility Network Feature Class
- Create LRS Network From Existing Dataset
- Append Routes
The Append Routes failed to load anything and was stuck at 0%.
My understanding of Append Routes is that it does 3 things.
- Appends routes into Continuous Network or Engineering Network depending on deployment
- Updates the centerline
- Updates the centerline sequence table to associate routes to the centerline
I believe mine is failing because in our ETL process, pipeline line already has data for transmission. I don't want to append data into pipeline line using append routes. I am wondering if ESRI has come across this issue before?
Can I append both the Network and the Centerline Sequence table instead of using the append routes tool?
We are using ArcGIS Pro 3.1 and Enterprise 11.1
Your help is much appreciated 🙂
