POST
|
Associations aren't managed using primary/foreign key relationships, they are stored within the utility network. You can read more about containment associations here: Containment associations—ArcGIS Pro | To create/maintain associations you can use the modify associations tool, feature templates, or attribute rules. For your initial data-load you will need to use the import associations tool to import your existing associations using a flat file. Documentation
... View more
yesterday
|
1
|
0
|
40
|
DOC
|
There is currently no tool to perform this or any plan to develop one. If you want to create a reporting database of all your layers, I recommend you check out the Export Reporting Data tool from the ArcGIS Solutions team.
... View more
|
0
|
0
|
131
|
POST
|
I recommend you follow the Configure a map for the ArcGIS Utility Network tutorial to see how you can create a map that separates out the layers by subtype using subtype group layers. Subtype group layers are supported on any kind of feature class, as long as it has subtypes. So if your data is in a feature service you can use the Add Data > Subtype Group Layer button to add each utility network layer in the service as a subtype group layer. This will allow you to set the field properties for each subtype as you desire.
... View more
Friday
|
1
|
0
|
36
|
IDEA
|
@JürgenBiendara we have a detailed article explaining the purpose of this option here Subnetwork Deep Dive: Status. I'll try to summarize it here. Managing Dirty means that when data is validated, the system will identify which specific subnetworks were modified by the edit. This is used to assist in quality assurance, so an editor knows specifically which subnetworks need updating. If you disable this setting, then the system will no longer perform this analysis and every subnetwork will always be considered dirty. Running update subnetwork is always a separate operation that must be run separately by a user (or process), the state of clean/dirty is just a way of indicating which subnetworks have been modified. So, if you care about precision with your quality assurance and just focusing on the subnetworks that have changed, you want to manage the status of your subnetworks. If you don't have any subnetwork-specific quality assurance and are ok with just running update subnetwork on all your subnetworks on a periodic basis, then you can disable managing the status of subnetworks.
... View more
Friday
|
0
|
0
|
62
|
IDEA
|
@JürgenBiendara can you provide a bit more context for why you want this? Is it that you want to set a tier to be managedirty=true and occasionally ignore a validate? Or do you want to have a tier be managedirty=false and choose to only mark the network as dirty at a time-and-place of your choosing?
... View more
Thursday
|
0
|
0
|
90
|
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
Wednesday
|
0
|
1
|
171
|
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
Wednesday
|
1
|
3
|
176
|
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
Wednesday
|
0
|
0
|
43
|
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
Tuesday
|
2
|
0
|
69
|
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
Tuesday
|
0
|
1
|
71
|
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
a week ago
|
0
|
0
|
129
|
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
a week ago
|
0
|
1
|
133
|
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
a week ago
|
0
|
0
|
137
|
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
a week ago
|
0
|
1
|
147
|
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
a week ago
|
0
|
0
|
116
|
Title | Kudos | Posted |
---|---|---|
1 | yesterday | |
1 | Friday | |
1 | Wednesday | |
2 | Tuesday | |
2 | a week ago |
Online Status |
Offline
|
Date Last Visited |
yesterday
|