Accepted Solutions
Here is a version of the subnetwork aggregator that might work for this use case.
You must create a trace configuration based on the subnetwork definition, but select Include Container. Add a tag to that Configuration call SubnetworkOverride and then another tag, this one can be anything.
This toolbox also has the trace to trace config tool which will help set up the trace config. Fill out a Subnetwork Trace with the properties you want, make sure to select Include Containers. Copy that python and you can input that into the trace to trace config tool(in the same attached toolbox). Make sure to fill out the tags of SubnetworkOverride and something else. Tags are separated by new lines, not commas.
You will select that other tag when you run the tool
We cannot do this with update subnetwork, but we can do this with a Trace. You can run a subnetwork trace and select Include Containers and Aggregated Geometry. This will return a line for the containers, so the cables, the strand is in.
We have created a tool, that will build the aggregated geometry for your subnetworks, but it does not allow you to override settings of a subnetwork definition, but we could look at exposing that if that will help you
We also have a batch trace that might work too, but that uses a trace configuration, so we would need to make a trace configuration per subnetwork definition, that includes content, and then you would need to pass a series of starting points into it. I am leaning towards providing some overrides in the Subnetwork Aggregator
You can find Batch Trace and Subnetwork Aggregator here - https://github.com/Esri/Utility-Data-Management-Support-Tools
Thanks a lot for the quick response, I appreciate it :).
I tried to use the tool you recommended but, unless I messed something up, the result is a geometry with length 0.
I believe that in the hierarchical communication network that uses strands as non-spatial objects it is really useful to be able to visualize the subnetlines as feature, built with the related strand (cable) containers like trace does. Could be a new idea 🙂
Anyway, Thank's again.
Here is a version of the subnetwork aggregator that might work for this use case.
You must create a trace configuration based on the subnetwork definition, but select Include Container. Add a tag to that Configuration call SubnetworkOverride and then another tag, this one can be anything.
This toolbox also has the trace to trace config tool which will help set up the trace config. Fill out a Subnetwork Trace with the properties you want, make sure to select Include Containers. Copy that python and you can input that into the trace to trace config tool(in the same attached toolbox). Make sure to fill out the tags of SubnetworkOverride and something else. Tags are separated by new lines, not commas.
You will select that other tag when you run the tool
What are you trying to achieve? If you want your subnetline to have geometry, you must update your subnetwork definition to include distribution mains. You are only aggregating transmission mains now. The Subnetwork Aggregator will not change your subnetline, it will create a new output GDB.
Also, the Subnetwork Aggregator should be showing a dropdown if it finds the trace configurations, like this:
I am not sure why it is not. You need both the SubnetworkOverride tag and another tag to display.
Dear MikeMiller,
Thanks a lot for your solution. It's really useful.
Unfortunately the necessary option "include up to first spatial content" which allows to select only cables that contain strands (excluding structure) is avaiable only for Trace configuration tool, not for set Subnetowrk Definition in whitch there is only the "include container" option. The result of your "subnetwok aggregator" tool polyline then includes the structure, not only the cable that is the necessary container.
For better understandig the first is the result of aggregator (green line - 11 part), and the second the trace (selection - 3 cable):
Chiara
