CP subnetwork lines exclude services and CP wire

[EdwardBlair]

I'm building CP subnetworks and noticed that the service lines (and CP wires) have a cpsubnetwork name assigned, but are not included in the subnetwork line geometry.    Is this by design?  Is there some configuration to the "Update Subnetwork" GP tool that controls this?

I'm not saying this is necessarily a bad thing.  I'd just like to understand it.

Thx,

Ed

[MikeMillerGIS]

Aggregating service lines is a bad idea. It creates a very vertex dense subnetline.

[RobertKrisher]

The asset types used to generate the subnetwork line are specified in the subnetwork definition for the tier. We typically recommend that the aggregated subnetwork line only include the most significant features in the network (high/medium voltage/pressure) because including all the lines creates very dense subnetwork lines that can take up a lot of storage and cause performance issues over time.

Consider that you're creating a full copy of all your line geometries every time you update that subnetwork. It can cascade when considering hierarchical networks that do this for multiple tiers (isolation, pressure, dma, system).

[EdwardBlair]

I understand the downside of include *many* lines in an aggregated subnetwork line.   

But, and sorry to be thick here, I just don't see how the asset groups/asset types that *are* included in the aggregated subnetwork line are defined.  I *do* see in the subnetwork tier definition the devices to be included, but not the lines to be aggregated.

[EdwardBlair]

I can see that.   Is this controllable in any way, or is that just the way it works?

[RobertKrisher · Accepted solution]

@EdwardBlair Keep scrolling through the valid features and objects group. This is configurable by using the Aggregated Lines For SubnetLine Feature Class parameter of the Set Subnetwork Definition tool.

[EdwardBlair]

Perfect!   Thank you.  Just what I was looking for.