Re: Utility and Pipeline Data Model 2023 がリリースされました

Question

皆さん、こんにちは、

UNM と Pipeline Referencing データを含む動作モデルはダウンロード可能でしょうか？

Naperville UPDM ソリューションをダウンロードし、ArcGIS Pro で Asset Package FGDB と付随するマップを表示できました。Pipeline* のフィーチャークラスのみがデータを持っているようです。untols を使って UPDM アセットパッケージを FGDB に展開でき、サブネットワークの構築や UN トレースの実行も可能でした。しかし、すべての P_ テーブル／クラスは空で、ルートやイベントがありません。このようなデータは利用可能でしょうか？それとも SubnetLine を使ってルートを作成し、イベントをルートに沿って一つずつ追加することが期待されているのでしょうか？UPDM の LRS 側の構築に関するドキュメントはありますか？

ありがとうございます、

Vish

Ayan Palit · Answer

@VishApte_NGIS The background helps; looks like a challenging project is at hand. There are knowledge gaps in the approach mentioned. Recommend your team get the right training and guidance for the design and implementation.

A good starting place: ArcGIS Pipeline Referencing - Useful Resources

*  Step 6 Create LRS Network From Existing Dataset should be used with Engineering Network or Continuous Network. Looks like you used with PipelineLine.
* Step 8 seems to use PipelineLine to load into new LRS network layer. Review the LRS data model requirements and format the LRS network data accordingly.

VishApte_NGIS · Answer

@AyanPalit

Thanks  for your prompt response.

As a background for my exercise, I am trying to document the exact steps to convert our Pipeline geometric network for Oil and Gas transmission into UPDM model with PipelineLine as the sole contributor for LRS centerline. We already have attributes like Pipeline ID, Pipeline System Name and From Date etc. in Pipeline FC but do not have measures. I intend to bring Calibration Points using Kilometre Posts layer. And we have feature classes like Inspection Points, Leak Survey etc. in the GN geodatabase that will act as events. Just not sure the exact migration and deployment steps to UPDM with LRS enabled. I could build standalone UNM model easily. But struggling a little with LRS part of UPDM.

I got up to Step 8 with following.

* Step #3: Used “Create LRS from Existing Dataset tool” with PipelineLine feature class.
* Step #4 skipped because it is applicable for Create LRS tool.
* Step #5: Ran "Configure Utility Network Feature Classes" successfully providing PipelineLine, PipelineDevice and PipelineJunction feature classes and relevant attributes.
* Step #6: Ran “Create LRS Network” successfully. (Tried initially with “Create LRS Network From Existing Dataset” but failed for PipelineLine param with error “This feature class is already registered with an LRS.")
* Step #7: Run “Create LRS Event From Existing Dataset" tool successfully and added “P_DocumentPoint” and “P_GasLeak” as point events and “P_InlineInspection” as linear event.
* Step #8: I am stuck here with Append Routes part. The PipelineLine fc data is somehow non-compliant as Route. To allow route creation, I assigned route name value of "Naperville Transmission System" to only transmission pipes (AssetGroup=3) in PipelineLine feature class. And I set "FromDate" to "1st June 2026", left "ToDate" null. I left RouteID and CenterlineID null as well. The data snapshot below:

In the tool's params, I am using "Route Name" as Load Field since Route ID is left null. I also ensured I have only transmission pipes with non-null values for route name and from date set are selected in a map. And then I ran the tool with parameters as below.

But the route load fails for all selected lines, text file has below details:

The following duplicate route IDs with an overlapping time representation were found in the source data. A route ID must only have one representation at a given point in time.

Object ID Route ID Route Name From Date To Date
2196 '{F37593A9-6542-452E-B3A8-37CEA5557CBD}' 'Naperville Transmission System' 1/06/2026 NULL
2197 '{F37593A9-6542-452E-B3A8-37CEA5557CBD}' 'Naperville Transmission System' 1/06/2026 NULL

(It looks like the tool generated Route ID value)

Any idea where I am going wrong?  I am kind of stuck.

Thanks in advance.

Cheers,

Vish

Ayan Palit · Answer

@VishApte_NGIS

* Step 3 "Create LRS from existing dataset" tool, should use "PipelineLine"? This is discussed in the Requirements section of  Manage Pipeline Referencing and a utility network together
* Step 5 P_Centreline is typically not used and is substituted by PipelineLine in the ArcGIS Pipeline Referencing and ArcGIS Utility Network integration pattern.
* LRS data is not provided with the asset package; these need to be created by the user. A sample geodatabase for APR is available at:  Get started using APR Foundation
* PipelineDevice and PipelineJunction are managed by Utility Network and hence should not be expected to work as LRS events.