|
POST
|
Please log an issue with support for this so you can get attached to the bug.
... View more
06-16-2025
06:08 AM
|
0
|
0
|
1039
|
|
POST
|
This thread is in response to this article: https://community.esri.com/t5/arcgis-utility-network-questions/re-branch-version-sql-views-utility-network/td-p/1623753 Materialized views aren't available on all platforms, so in some cases, you would be writing the contents of the branch version analytics to a table for reporting purposes. For the sake of this comment, I'll just assume you're using a materialized view. I would typically create a materialized view on the separate tables first. That way when I need to create a second or third report using any of those tables I can just use the tables I've already materialized. Creating a materialized view that contains a join for those tables will probably take longer than materializing the tables separately, especially once you bring the associations table into the mix. If this is a one-off, and the performance is better this way, then go ahead. But as soon as you need to make a second or third materialized view you will likely find the approach outlined in the article will be more scalable.
... View more
06-16-2025
06:04 AM
|
1
|
0
|
992
|
|
POST
|
The Analyze Network Data tool will only create a RuleCandidates CSV file for rules that are missing from the model. If you want to rebuild your rules from the ground up, you must first remove all the rules from your model.
... View more
06-13-2025
01:42 PM
|
0
|
0
|
883
|
|
POST
|
The image says it's still virus scanning (50 minutes later). Maybe try embedding it directly in your post?
... View more
06-12-2025
12:59 PM
|
0
|
1
|
2485
|
|
POST
|
After reading your question more closely, please post a screenshot of exactly where you are seeing this error. If you are publishing a deployed utility network to ArcGIS Enterprise it should not contain that table, domain, or coded value.
... View more
06-12-2025
11:49 AM
|
0
|
3
|
2518
|
|
POST
|
The big blue block saying the topology is disabled should go away when you run enable network topology, UNLESS you have the only generate errors option select. Can you confirm that this option wasn't selected and that the tool was run against the same utility network?
... View more
06-12-2025
11:31 AM
|
0
|
1
|
978
|
|
BLOG
|
Have you ever wanted to find all the errors in your in the utility network, but you weren't sure how to query the dirty areas table to filter our unvalidated edits from errors? This article has you covered! If you've looked at the dirty area before you have seen it has many different status values: If you've look at how these values are defined for the layer, you will see that they are calculated using an Arcade Expression. So how do you use that expression in something like Select By Attributes or a Definition query? The secret to filtering out edits is to know that the status field represents multiple states at the same time. That is to say that while a dirty area not only represents features that are need validating (i.e. dirty) or have errors, but a single dirty area can also represent a feature that has an error that needs to be re-validated. All using the same field! If all you care about is finding features that have error, you can use the simple expression: STATUS >= 8 But what if you want to know what kind of error (Feature, Object, Subnetwork)? For that, you have to use a more complicated expression. First you need to know what kind of error you're looking for to determine its Status Code or its calculated value. Feature Error: STATUS in (8, 24, 40) Object Error: STATUS in (16, 24, 56) Subnetwork Error: STATUS in (32, 40, 56) It is also possible to use BITWISE and operators to perform the calculations, but because that operator is implemented differently across different DBMS platforms (and is not available in File Geodatabases) it is simpler to use an In List. However, if you wanted to find dirty areas that need validation you WOULD need to use a BITWISE comparison to find errors with the first, second, and third bits set. The Validate Network Topology tool filters out these dirty areas when it runs, so this is more of a reporting check to ensure that nothing needs to be validated. You can learn how to write a query that does a bitwise comparison or learn how to parse specific error codes, in the article about querying the dirty areas table. You can find the online help topic for Dirty Areas to learn more about the fields on the Dirty Area layer. If you want to see some industry specific blogs or some hands-on tutorial for managing errors, check out the connectivity and topology learning series. If you want to create a report of all the errors in your utility network, check out the Summarize UN Errors tool from the ArcGIS Solutions team.
... View more
06-11-2025
12:31 PM
|
1
|
0
|
965
|
|
POST
|
Instead of using create/stage utility network, try using the Asset Package to geodatabase tool (for convenience). Instead of outputting the data to a mapped drive or network location, try outputting it to a local drive instead.
... View more
06-11-2025
11:37 AM
|
0
|
0
|
770
|
|
POST
|
That's most likely being caused by a restrictive contingent value not being met (see the 'Generate Contingent Values' section of this article for an example). Click the right arrow and see what fields/values it is unhappy with. My guess is that you are trying to create a feature with an unknown asset type.
... View more
06-11-2025
11:34 AM
|
0
|
0
|
885
|
|
POST
|
You're welcome to log an idea for it on the community site. There have been similar requests made for lifecycle status to be considered when evaluating topology rules.
... View more
06-10-2025
02:52 PM
|
1
|
0
|
789
|
|
POST
|
Are your pumps set up as subnetwork controllers for the pressure tier? What is the filter barrier you used in your isolation trace? It's usually configured to stop at any operable, accessible, system valve (or other piece of equipment that has the isolating category). In the diagram above I see that you are not treating system valves as equipment capable of isolating the trace. Some lines are missing in the network diagram. It's unclear why the features downstream of pumps 140, 144, 165, 166, and 167 are included. It is unusual for an isolation trace to span multiple pressure zones, so knowing the answer to the above questions should help us solve this mystery.
... View more
06-10-2025
02:48 PM
|
0
|
2
|
1123
|
|
IDEA
|
Another update on this one. In ArcGIS Pro 3.4 we introduced the ability to do this using ArcPy: UtilityNetwork—ArcGIS Pro | Documentation. In addition to the methods mentioned above.
... View more
06-08-2025
07:03 AM
|
0
|
0
|
1010
|
|
POST
|
@lfrazeurfw Are you using ArcGIS Online? If so, ArcGIS Online does not currently support utility network datasets, so you can only use the Stormwater Data Management solution. If you plan to use a utility network in the next few years, familiarize yourself with the Migration Toolset and the Utility Network Migration wizard. They include data migration and data cleanup tools to help you turn your current model to a utility network. Ideally this would be how you would get from your Stormwater Data Management solution to a utility network, since this would build a like-for-like utility network using your current model that includes all the data model changes you've made while implementing your solutions.
... View more
06-06-2025
05:55 AM
|
1
|
0
|
4250
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 1 | Tuesday | |
| 1 | 03-30-2026 07:24 AM | |
| 1 | Tuesday | |
| 1 | a week ago |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|