Latest Contributions by DamienPyne

‎03-23-2025

The summary tool for Pro 3.1 does not remove duplicates data correctly and therefore is reporting a count higher that the total errors in the database. Refer Reporting topology errors - Esri Community At the moment this is not an option while we are using pro3.1. If/when we upgrade to 3.3 or 3.5 (this is probably our target) this tool would be an option.

‎03-20-2025

Thanks, that looks like a useful approach. In terms of migration, I have a foot in each camp. We had previously gone live with un3 on 10.8.1 but due to other factors we are doing a new migration to 11.1 un6. For migration I have all the tooling in the database, but also looking to the future post new go live of how a general user can filter and search for targeted errors where they will only have Pro. Let me take your suggestion to one of the team and confirm this will work and provide the requested approach.

‎03-20-2025

Thanks David. I'm really chasing where there can be >1 error type. Something like E25 and E9 both present (but i dont know what is there I just want all the errors of each type that I can filter to). So E25 = 2 power 25 + E9 = 2 power 9 = 33,554,432 + 512 = 33,554,944 Where there is only one error present its fine. Any ideas?

‎03-20-2025

With the topology errors being stored as bitwise values in the dirty areas layer, how can I filter to just specific errors? This needs to be in ArcGIS Pro. For the migration of our data I can report from a database level, but for the general users who will not have database access (and in our production environments we have heavily restricted database access) they need to be able to find through Pro. I did try building some definition queries on the DAs layer, but this only works were there is a single error. For example with Error 25, this works fine for E25. ERRORTYPE = POWER(CAST(2 AS BIGINT),25) How do users filter to specific errors when bitwise is not supported in def queries? We are currently using Ent11.1, ArcGIS Pro 3.1, UNv6.

‎03-12-2025

@MikeMillerGIS yes looks like its better in 3.3. Is that something you are looking to correct for 3.1?

‎03-12-2025

I will let you know when I have some 3.3 with the tool. This is the quick def query view of the data. I am expecting about 8000 errors so hopefully 3.3 provides an aligned output.

‎03-12-2025

Possible to share let me get back to you, and yes I can hook up a 3.3 with the tool and review.

‎03-12-2025

Thanks Mike, but what about specific examples like E29 where this should not have 2 feature classes driving the results and therefore increasing the number? And the fact this particular error is showing 25K errors while the network property value is 11K in total for points or 15K in total for all errors? This is an important item as for this error type has never been high (under 1000 on our original go live on UNv3) and is now significantly higher (25K). I am trying to determine the correct reporting and focus of the issue.

‎03-11-2025

Hi I'm hoping @MikeMillerGIS you can assist here in understanding the output from the "Summerize Utility Network Errors Tool" within UtilityDataManagementSupport toolbox, vs looking at the errors themselves. At the moment our migration partner is using your tool for reporting which is creating some concerns about volumes. I have downloaded the toolbox from GitHub - Esri/Utility-Data-Management-Support-Tools at 3.1, but I dont see aligned numbers. We are in the middle of a remigration of data (long story not worth the discussion) and when I use the toolbox for topology error counts there are ~25K errors for Error29 alone reported (item1) but in the network properties there is only ~11K point errors in total (item2), and using SQL at the database supports the network properties, and specifically for error29 only reports 7,904 errors (item3). Can you please assist in understanding why there are such large numbers reported in the toolbox report. Thanks Damien

‎02-27-2025

Hi Dani We created our own data model with one structure network, and an electric and communication domain network. Our comms is just the bearer network (not all the individual fibres). We have had no issues with both electric and communication equipment on the same poles, or in the same trench and conduit systems. Damien

‎11-20-2024

We have been working with professional services on this one. They have created BUG-000171403 for this issue. Its a pretty buried config. According to the product engineer, the CAV issue is ‘as expected’. This is expected behaviour because of the Auto-Apply option on the layer's table- screenshot below. Behaviour is repro at 3.1.7 and 3.4 when the option is checked and not repro when the option is unchecked. Prior to 3.2, this option was checked by default. At 3.2, the default was changed to be unchecked b/c of this unexpected behaviour. Which is why we don’t reproduce this on 3.3.

‎09-02-2024

Hi We are in the process of uplifting from Pro 2.7 to Pro3.1 and have found contingent values are working differently and changing the selected asset type. We have a large number of contingent values and in many cases have configured the rule to use "<ANY>" for the Asset Type. When we select a new asset to create and populate the value with contingency on it, the asset type is changed based on the first value found in the list where the asset type is not <ANY>. Below is a snip of the rules and example. I selected a new asset of Underground Low Voltage, needing to populate the "nominal voltage", "Phasing" and "number of conductors". When a voltage of 415V is selected, the asset type changes to Overhead service cable low voltage - the first named asset type for 415, ignoring the <ANY> classes. This is not the behaviour in Pro2.7 and although we can manually reset the asset type after populating these fields, is this really the expected bahaviour in pro3.1?

‎09-02-2024

I am trying to consume a service from our ArcGIS Server 10.31 dataset into Pro with our utility network dataset and cannot get the transformation to work. The UNM data is in GDA2020 (EPSG7844), and the older data is web mercator (EPSG3857). This appears to be an incompatibility between AGP 3.1.x to ArcGIS Server 10.31. It is noted that AGS 10.31 is no longer a supported product. It's noted that AGS 10.31 does not support GDA2020 transformation and it has to be done manually through a client application (like AGP 3.1.x). When adding Web Auxilairy sphere services (EPSG 102100, 3857), the 3.1.x AGP client application does not apply the spatial transformation locally for map objects set in GDA2020. The service fails to display geometry. Is this a known issue? Does anyone have an approach to overcome this?

‎08-07-2024

Thanks @RobertKrisher I will pass this information back to the team and get back to you.

‎08-07-2024

Thanks @RobertKrisher. I will discuss with the team. With our upgrade project we have been advised to keep the pro and enterprise version aligned. This means we need to remain on pro 3.1.x.

Online Status	Offline
Date Last Visited	‎10-20-2025 02:51 PM

My Ideas

Latest Contributions by DamienPyne

Re: Displaying and filtering topology error codes in ArcGIS Pro

Re: Displaying and filtering topology error codes in ArcGIS Pro

Re: Displaying and filtering topology error codes in ArcGIS Pro

Displaying and filtering topology error codes in ArcGIS Pro

Re: Reporting topology errors

Re: Reporting topology errors

Re: Reporting topology errors

Re: Reporting topology errors

Reporting topology errors

Re: Comms Utility Network with Electric UN

Re: Contingent values changes the subtype selected

Contingent values changes the subtype selected

ArcGIS Pro3.1 transformation issue

Re: Find subnetworks tool is now case sensitive

Re: Trace subnetwork error message globalid cannot be copied

Re: Comms Utility Network with Electric UN

Re: Contingent values changes the subtype selected

Re: ArcGIS Pro takes the screen focus

ArcGIS Pro takes the screen focus

Re: object snapping not aligned to grid location

APAC Utilities Community of Practice