Latest Contributions by JonDeRose

To add to Mike's response... If you were to run an aggregated geometry trace using the Synthesize Geometries parameter, this would also return aggregated geometry for the edge object or association from which you could derive length. Synthesize association geometry in a trace Synthesize geometry for edge objects in a trace ... View more

@ReyesAlami  You referenced you're working with ArcGIS Pro 3.3 and Enterprise 11.2.  When working within an enterprise deployment, the version of ArcGIS Pro and the portal's federated server are used to determine the compatible Utility Network Version.  UNv7 is supported starting with Enterprise 11.3 so this combination would create a UNv6.   Being that you are already at this version this is why you are seeing the "dataset is already upgraded". https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/utility-network-compatibility.htm     ... View more

@rlyding This appears to be a bug.  I will look into this further, and I'd recommend reaching out to Support to get this logged. ... View more

Good morning, I am unable to reproduce this behavior with a trace network in 3.1.2 or 3.1.3.  If there are current TN_Temp_Starting_Points and TN_Temp_Barriers feature classes in your project's default geodatabase,   could you test deleting these and recreating them by placing the trace locations again to see if the issue persists. ... View more

@Acharya  In ArcGIS Pro, when you select the Portal tab from within the Catalog pane and navigate to your trace network service, can you double-click this and see your trace network? ... View more

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 ... View more

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