Latest Contributions by JonDeRose

‎07-20-2022

David, At the current time, unfortunately, there is a known limitation with using the Display Flow Direction Arrows UI command with Trace Network Services. Flow direction is persisted as a network attribute with TN version 2 and later so this can still be used to display flow direction by changing the symbology of the lines in the network to use this field to symbolize the lines. To make this easier I've attached a sample .lyr file containing the default symbology for flow direction as you would see within a TN on a file or mobile geodatabase. To apply this: 1. Right-click the line feature class in the trace network for which you want to display flow arrows and select Symbology. 2. In the Symbology pane that opens, select the Flow direction field under Unique values to display the 3 symbol classes and then select Import Symbology from the burger button at the top right. 3. In the Apply Symbology From Layer GP tool, set the class you want to apply symbology to in the Input Layer (should already be set) and navigate to the FlowDirectionSymbology.lyrx provided as the Symbology Layer. 4. Set the Symbology Fields as below and leave others as default, nd click Run: - Type: Value field - Source field: FlowType - Target Field: Flow direction This updates the symbology of the lines class to use the flow arrows imported. I use this layer (Alias renamed to Arrows in below screenshot) to display flow by toggling the layer on and off as needed in the Contents pane. I also disable the selectability on this layer. I then use another copy of the line for general display. We are working to address this in a future release but I hope this helps you move forward with the ability to display flow in the meantime. Jon

‎07-14-2022

@GardenKo I am sorry to hear of your frustration. Are you working within a services based environment or single user geodatabase? When working with a trace network in a single user geodatabase (File GDB) the FEATUREGLOBALID field can be used but is not required. Instead, the geometry of the input feature class can be used to intersect the network feature's geometry and place starting points or barriers. This is one approach you could take, but for this to work you would need to remove the FEATUREGLOBALID field from the class. When the FEATUREGLOBALID field is present you can create user-defined starting points and place these on line (edge) or point (junction) features with the corresponding network feature's GLOBALID as you specified; however, the issue you are encountering is due to the placement of the starting location on an edge feature... To use FEATUREGLOBALID for the placement of user-defined starting points and barriers on edge features we must also supply a PERCENTALONG field of type double. This tells the trace the location of the starting point or barrier along the edge. When the PERCENTALONG field is not provided, the starting point/barrier is assumed to be a junction feature instead. Please add a PERCENTALONG field (double) and provide a value between 0 and 1 or test removal of the FEATUREGLOBALID field to use the input class geometry to intersect the network feature's geometry This is an omission from the documentation that I will get addressed. Please let me know if you are still having issues after testing the above. Thanks, Jon

‎07-12-2022

Good morning, Are you experiencing this issue when you also provide a traceConfiguration? Does this same trace complete as expected when run via ArcGIS Pro? Is the feature class associated with this GlobalID part of the trace network?

‎07-12-2022

Good morning @EvelynHsu - If you were to double click the published trace network service under the Portal tab in the Catalog pane does this expose the trace network service. You should be able to right-click this and add to a map.

‎05-17-2022

Moved:

Moved to Field Maps Questions

‎03-07-2022

@JonathanDaweEsriUK Nested containment is supported ( i.e. For example, a substation can contain a junction box, and the junction box contains electrical devices...) ; however, we do not allow for a point feature/junction object to be contained by more than one container. I have created an issue internally to improve the documentation and clarify supported containment configurations.

‎01-26-2022

@GIS_Solutions Are you running into this issue with UN on File Geodatabase or Enterprise? I beleive this is file... The issue is likely with the index on SubnetLine. Could be a result of the current update adding a very large subnetwork to a class previously populated with much smaller features. Agree with @Anonymous User above that dropping the spatial index, running Update Subnetwork, and then recreating the index should allow you to move past this.

‎12-20-2021

Good morning @RandyCasey If I am reading your post correctly...there is no requirement to downgrade ArcGIS Pro to manage earlier versions of the utility network dataset. We are in the process of updating the matrix you reference to clarify compatible releases as it can be read that management of a dataset such as UNv3 is tied to a specific version of Pro (but this is not the case). When this matrix was authored, the intent was to display the UN version created using the listed combination of companion releases (i.e Pro 2.5 creates a version 3 UN which requires ArcGIS Enterprise 10.7 or later.) This would be better represented by stating that the compatible versions for a Utility Network Version 3 are Pro 2.4 and later and Enterprise 10.7 and later. Two general rules from ArcGIS Platform Compatibility Later versions of ArcGIS Enterprise can share earlier versions of the utility network. Later versions of ArcGIS Pro can be used to view and edit earlier versions of the utility network. You can use any version of ArcGIS Pro to connect and work with the utility network in ArcGIS Enterprise as long as the Utility Network Version is supported by that release. To provide a couple examples, I could ArcGIS Pro 2.9 with a Utility Network Version 4 in ArcGIS Enterprise 10.8.1 or later because both Pro and Enterprise are compatible with version 4 UN's. Earlier releases cannot open utility network datasets that participate in newer functionality. For example, you cannot use ArcGIS Enterprise 10.7 to share a Utility Network Version 4 or consume a Utility Network Version 5 using ArcGIS Pro 2.6. Likewise I could use ArcGIS Pro 2.8 with a Utility Network Version 3 in ArcGIS Enterprise 10.9 because this version of the UN dataset is supported with Pro 2.4 and later as well as Enterprise 10.7 and later. Beginning with ArcGIS Pro 2.7 in an enterprise deployment, the version of ArcGIS Pro and ArcGIS Enterprise determines the Utility Network Version when you create a new utility network or upgrade and existing one; however, this only governs the version created, not the versions that can be used to interact with the dataset. Let's say you were using ArcGIS Pro 2.7, an earlier version of the UN dataset (such as Utility Network version 4) could still be created if you were connected to an earlier version of ArcGIS Enterprise (such as Enterprise 10.8.1). I hope that helps to clarify, if I have misunderstood please let me know. Jon

‎11-18-2021

Hi Robert, Yes, the fix for this issue was included with 2.9 and the recent 2.8.2 patch.

‎11-02-2021

Good day Luca, What version of ArcGIS Pro are you working with? The current lesson was authored with ArcGIS Pro 2.8; however, an earlier version created with ArcGIS Pro 2.5 is also available here which uses a Utility Network version 3. Thanks, Jon

‎08-06-2021

Hello Bryce, I have not come across this when converting geometric networks. Are you still encountering this issue? Is this reproducible?

‎08-06-2021

@GavinRunyon While it sounds as though it has the potential to cause confusion when placing trace locations and interpreting trace results due to the duplication of features, the current method of modeling would not flag these as errors as the two lines would not technically be connected, each would remain modeled as its own edge feature.

‎08-05-2021

@curtvprice We have a couple of ArcGIS Learn lessons in the planning stages at the moment to cover various usage scenarios. Within one, we aim to cover the conversion process, taking an NHD dataset and converting the existing geometric network into a trace network. Is this what you refer to when you mention a "tutorial of how to load NHD into the trace network." ?

‎07-21-2021

When you have an edge (line) connected to another edge midspan, as long as they share the same AG/AT the same principle applies because we are focused on edge elements instead of the line (edge) feature itself. In scenario 1 and 3, a system junction is placed (hidden) midspan on the line, updating the line to be composed of multiple edge elements. So, in this scenario the two edge elements share the same endpoint. For connectivity to be established midspan in the first place you need to ensure the line feature supports midspan connectivity by setting the edge connectivity policy for the AG/AT. A picture using your example 3 might explain it better: Another way of looking at it. When a line in the utility network has another feature connected midspan, it creates another edge element for the line. Edge elements compose the logical component of edge (or line) features in a utility network. A complex edge (which all UN line features are)... is a feature is associated with a set of junction and edge elements in the logical network. Hope that helps to clarify.

‎07-21-2021

@GavinRunyon If two edge elements share the same endpoint and have the same Asset group and Asset type, these features can connect without a user-defined intermediate junction or network rule. In this situation, a system junction is created and connectivity is established when the network topology is validated or enabled. If I understood your question properly, it sounds like your Water Line subtype Services share the same Asset group and Asset type. As a result they could be connected to each other without the creation of a specific network rule to model the split. The feature restrictions topic covers this in a little more detail. Thanks, Jon

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by JonDeRose

Re: Display Flow Direction in Trace Network serviced

Re: Using user-defined starting points as input when tracing

Re: How to Get the right global id for the trace newwork server?

Re: Problems with Published Trace Network Service

Utility Network map server pop ups not working in Field Maps

Re: Containment Error: The point feature/object is already content.

Re: ERROR 160189: The spatial index grid size is invalid

Re: Stop tying Utility Network versions to ArcGIS Enterprise or provide the option to choose your version from Pro

Re: Creating a Trace Network-160310: The spatial references do not match

Re: Unable to create Features in GettingtoKnow - Utility Nework Project

Re: Convert geometric network to trace network failed - error 001841

Re: Water Utility Network Rules allow Water Line Service to connect to Water Line Service?

Re: Trace Network - FAQ

Re: Water Utility Network Rules allow Water Line Service to connect to Water Line Service?

Re: Water Utility Network Rules allow Water Line Service to connect to Water Line Service?

Re: Apply Asset Package on UnTools/Pro 3.3 require...

Re: junction-edge from/to connectivity and relati...

Re: Error ArcGIS Pro 3.3 Terminal Connections Mult...

Re: Publishing a File Geodatabase based Utility Ne...

Re: Is it manageable to make something like Up&Dow...