Latest Contributions by EC1

‎01-12-2023

Good suggestion, but that doesn't seem to be the case. I've created a new map project and added minimal layers to it, just all of the required UNM layers (once) and a few others: The strange thing was the terminal connection tool worked in this new map for very short period of time before coming up with the same Terminal Connection error. 😞

‎01-11-2023

Hello, I have been actively setting terminals using the "Terminal Connections" UNM tool over the past few days, but it has suddenly stopped working. See picture below. I've tried: disabling/enabling topology. Creating a new map project, which worked for about 3 edits of terminals, then the same error occurred again Closing/opening arcpro I've been using this tool for several months without issue, but now I cannot edit any terminals. The devices in the picture are subnetwork controllers with terminals. I managed to set them up with terminals/subnetworks but now I cannot edit the terminals. What can I do to fix this? Is there something I am missing? Thanks.

‎09-14-2022

Managed to fix this via SQL Management Studio. There is no way to fix this via arcPro as far as I can tell. Solution using SQL Management studio: -Find the table which has duplicate GIDs -Identify the duplicate GIDs and record them. -use a command similar to this. UPDATE [egdb name].[unm].[WATERJUNCTION] SET GLOBALID=NEWID() WHERE GLOBALID = '(your GID(s) here)' Lastly you'll have to delete the duplicated items manually in ArcPro.

‎09-13-2022

Thats useful, but how would I enter multiple the GIDs of the multiple isolation valves that create a shut-off block? It looks like in the exported subnetwork controllers csv theres only one FEATUREGLOBALID per subnetwork. Or would I have to set up multiple SUBNETWORKCONTROLLERNAMES for each of the isolation valves that define all the isolation valves that go into a shut-off block? and those would all share the same SUBNETWORKNAME? If I was to do this on a large scale I could automate the naming process.

‎09-07-2022

I have a Water Utility Network Model up and running, with various source/pressure subnetworks. My Network includes the following relevant features: Water pipes and isolation valves I wish to create shut-off blocks using the isolation valves. By shut-off block I mean an area of pipe that can be turned off using the nearby isolation valves. I wish to set these up as their own individual 'isolation' subnetworks. Below is an example of what I wish to achieve, with the highlighted line being a isolation subnetwork. The red circle is a isolation valve, the red arrow is also a isolation valve. Note that the sub isolation valves (red arrow) are included in the isolation subnetwork. So far to define any subnetworks I have used the modify subnetwork tool through ArcPro. Manually setting isolation subnetworks will not be possible. Is there a way to automate this process? Either through ArcPro, or through something like FME - is it possible to define these isolation subnetworks purely via changing attribute fields on the pipes/isolation valves or is there more back end things going on? Thanks for reading.

‎08-31-2022

Have you made sure that all layers of the UNM are included and published together?

‎08-31-2022

Solution found: There were some scour valves which had incorrectly connected directional terminals, nearby the areas which returned the whole network incorrectly. In the areas with issues the startpoint/endpoint of the pipe was not connected to the appropriate terminal. For example the from terminal was connected to an end of a water line, rather than a start of a water line. My guess is this incorrect assignment caused the trace to return the entire network, ignoring any more condition barriers (isolation valves) it came across.

‎08-30-2022

Hello I am working on a Water Utility Network Model, which include the following features: Water mains, Water meters and Isolation valves. I have created a isolation trace that selects water meters impacted if that water main had to be shut off using the nearby isolation valves. This trace works 95% of the time when run. But occasionally it will instead return the whole network of water meters. I have been trying to work out why, but so far I have not come up with any conclusion. I have checked my topology rules and everything seems fine, which makes sense, because this trace works in the majority of the cases. When I run a connected trace on the same areas with issues, instead of an isolation trace, I get the appropriate results. see example below. note that the example below shows selected isolation valves instead of water meters, but the issue is the same. above images description: Connected trace, condition barriers: isolation valves, output: isolation valves. (Include barrier features is on). above images description: Isolation trace, Filter barriers: isolation valves, output: isolation valves. (include isolated features is on) as can be seen the connected trace returns the appropriate selected isolation valves (5), while the isolation trace returns the whole network of isolation valves (1000+). I need to use the isolation trace specifically for the include isolated features function, to define the shut-off blocks properly, rather than a connected trace. I am truly stumped by this issue. Any recommendations of things I could try/check would be greatly appreciated.

‎08-08-2022

ArcPro 2.7.1, how do I find my UN version? I think I am using UNtools 2.7.

‎08-07-2022

In this case zooming/validating without me editing it results in 'no dirty areas found', as you can see in the first picture. Its quite annoying!

‎08-07-2022

Hello, Where can I find connection tolerance information/settings for the Utility Network Model? I assume I am using the correct terminology, tolerance. What I want to find is how close features can be where the UNM counts them as being connected and can this be changed? I am using ArcPro. Thanks.

‎08-07-2022

I have two features that have the same Global ID. When I try to remove/delete one of the pair I get this error: This is not the first time this has happened. Currently the only way to fix this is to connect to the database via sql manager and generate new global IDs for the duplicated features. Is there a way to get around this/delete the duplicated feature with duplicate GID via ArcPro without the use of sql management studio?

‎08-07-2022

How can I recover features that were incorrectly deleted in the Utility Network Model? I recall reading that all features are never truly deleted in UNM, but are just marked as inactive or similar, I can see them in the SQL DB. Is there an edit history somewhere? Also, if a feature is restored/recovered, and a feature with the same global ID already exists, how can we avoid this issue from happening: https://community.esri.com/t5/arcgis-utility-network-questions/duplicate-globalid-renders-deleting-removing/m-p/1200240#M1920 Thanks.

‎08-04-2022

Hello, I am setting up a Utility Network Model. I am using FME to push data into the model via a web feature layer. In this circumstance there were originally errors (small dirty areas) along the blue line, which were fixed via inserting required features to meet network topology rules. When the smaller dirty areas were initially flagged, the selected line was also flagged. Now the other errors have been fixed, this blue line should not be flagged as an error anymore, as the issues have been fixed. But even when trying to validate the UNM thinks there is nothing wrong and does nothing: . To fix this issue I am currently doing this, which is a very tedious and slow process: I edit the vertices on the point with the red arrow, simply by clicking, draging and putting it back to its original position, after that the error area is now a dirty area: and now it can be validated. This seems to be a major bug in the utility network model. This issue is chewing up a large portion of users time to fix. Is there a way to do this quicker? I have tried turning network topology off/on, refreshing the connection and restarting arcpro. The errors remain as the Utility Network Model validate does not seem to realise they exist until I manually edit and refresh that dirty area. Please help, or fix this bug. Thanks.

‎08-04-2022

I am also consistently having this issue. I haven't found any easy fixes. my issue is the UNM ERROR areas occur, fixes are made via FME, then validate runs fine, a popup tell me "there are no dirty areas", but the ERROR dirty areas remain. The only way to fix in my case is to edit the line the ERROR dirty area is flagging, moving and replacing it where it was, then re-validating it. Very time consuming and annoying.

Online Status	Offline
Date Last Visited	‎01-17-2023 04:54 AM

My Ideas

Latest Contributions by EC1

Re: Cannot set Terminal Connections

Cannot set Terminal Connections

Re: Duplicate GlobalID renders deleting/removing feature impossible - Delete selected features failed.

Re: How to Automate Creation of Subnetworks

How to Automate Creation of Subnetworks

Re: Utility Network Field Maps

Re: Isolation trace returning incorrect results

Isolation trace returning incorrect results

Re: Validate doesn't validate "Error" dirty areas.

Re: Validate doesn't validate "Error" dirty areas.

Finding connection Tolerance (define within what distance features are considered connected) - Utility Network Model

Duplicate GlobalID renders deleting/removing feature impossible - Delete selected features failed.

How to restore deleted features in Utility Network Model

Validate doesn't validate "Error" dirty areas.

Re: Dirty Area Status meaning