Latest Contributions by RobertKrisher

‎11-06-2023

For item #3 you should always buffer out your service territory with room for expansion, but having an unnecessarily large service territory will impact the default grid sizes for your spatial index (database dependent, but you may need to adjust them after deploying), it will also prevent us from being able to leverage certain performance optimizations during validate network topology.

‎11-06-2023

The trace is stopping at that barrier but because your result type is a selection it appears like the whole line is included (because ArcGIS Pro doesn't allow us to select segments of a line). If you want to show partial geometry results try using the "aggregated geometry" result type, this will produce a new set of layers that will include partial edges without requiring you to split your source lines.

‎11-06-2023

Can you provide an example of the use case you are trying to solve by tracing a structure? Tracing allows the utility network to analyze the connectivity of the network topology. Only features in a domain network have connectivity that you can trace. When analyzing structures, the system performs the network analysis on connectivity then looks at the attachment and containment associations they have with the resulting network features how they support the connectivity of the network. Off the top of my head I can think of a couple of purely structural type analysis, so I'm curious to hear what your use case is.

‎10-31-2023

@GIS_Solutions The easiest way would be to export your data to an asset package and delete any rows out of the C_Subnetworks table that you don't want. You're only other option would be to use the ArcGIS API for Python (or other code) to access the REST endpoint of the utility network and call Disable Subnetwork Controller—ArcGIS REST APIs | ArcGIS Developers. We don't let you edit the subnetworks table directly to mark subnetworks as dirty.

‎10-27-2023

In a sink-based network, the 'highest rank' tier is the ultimate destination for resources in your network. So, for a sewer utility network, the wastewater treatment plant is a subnetwork controller for the sewer collection system (tier 1). Any of the sewershed areas within the sewer collection system are tier 2. The current stormwater model only has a single tier, but if it did have two tiers then the terminal discharge points in your system would be tier 1 and any minor outfalls would be tier 2. Ranks are discussed in several pages in the documentation (Tiers—ArcGIS Pro | Documentation, Network hierarchies with tiers—ArcGIS Pro | Documentation). We'll work on making the documentation more precisely differentiating the language for source-based and sink-based domain networks.

‎10-25-2023

Question originally asked by @DominicCwalinski on 02-20-2020 06:38 AM Does anyone know of any free software/code which would allow me to generate a report like the picture attached here? Something that you can input where laterals are with distances and direction, run the software and code, and a report similar to the one uploaded would appear? It does not require all the information needed top, but the linear referencing of a line should occur. Capture.PNG

‎10-24-2023

Because these features have no geometry, the utility network has to create dirty areas for them somewhere. In these instances, it chooses the lower-left corner of the extent of your service territory. Once you correct the underlying features by either creating a geometry or deleting them you should validate your network topology with the full extent of your dataset to clear the error.

‎10-24-2023

Because this is specific to the utility network I am going to move this to the Utility Network channel.

‎10-23-2023

As long as you are adding the layer from your utility network feature service as a regular layer and not as a subtype group layer you can run the 'add join' tool on the layer, no problem. Join field would be problematic because it would change the schema (and you could only do it once). All the discussions about performance implications still stand, I just wasn't clear enough about using the individual layer from the feature service instead of a subtype layer from the subtype group layer.

‎10-23-2023

@shildebrand You should still be able to use a regular feature layer to do the join, but you will want to use a definition query to filter out any rows that aren't relevant or don't need to be updated (e.g. excluding everything but the relevant asset group or features whose z-value hasn't changed). You can also do the same thing using Python scripts or Python Notebooks (using either ArcPy or the ArcGIS API for Python), this would give you even more control over your analysis and which features to update.

‎10-23-2023

@GISUN An entire gas utility network can have multiple systems if it is large enough to have separate, disjoint areas of service (e.g. a western system that is not connected to an eastern system). The advantage of an asset belonging to multiple tiers is that it accurately reflects the real-world configuration of a network. Companies organize their data into these different subnetworks, and in the case of hierarchical networks these boundaries are either nested in each other (system, pressure, isolation zone) or overlap with each other (cathodic protection). If we required everything to be partitioned, then we would only be able to model one of these tiers as a subnetwork and everything else would have to be managed manually (or through customization).

‎10-23-2023

@GISUN In practical terms, a feature in a hierarchical network can belong to many subnetworks while a feature in a partitioned network can only belong to a single subnetwork, I provide industry-specific articles as well as some hands-on tutorials in this learning series. So, a gas pressure valve can belong to a gas system, a pressure zone, an isolation zone, and even a cathodic protection zone. An electrical customer only belongs to a single circuit.

‎10-23-2023

@GISUN If you need to refer to an attribute in order to control tracing or calculate summary statistics, you need to make it a network attribute. Normal attributes are not available in the Trace or Set Subnetwork Definition tools. With that being said, I recommend you download one of the Utility Network Foundations to learn how each industry uses different network attributes to control tracing and produce statistics for their subnetworks. If you want to include an attribute value in tracing/analysis it needs to be defined and validated as part of the network, this ensure that as we are loading the topology for analysis, we are also loading all the attributes required for analysis. You can imagine that if we didn't store this information with the topology and we needed to query individual features (or cache entire areas of the map) as we were evaluating the topology that this would be quite slow!

‎10-23-2023

@shildebrand Doing a calculate field against a feature service can be a slow operation if you're doing this on a lot of rows and can also bloat the size of your history tables if you don't narrow the scope of your calculation. If you're familiar with Python I can recommend a few techniques that will be more sustainable, otherwise if you're just doing this once and don't mind the pain you can try using a regular layer and just apply a definition query to it.

‎10-19-2023

This is not the expected behavior; I'd recommend you work with support to log an issue for this.

Online Status	Offline
Date Last Visited	10 hours ago

My Ideas

Latest Contributions by RobertKrisher

Re: Multiple service territory?

Re: stop trace at any vertex along the edge

Re: Set Structure feature as starting point

Re: ArcGIS Utility Network: Using programming to batch enable Subnetwork Controller

Re: Source VS Sink tier tanks

Help with Generate Sewer Lateral Inspections?

Re: I NEED HELP TO CLEAN THOSE MESSAGES IN ERROR INSPECTOR AND DIRTY AREA

Re: I NEED HELP TO CLEAN THOSE MESSAGES IN ERROR INSPECTOR AND DIRTY AREA

Re: Join Table to ArcGIS Utility Network Feature Service

Re: Join Table to ArcGIS Utility Network Feature Service

Re: benefits of network attributes

Re: benefits of network attributes

Re: benefits of network attributes

Re: Join Table to ArcGIS Utility Network Feature Service

Re: Isolation trace taking out entire subnetwork

Re: How to sync my Utility network geodatabase wit...

Re: Pre UN migration data cleanup workflows

Re: Best practices for managing and validating Uti...

Re: Pre UN migration data cleanup workflows

Re: Can one web map hold two separate utility netw...

European Utility Network Community (UNC)

APAC Utilities Community of Practice