|
POST
|
@EdwardBlair Customers often adapt the model to suit their requirements. In the case of rectifiers/anodes, because the Domain Network is defined as being source-based and because anodes aren't always physically connected to pipes you'll likely want to use rectifiers as sources (see article 2 for examples). I have seen some customers use the existing tier to manage this, foregoing the importance of test points. I have also seen one customer add a new tier so they could trace and manage the electrical conductivity of the cathodic protection system separate from the regulatory requirement. It comes down to what are the requirements that you are trying to solve with your GIS and what configuration best meets that need. This is why I linked to the first article, because it lays out the requirements and business case for the original design and configuration of cathodic protection in the UPDM model.
... View more
12-17-2025
08:56 AM
|
0
|
0
|
285
|
|
POST
|
@Andy_Morgan You can mitigate the risks of pressure zone boundaries breaking if you have editors work in a version, instead of defaulting directly, and ensure they validate all their dirty areas, fix all their edits, and trace or update their subnetworks before posting their versions. This will flag any inconsistent subnetworks before they are posted to default and become everyone's problem.
... View more
12-17-2025
07:10 AM
|
0
|
1
|
252
|
|
POST
|
As always, I defer to @TomDeWitte on all Gas and Pipeline matters, but this is my understanding based on my time spent implementing cathodic protection in GIS for gas utilities. From an electrical perspective, you are correct that it would make sense to model the rectifier (source) or anodes (sink) as subnetwork controllers. However, from a regulatory perspective each zone is considered a cathodic structure and is typically associated with a set of specific test points. Because of this many of these gas companies already have a database that lists out the structures and test points for each cathodic structure, which makes it easier to create and validate this information in the utility network, as well as integrate it for compliance purposes. For more information on the compliance side of things, read Tom's One Source of Truth for Cathodic Protection. For more general information on how CP works, read Tm's Understanding Cathodic Protection for GIS & IT Professionals. @EdwardBlair you probably already know all the info in those two articles, but others reading this comment or post in the future may benefit from the information.
... View more
12-17-2025
07:08 AM
|
0
|
3
|
288
|
|
POST
|
If you ever want to turn that attribute rule back on, while still supporting the workflow of manually entering attributes. You would want to add logic to skip over updating the fields if they're already populated.
... View more
12-17-2025
07:00 AM
|
0
|
4
|
373
|
|
POST
|
The sewer model features a directional manhole channel with four terminals whose purpose is to manage this. In practice, it can take a bit of work to get all the terminal connections correctly populated so customers who want to use subnetworks tend to rely on digitized direction tracing until they get the terminals sorted.
... View more
12-17-2025
06:59 AM
|
1
|
0
|
491
|
|
POST
|
@VishApte_NGIS if you do keep the utility networks in the same database, but put them in separate schemas you avoid the StructureJunction_1 type issue.
... View more
12-17-2025
06:55 AM
|
0
|
0
|
178
|
|
POST
|
The subnetworks table is the more reliable way of determining status, especially in networks with multiple subnetwork controllers.
... View more
12-16-2025
08:22 AM
|
0
|
0
|
439
|
|
POST
|
If the domain isn't associated with one of the system fields of the utility network (including asset group or asset type), you should be able to rename it using the Domains Design view pane.
... View more
12-16-2025
08:19 AM
|
0
|
0
|
200
|
|
POST
|
The Geometry method takes a $feature and returns its geometry. I recommend you test out this method by putting it in a popup expression on the line layer (have one for the upstream elevation and another for the downstream elevation), then click a few features and see what its outputting. I'd defer to the data dictionary and @MikeMillerGIS about the elevation field.
... View more
12-15-2025
07:53 AM
|
0
|
0
|
783
|
|
POST
|
The fastest way I've found to do this on Enterprise is to use the ArcGIS API for Python. That's a weird response your getting, and my guess is you should be getting an error instead (check the server logs). The problem is that your starting locations are missing required fields. You're only providing a type and globalid, but you need to provide at least one additional value, depending on whether the starting location is a point or line: If you're running isolation traces from lines that can get tricky, because you aren't required to split lines at valves so you could potentially be missing out on results. This is why I'll usually try to pick some piece of equipment like a meter or a corp stop as my starting points, but put in skip logic to ensure I don't process the same area multiple times. If you are open to using a community sample written in C#, there is a batch trace community sample available that does all of this (including the skip logic). You just need to compile and run it. You would partition your network using your mains, then set up a named trace configuration to run a connectivity trace that stops at isolation devices. In fact ... there are already sample configuration files that do this for the standard naperville model, so you'd just need to adjust them to account for any schema changes you've made (Partition_Water_Isolation). You can use the link in the partition markdown page to access them:
... View more
12-14-2025
08:02 AM
|
0
|
3
|
776
|
|
POST
|
Can you please verify three things: The attribute rule for updating elevation to lines is assigned and enabled. The device/junctions on either end of the line have Z-values The line itself has z-values on its first and last vertex.
... View more
12-14-2025
07:48 AM
|
0
|
5
|
814
|
|
POST
|
Can you post a screenshot of what attributes or values you are expecting to be updated on the lines class? Do you have any attribute rules written to maintain these attributes as you are creating or updating features?
... View more
12-12-2025
06:10 PM
|
0
|
1
|
854
|
|
POST
|
@PierreloupDucroix you'll want to ensure that versions are reconciled on a regular basis. You can automate this, but you need to make sure that you don't reconcile a version that already has conflicts! Otherwise, you will automatically accept the conflicts as-is without any record that they existed (the default behavior). If you use Python you can accomplish this with the Reconcile Versions tool by seting the parameter proceed_if_conflicts_not_reviewed to NOT_PROCEED (which isn't the default value). If you're using REST, or some other means you will need to use the APIs to query for persisted conflicts on the version before you reconcile.
... View more
12-12-2025
06:59 AM
|
0
|
0
|
180
|
|
POST
|
@NathanHeickLACSD Correct, subnetwork flow direction is calculated every time. This is important, nay required for certain scenarios like cathodic protection. The upstream path to a pressure source vs. the upstream path to a rectifier (or the downstream path to an anode) are going to be different.
... View more
12-12-2025
06:54 AM
|
1
|
1
|
286
|
|
POST
|
Is the connection file using the credentials of the data owner? It sounds like there may be a difference in the connection files between the machines. If you copy one of the connection files from the other machines to this one, does it work?
... View more
12-12-2025
06:52 AM
|
0
|
0
|
260
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Sunday | |
| 2 | Wednesday | |
| 1 | Tuesday | |
| 1 | a week ago | |
| 3 | a week ago |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|