Latest Contributions by JimmyBowden

‎09-17-2024

When using the Register As Versioned geoprocessing tool it would be nice to include the prerequisites (Globalids, Archiving, Editor Tracking) as options similar to the UI Manage geodatabase functionality as shown below.

‎02-08-2024

There is a UI blocking "Loading locators..." window that frequently popups up when using ArcGIS Pro in version 2.9.8 and 3.2.1 at least. I have several questions: Is this actually loading locators? Is this an incorrect message and ArcGIS Pro is actually doing something else? Why does it need to block the main UI thread? What is the need for ArcGIS Pro to load locators when the locate tool isn't open?

‎12-13-2023

With the release of ArcGIS Enterprise 11.2 the UN extension is no longer available. It has been replaced by the Advanced Editing user type extension. Is this new extension required to run a trace? I don't see any documentation indicating this. @LarryYoung Any update to this idea based on 11.2 licensing changes?

‎09-07-2023

I agree that there's a need to exclude features from validation based on lifecyclestatus. We have similar issues with Approved features. The work around that I came up with was to apply a uniform Z value (-10 for instance) to the abandoned/removed features. This isn't a perfect solution we still had errors to review, but it was preferred to having 1,000s more errors to review. Also note that this may not be a great solution if you desire view your data in 3D.

‎08-28-2023

Over a year ago I posted an Idea to allow read access to branch version data in ArcGIS for AutoCAD. It is currently "under consideration".

‎02-23-2023

@JoseBanuelos Thanks for the update. It is good to know that there is ongoing effort to support subtype layers. This popup is just a simple example of a deficiency of the subtype layer. I look forward to seeing these updates.

‎02-08-2023

@JoseBanuelos Two versions of the api have been released and this still doesn't been fixed. Has there been any progress?

‎02-07-2023

As Mike indicated the Utility Network feature classes are M enabled when they are created. If you are deploying your UN as an enterprise you will want to check the box "Allow geometry updates without m-value" in the Feature properties. This will set the M value to NaN when features are created. At this point you can just ignore them.

‎02-07-2023

If you are using an Enterprise Utility Network ensure that you are connecting to the geodatabase when attempting to make domain changes. Domain changes can only be made when connected to the geodatabase then to see those changes the feature service must be restarted. Some domain changes like to asset type can only be done when topology is disabled. Be aware that changes to asset type will impact your network rules so makes changes with care. Also some fields participate as Network attributes, including operable. Adding a new operable value shouldn't be an issue but will have impacts in some trace situations.

‎10-04-2022

When I run a trace with "Validate Consistency" checked it's possible that the trace will fail because "One or more dirty areas were discovered". The globalids of the features with errors shown in the geoprocessing error report which is helpful. An improvement would be to select these features so the user doesn't have to manually select them.

‎09-19-2022

Thanks @MikeMillerGIS I'm going to try this out and see if it meets our needs.

‎09-15-2022

I have implemented the Water Distribution Utility Network Solution. The system and pressure subnetworks defined in this model use the Lifecycle Status (Does not include In Service and To Be Retired) as a condition barrier. This has caused some issues creating subnetworks with approved to be constructed features and valves that are abandoned in the open position. These features prevent subnetworks from being created correctly by stopping the subnetwork from continuing past devices with those Lifecycle Status values. It is fairly common in our water system that valves, tees, and other junctions are wet tapped into existing waterlines. I'm considering adding a new true/false attribute to the feature classes and the network called "traceable". Generally this would be true for Lifecycle Status In Service and false for Approved, Abandoned, Removed. Then for junctions or devices that connect to in service lines set the traceable to true (the circled features in the image). Then I would remove the Lifecycle Status condition barrier and use the traceable value as the condition barrier. The obvious drawback of this is the some approved features will be included in subnetwork traces before they are installed. Are there other unintended consequences that I'm not considering? @MikeMillerGIS @RobertKrisher @JoelSmith3

‎08-24-2022

On August 4, 2022 a Revised Lead and Copper Rule | US EPA was released. Will the Esri Lead Service Line Inventory Solution be reviewed against these new rules and possibly updated?

‎08-23-2022

When I encountered the same issue I created a constraint attribute rule for each feature class that prevents edits against default. It's actually a simple script (see below) and I haven't noticed any performance issues with it. The biggest drawback is viewing attributes in ArcGIS Pro when in sde.default, you are constantly reminded that you can't edit (attached image). You also have to add it to each feature class but that gives you more flexibility in case you have a feature class or table that it's valid to edit default. var version = gdbVersion($feature) if (UPPER(version) == "SDE.DEFAULT") { return false; } return true;

‎08-04-2022

This is still (maybe more) relevant as the Utility Network makes use of subtypes with different domains applied forcing any client to have handle resolving domains. Currently some of the Esri clients do a poor job of resolving domains (Portal map viewer, Javascript api) so this could be useful for those internal use cases.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by JimmyBowden

Register as Versioned

Loading Locators...

Re: Trace should be possible without an UN extension

Re: Remove abandoned features from active UN

Re: Will the UN Data Model work with ArcGIS for AutoCAD - Free Plug-In between AutoCAD & ArcGIS?

Re: Decode Domain

Re: Decode Domain

Re: Do features need to be M-enabled for Utility Network compatibility?

Re: Assigning a different domain to a field

Select features when trace fails with dirty areas

Re: Water Network Subnetwork Issue

Water Network Subnetwork Issue

Lead Service Line Inventory

Re: Post versions without being version administrator

Re: Automatically Resolve Coded Domains in REST Endpoints and Operations

Register as Versioned

Loading Locators...

Read from Branch Version

Re: Do features need to be M-enabled for Utility N...

Re: Use the getUser Arcade Function to return the ...