POST
|
Good afternoon Ben, Single-user deployments in either a file or mobile geodatabase provide access to the same analytic capabilities of the utility network; however, these cannot be published to create a utility network service. The publishing and consuming services topic touches upon this. While it does not explicitly state that utility networks in file and mobile geodatabases cannot be published, it does communicate that "map layers must be from a database connection established as the database utility network owner, and that all network layers must be registered as branch versioned", both of which are only possible when the data source is an enterprise geodatabase. While you cannot publish the UN in the file geodatabase, you can still configure and test your network in the file geodatabase and copy the UN into an enterprise geodatabase for publishing once you feel comfortable with it. Hope that helps, Jon
... View more
11-16-2023
12:21 PM
|
1
|
0
|
180
|
POST
|
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
09-05-2023
04:50 AM
|
0
|
0
|
220
|
POST
|
Good evening Alex, I am not clear on what the end goal of these traces are so cannot comment on alternatives but... for the first example, we cannot evaluate network attributes across two separate classes in this way. Because the values associated with the network attributes are not present on both feature classes, the expression will never evaluate as true and stop the trace. The second example you show using the value of "h_l = 214" applies a simple condition barrier that stops the trace once satisfied at the highlighted line (as well as the line south of the junction) . The highlighted line is excluded from the trace because it satisfies the barrier condition and the Include Barrier Features parameter is unchecked. Checking that box should return the expected result:
... View more
07-26-2023
11:46 AM
|
1
|
1
|
402
|
IDEA
|
This capability was added in ArcGIS Pro 2.9. Here is the text from the What's new in ArcGIS Pro 2.9: You can migrate utility network datasets between geodatabases for staging and testing using Copy and Paste tools and the Export XML Workspace Document and Import XML Workspace Document geoprocessing tools.
... View more
07-18-2023
11:53 AM
|
0
|
0
|
642
|
POST
|
@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
03-14-2023
01:27 PM
|
0
|
0
|
480
|
POST
|
Thank you for the additional info, would you be able to share the error report generated from the operation? Here is some info on where to find these: https://support.esri.com/en/technical-article/000011589
... View more
07-26-2022
05:35 AM
|
0
|
0
|
663
|
POST
|
@GardenKo Is this occurring with any project, including a newly created one? It is possible this is related to an issue with the install. Is this behavior recent? What version of ArcGIS Pro are you working with and has anything changed with your install recently? Are you able to share the error report that is created when this issue is encountered? Thanks, Jon
... View more
07-25-2022
04:46 AM
|
0
|
2
|
682
|
POST
|
Glad that helped @DavidNovak To answer your question, yes, I would say that using the Trace Network in a services-based architecture is ready for production use. Whether you choose to utilize a trace network or "simplified" utility network comes down to how you plan to manage your network and the capabilities you are looking for. I'll reach out to you directly to gather more information on what you are trying to accomplish with the trace network.
... View more
07-21-2022
07:00 AM
|
1
|
0
|
1047
|
POST
|
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
07-20-2022
08:15 AM
|
1
|
0
|
1058
|
POST
|
@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
07-14-2022
08:21 AM
|
0
|
1
|
548
|
POST
|
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?
... View more
07-12-2022
08:25 AM
|
0
|
0
|
338
|
POST
|
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.
... View more
07-12-2022
06:03 AM
|
2
|
1
|
757
|
POST
|
Moved to Field Maps Questions
05-17-2022
01:53 PM
|
0
|
0
|
121
|
POST
|
@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.
... View more
03-07-2022
12:48 PM
|
2
|
0
|
469
|
POST
|
@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.
... View more
01-26-2022
06:49 AM
|
2
|
1
|
3957
|
Title | Kudos | Posted |
---|---|---|
1 | 11-16-2023 12:21 PM | |
1 | 07-26-2023 11:46 AM | |
1 | 07-21-2022 07:00 AM | |
1 | 07-20-2022 08:15 AM | |
2 | 07-12-2022 06:03 AM |
Online Status |
Offline
|
Date Last Visited |
2 weeks ago
|