|
POST
|
I did have to manually snap it. It looks like you have made adjustments to the z values of some of these geometries. The Z of the attachment and the first line is 0 (which is why they're connected), but the first vertex of the next line has a Z value of -1.
... View more
04-17-2024
12:52 PM
|
0
|
1
|
2383
|
|
POST
|
The real problem is that your distribution circuit isn't able to make it past your first length of conductor because the second conductor is not connected to the attachment. I noticed there were a lot of dirty areas in the network, and after disabling the network topology and enabling the network topology the subnetwork appears to trace correctly (according to the data you have provided). As for why busbar 93 is still showing as isconnected after deleting the subnetwork, I'm not sure.
... View more
04-17-2024
12:42 PM
|
1
|
3
|
2388
|
|
POST
|
@BasWest1 In the scenario above, dirty areas would be able to manage the status/validation of deleting the second pipe because all features involved have dirty areas with their own status fields. Based on this, I'm assuming, you're talking about a batch validation attribute rule right? If so, please start a new question for this discussion (since its a separate discussion with a separate, but important solution).
... View more
04-17-2024
06:39 AM
|
0
|
0
|
2709
|
|
POST
|
That looks like a bug, we'll take a look at it. If you end up logging a case let us know.
... View more
04-16-2024
12:00 PM
|
2
|
0
|
1561
|
|
POST
|
In order to edit the data you will need to start an edit operation then start editing. once you've completed your edits you will need stop your edit operation and stop editing (with save edits = true). If you want to go down the route of performing these edits in a version, which is a good idea since it lets you QaQc or roll back changes if something fails partway through, you should look at using the ArcGIS API for Python. It will allow you to create a version, perform your edits, validate, reconcile and post, all from a standalone python script (or within ArcGIS Pro if you prefer that approach).
... View more
04-16-2024
06:37 AM
|
0
|
1
|
2310
|
|
POST
|
A subnetwork trace for a pressure subnetwork should only include features that belong to that pressure zone, if it is including additional features than you have not correctly defined the subnetwork in your utility network or the data in the utility network is incorrect. If you haven't already, you should read the articles we wrote about modeling water subnetworks using the utility network, as they answer most of these questions and provide examples (for this thread, and several of the other threads of questions you have on here). The questions you just asked are part of the quality assurance process (article three below). https://www.esri.com/arcgis-blog/products/utility-network/water/creating-subnetworks-water/ https://www.esri.com/arcgis-blog/products/utility-network/water/water-subnetwork-errors/ https://www.esri.com/arcgis-blog/products/utility-network/water/water-data-quality-assurance/ https://learn.arcgis.com/en/projects/create-and-manage-subnetworks/ https://learn.arcgis.com/en/projects/edit-and-validate-subnetworks/ https://learn.arcgis.com/en/projects/perform-quality-assurance-on-subnetworks/
... View more
04-15-2024
10:31 AM
|
0
|
0
|
2090
|
|
POST
|
Define your pressure zones using the devices that regulate the pressure for those zones (typically pumps and pressure-reducing valves in a water distribution system) and you should have the correct number of features in each zone. You should check with an engineer or someone with an operational understanding of the specific system you are modeling if you are unsure you are seeing the correct results.
... View more
04-15-2024
10:14 AM
|
0
|
1
|
2094
|
|
POST
|
Because you only created a single pressure zone in the entire system then by your very definition all the features in the system must belong to that one pressure zone (although by your screenshot I can see there are quite a few features that don't belong to any subnetwork). The subnetwork will stop when it encounters a barrier (closed valve for pressure) or when it encounters another subnetwork controller.
... View more
04-15-2024
10:02 AM
|
0
|
0
|
2098
|
|
POST
|
If you are using the standard model, you likely either haven't populated any of the fields that are associated with the condition barriers in those tiers (valve status, CP Only, etc) or you haven't defined the rest of the subnetworks in your system. If you only create one pressure zone for your system, you should only expect to see one pressure zone for your system.
... View more
04-15-2024
08:01 AM
|
0
|
1
|
2108
|
|
POST
|
Your subnetwork controllers are all traversable to one another. Read this managing electric subnetworks article to learn more about what may be going wrong with your data.
... View more
04-15-2024
07:59 AM
|
0
|
0
|
1252
|
|
POST
|
This is not the expected behavior, but I am not able to reproduce it on the latest version of the software. That means that it is likely a bug that we fixed some time ago. Can you test this out using ArcGIS Pro 31? That's the latest network management release version of ArcGIS Pro.
... View more
04-15-2024
07:54 AM
|
0
|
2
|
1274
|
|
POST
|
The constraint is that you can't use object ID based relationships (002568: Branch version relationship classes must not use Object ID for the primary key.—ArcGIS Pro | Documentation). You are welcome to use any user-defined and maintained field. Many customers prefer to use the global ID field because it is a system-generated and maintained unique identifier.
... View more
04-12-2024
01:58 PM
|
0
|
0
|
1114
|
|
POST
|
The connectivity is ambiguous because either of those lines could be connected to either of those terminals, and you haven't used the modify terminal connections tool to specify which line is connected to which terminal. Once you do that the error will go away. Also, I hope that third line isn't also spatially coincident with that recloser.
... View more
04-12-2024
01:55 PM
|
2
|
0
|
1318
|
|
POST
|
For terminal configurations where that aren't directional, the terminal assignments are often arbitrary, so you just assign the terminals on a first-come, first-served basis. For devices like pumps or pressure regulators, you would look at the inlet and outlet pressures of the device and match them with their corresponding pipe. Secondly, water distribution is a highly looped system so you can't rely on the digitized direction to indicate any kind of flow (and even if you could, a closed device would always be downstream of two lines).
... View more
04-10-2024
06:37 AM
|
0
|
0
|
900
|
|
POST
|
@gis_KIWI4 That sounds like a separate issue. If you're noticing a performance hit when you query the layer using a particular attribute, and that query is something you intend on using a lot, have you considered adding an index to that field? As an example, you could add an index to the tier name field (which is used as the subtype for the layer) and use a subtype group layer to control scale suppression.
... View more
04-10-2024
06:29 AM
|
1
|
0
|
2545
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | yesterday | |
| 1 | Monday | |
| 1 | Friday | |
| 1 | a week ago | |
| 1 | a week ago |
| Online Status |
Online
|
| Date Last Visited |
yesterday
|