|
POST
|
If the layer is pointed to a version and you're seeing it appear in default, I would log a case with support on that.
... View more
10-22-2025
12:59 PM
|
0
|
0
|
219
|
|
BLOG
|
@gis_KIWI4 There was an issue with the original add-in I posted (the 1.0.0 version), try downloading the 1.0.1 version and see if that fixes the issue.
... View more
10-22-2025
08:14 AM
|
0
|
0
|
1345
|
|
POST
|
The easiest way is to use the "Create Utility Network System Tables Views" tool in the Utility Data Management Support tools to add the layer to your map: Esri/Utility-Data-Management-Support-Tools: A set of tools to work with the utility network and their maps.
... View more
10-21-2025
11:42 AM
|
0
|
0
|
423
|
|
POST
|
Do you have a copy of the database from before the upgrade to see if this was still reporting an error? If you add the associations table to the map and query for the association between these two features, what do you see?
... View more
10-21-2025
08:57 AM
|
0
|
1
|
468
|
|
POST
|
This appears to be a duplicate of this thread: https://community.esri.com/t5/arcgis-utility-network-questions/how-to-merge-the-asset-packages-in-egdb/td-p/1658690/jump-to/first-unread-message?
... View more
10-18-2025
07:53 AM
|
0
|
0
|
222
|
|
POST
|
The point @gis_KIWI4 makes about missing vertices is one you need to consider carefully. If the source data is coming from a geometric network, and you aren't creating new features, then this isn't a big concern. If the data is being created outside of an environment that maintains a proper topology, then your appending process must identify and create any missing vertices on lines (in the asset package as well as in the source data) to ensure the newly imported data becomes properly connected. If you need to create missing vertices, you will probably want to use FME. The methods suggested by @gis_KIWI4 should work regardless of whether you're loading one asset package or 5,000 asset package, although individually loading 5000 asset packages will require some special attention be paid to how you load and QaQc each package as well as how you manage pruning out the unnecessary history you will be creating during the loading process.
... View more
10-18-2025
07:52 AM
|
0
|
0
|
266
|
|
BLOG
|
We recently developed a Calculate Flow Arrows community sample that allows a user to visualize the flow direction of subnetworks and have included a copy of the community sample as an add-in on this post. This sample includes quite a few limitations, and we recommend that customers who are serious about understanding the flow in their network seek out partner solutions that do not have these limitations and provide a more robust user experience. While this add-in is useful for many different kinds of networks, it is designed primarily to support the radial flow found in electric distribution networks. This is different from pressurized pipes of pipeline networks like gas and water, which are either heavily looped (distribution) or possess simple topographies (transmission). This also differs from gravity-based networks such as sewer and stormwater which often use a flow direction field to model the effects of gravity, and visualize the resulting flow in the network, using the techniques described in the Tracing using Digitized Direction article. Usage 1. Download the add-in from this post and double-click the file to and select Install Add-in to install it. Double-click the add-in file to open the dialog that allows you to install it. This add-in was built for ArcGIS Pro 3.5. If you have an older ArcGIS Pro client, this add-in may not load or work properly. 2. Open ArcGIS Pro. On the ribbon you will notice an additional Add-in tab. Select the Add-in tab and you will see a Show Flow Arrows Pane command. Launch the calculate flow arrows pane using the command on the Add-in tab of the ribbon. 3. Click the Show Flow Arrows command to open the Calculate Flow Arrows pane. Meet the calculate flow arrows pane. The pane will populate the Tier parameter dropdown with the tiers from the first utility network in your map. You can refresh the list by closing and re-opening the pane. 4. For the Tier parameter, select the tier you want to analyze from the dropdown; this will populate the Subnetworks parameter dropdown with clean subnetworks in the tier. Select the tier that contains the subnetwork you want to analyze. The pane will only load the first 3000 clean, active subnetworks from the tier. You can force the pane to load dirty subnetworks by clicking the Include Dirty parameter. 5. For the Subnetworks parameter, select the subnetwork you want to analyze and click the Analyze Subnetwork command. Select the subnetwork you want to analyze from the list. 6. The tool will output several log messages as it exports and analyzes the subnetwork. Click analyze to calculate and display the flow for the selected subnetwork. When the analysis completes it creates a FlowLines feature class added inside the default geodatabase for your project if one doesn’t already exist. You can control whether previous flow arrow results will be deleted from the layer by selecting the Clear previous results parameter. The first time you run the tool you will need to add the newly created layer to your map. 7. Add the FlowLines layer to your map to visualize the results. An example of flow arrows for the distribution lines within a substation and all its downstream circuits. A sample layer file has been included in this article that includes sample symbology. Add it to your map and point it to the FlowLines layer in your project. 8. If the tool was run with the Apply filter parameter checked, a definition query will be applied to the FlowLines layer, and the map will zoom to the selected subnetworks. 9. You can change the active subnetwork, or remove the filter, by changing the active definition query using the Ribbon or layer properties. The FlowLines layer has definition queries for each subnetwork you analyze. This definition query will filter the flow arrows to only show the selected subnetwork. 10. The flow calculated can be one of four different values: The initial symbology for the FlowLines layer allows you to visualize flow for each section of line. • With Digitized Direction – The flow calculated from the subnetwork controller matches the digitized direction of the line. • Against Digitized Direction – The flow calculated from the subnetwork controller is in the opposite of the digitized direction of the line. • Indeterminate – The line was found to be part of a loop within the network. • Bi-directional – The line is not part of a loop, but the flow calculated for the line is different depending on the subnetwork controller used to calculate flow. 11. The FlowLines layer also includes a chart that can be used to quickly identify features that have indeterminate or bi-directional flow. The chart on the FlowLines layer allows you to quickly identify indeterminate or bidirectional flow on the current subnetwork. Known Limitations The add-in is provided with several known limitations. Because the utility network doesn’t expose flow information, the tool estimates flow direction for the utility network features. Because of this, there are certain scenarios where the flow direction calculated by this tool may differ from the actual flow direction returned by an upstream/downstream trace of the utility network. This tool is designed for and works best with balanced electrical distribution networks with a single condition barrier. While it can still be run on circuits that have multiple condition barriers or propagators, the flow will be calculated using more basic logic. The tool can also be run on subnetworks from other domains but may run slower on large networks or networks with many subnetwork controllers. If you find that the flow arrows calculated by the tool are incorrect for your network configuration, you should seek out partner solutions for this problem. While it is possible to download and extend the community sample, it requires a deep understanding of the domain being analyzed and graph traversal algorithms. Conclusion While this add-in does have many limitations, we felt that it was a good way for customers who were getting familiar with the utility network to begin understanding flow. We also recognize that as customers become familiar with the utility network and more advanced workflows, they will want to rely on partner solutions that don't suffer from the limitations of this tool and provide a more robust user experience. Please be aware that support is not provided for this tool. If you run into any issues with the add-in or have questions, you can raise these on the community site. If you want to see any enhancements to the tool or need it Enhancements and support for other releases of ArcGIS Pro can be completed using a version of the Calculate Flow Arrows community sample which you maintain from the ArcGIS Pro SDK Community Samples page. This add-in is provided with compatibility for ArcGIS Pro 3.5 and supports all utility network schema versions. You can analyze clean subnetworks beginning with ArcGIS Enterprise 10.9. 1; however, analyzing dirty subnetworks requires ArcGIS Enterprise 11.1 or later. This tool supports both capabilities on utility networks contained in File and Mobile geodatabases.
... View more
10-17-2025
11:01 AM
|
6
|
9
|
2580
|
|
POST
|
Based on previous discussions can you show how you are currently modeling these features and what problem you are trying to address by re-migrating them? It would be especially useful to know how or if you are making use of assemblies or non-spatial objects. At a high level, the pad mounted transformers are going to be 3phase pad mounted transformers, and the PME is going to be a structure that contains 2 switches, 2 fuses, and the bus work between them. The connection between the junction box and the PME seems unusual in that the second bay of the PME isn't occupied and the third bay has two connections. You could model that like-for-like in the UN model using electric devices, electric junctions, and structure boundaries (for the cabinets) if you wanted to. Just upstream of the PME there appears to be a junction box with an open point in it.
... View more
10-16-2025
04:58 PM
|
0
|
0
|
244
|
|
POST
|
If you're experiencing slow draw times, please submit a case with support. That query indicates that you're attempting to draw all the features in the water lines layer for the current moment, which should perform well under reasonable circumstances. You can find a presentation explaining a generic form of the query to answer your first question here: Version Management with ArcGIS - Esri Videos: GIS, Events, ArcGIS Products & Industries. The short answer is that moment is used to ensure that you're looking at the data as it existing for the current moment that the client is using for viewing the data.
... View more
10-16-2025
07:39 AM
|
0
|
0
|
178
|
|
POST
|
The issue that was discussed was trace results not appearing correctly when layers are duplicated in Field Maps. Because tracing is not supported for Trace Networks in Field Maps this is not a concern.
... View more
10-15-2025
10:42 AM
|
0
|
1
|
432
|
|
POST
|
@BGEGIS I only see three of the possibilities listed above, what about the fourth option of leaving both boxes unchecked? What I'm suggesting is that you run it with the Report Only box unchecked (so it will actually prune) AND the Only Prune System Tables box unchecked (so it will prune the data in the user tables).
... View more
10-14-2025
09:24 AM
|
0
|
0
|
723
|
|
POST
|
Instead of using the asset group field to create the definition queries for your mappings, use the asset type field. You will find it much easier to do your mappings this way.
... View more
10-13-2025
11:38 AM
|
0
|
0
|
458
|
|
POST
|
In the simple data mapping spreadsheet, you need to create separate mappings for each of the asset groups and asset types in your model. This will allow you to properly identify (through a definition query) each asset type in your source model and map it to its corresponding asset type in the target model.
... View more
10-11-2025
02:56 PM
|
0
|
2
|
487
|
|
POST
|
Can you post the command you're using to prune? I notice in the initial post it looks like when you're pruning you had the option to only prune system tables checked. If you run the tool with the "Report Only" option and "Only Prune System Tables" options unchecked, it should prune all user and system tables.
... View more
10-10-2025
02:49 PM
|
0
|
2
|
778
|
|
POST
|
Your views don't appear to be filtering out rows from default, which could be causing some of the problems that you're seeing. The rows in non-default branches may have newer gdb_from_dates that the rows in the default version. In terms of verifying that everything is really being pruned, it's hard to do that without looking at the contents of your system tables and comparing them to the table(s) in question. You may need to open a support case on this one.
... View more
10-10-2025
01:37 PM
|
0
|
4
|
780
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 1 | 3 weeks ago | |
| 1 | 09-22-2025 06:57 AM | |
| 1 | 3 weeks ago | |
| 1 | 3 weeks ago |
| Online Status |
Online
|
| Date Last Visited |
11 hours ago
|