Hello,
my subnetwork definition has the following condition barriers :
- lifecycle_status is different from "in service"
- category is "ground"
Problem : I want to include the ground features in my subnetwork's features so that they have a subnetwork name and can be exported to the ADMS, but I don't want to include out of service features (like cables) that could be connected to an in service part of the network.
Is there a way to achieve this ?
Solved! Go to Solution.
@PierreloupDucroix - You can achieve this by using the trace tool and selecting the Include Barrier Features option.
Then there are two ways of limiting what barrier features are output
1)Delecting the Output Asset Types = The assets you are interested in.
2)Using Output Conditions and setting the condition to return all features except the ones where "Lifecycle Status != Out of Service"
But in saying that, I assume you are using the export subnetwork tool for your ADMS exports which doesn't present any options to selectively output the barriers.
Also in the Set Subnetwork Definition tool if you "include barrier features = true" there is not way to selectively output the barriers.
I reckon the ideal solution here is to use the EXPORT SUBNEWORK REST API.
The rest API call allows you to define a trace configuration where you can use one that is set only to output a certain type of barrier (use the config at the start of this answer)
https://developers.arcgis.com/rest/services-reference/enterprise/exportsubnetwork-utility-network-se...
Last option is to remove these feature in post process. Whatever you might be using to create the input for your ADMS CIM adapter, FME, python scripts?)
@PierreloupDucroix - You can achieve this by using the trace tool and selecting the Include Barrier Features option.
Then there are two ways of limiting what barrier features are output
1)Delecting the Output Asset Types = The assets you are interested in.
2)Using Output Conditions and setting the condition to return all features except the ones where "Lifecycle Status != Out of Service"
But in saying that, I assume you are using the export subnetwork tool for your ADMS exports which doesn't present any options to selectively output the barriers.
Also in the Set Subnetwork Definition tool if you "include barrier features = true" there is not way to selectively output the barriers.
I reckon the ideal solution here is to use the EXPORT SUBNEWORK REST API.
The rest API call allows you to define a trace configuration where you can use one that is set only to output a certain type of barrier (use the config at the start of this answer)
https://developers.arcgis.com/rest/services-reference/enterprise/exportsubnetwork-utility-network-se...
Last option is to remove these feature in post process. Whatever you might be using to create the input for your ADMS CIM adapter, FME, python scripts?)
Thank you,
indeed, I am using the export subnetwork but with ARCGIS API, and I can see that the same parameters as REST API are exposed. It may be a good solution !
I can also see in the export subnet tool, that there is a "Result Network attribute" parameter that may help identify features that are "out of service" in post process, unfortunately there is no "Result network category" option to identify specific categories such as "ground" or others.
Regards
You are right, there is no "Result network category" but you could add the Asset Group and Asset Type to Result attributes and use those to identify the features that would make up "Ground" network category.
Not the most straight forward solution.
In fact, asset group and asset type seem to be a base result for features in the json :
{
"networkSourceId" : 9,
"globalId" : "{D14E41F9-3B84-4993-BF25-B3BA5F4ADB12}",
"objectId" : 44156,
"terminalId" : 1,
"assetGroupCode" : 14,
"assetTypeCode" : 14,
"networkAttributeValues" : [
{
"E:Cycle de vie" : 2
}
]
},
I will have to rework the CIM exporter in order to take this into account
Perfect! You can also use the "Include domain descriptions" options if that makes things easier.
All the best 🙂
Also just out of curiosity - what CIM exporter do you use?
👍
We developed a custom python exporter