nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Las líneas de subred CP excluyen servicios y cables CP

EdwardBlair

Estoy construyendo subredes CP y noté que las líneas de servicio (y los cables CP) tienen un nombre de cpsubnetwork asignado, pero no están incluidas en la geometría de la línea de subred. ¿Es esto por diseño? ¿Hay alguna configuración en la herramienta GP "Update Subnetwork" que controle esto?

No digo que esto sea necesariamente algo malo. Solo me gustaría entenderlo.<\/P>

Gracias,

<\/span><\/P> <\/P>

Encuentra más publicaciones etiquetadas con

Gas

Accepted answers

RobertKrisher

@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.

All comments

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 can see that. Is this controllable in any way, or is that just the way it works?

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.

RobertKrisher

EdwardBlair

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

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.