Latest Contributions by EdwardBlair

There you go! That did it. Thanks Robert!

Yes. The fuse has terminals. Kind of confusing. But if that's the way it works its good to know. Thanks for the info. Ed

Here goes... Devices in in the category "E:Switch -Fuse" are defined as barriers for this trace. Option to include barrier features is un-checked. Trace is executed stopping at fuses, but fuses are included in the result.

Sorry I missed this post the other day. Thank you for the reply! Unfortunately, as you probably know, having to do the trace to derive the flow direction has a bunch of drawbacks. Thanks again, Ed

In the Geometric Network using ArcObjects you can dig in to the details of a network edge and determine its flow direction -- which is useful in a number of circumstances, including if you want to determine the source side and load side of a given electric device (in a radial network). I can't seem to find an equivalent way to do this with the UN and the Pro SDK, but I could be missing something. Any guidance here would be much appreciated. Thx, Ed

We just started trying to use the ConductorDetail table to hold rows describing conductor phase and neutral wires. I noticed that when we split a conductor these are not duplicated to both new features. Is there a way to configure this behavior in the UN database? Thx, Ed

Hi - Thanks much for the feedback/suggestion. We'll definitely look into this approach. Much appreciated, Ed

All - We represent discovered cross bore locations as simple point features in our current gas distribution ArcMap/GN implementation. I don't see a direct correspondence in the UPDM - but I may be missing something. Any guidance/suggestions here would be much appreciated. Thx, Ed

This has been happening for me on and off and its really annoying -- and a total productivity killer. I'm using Pro 3.5. Any updates since the original issue was posted 7 years ago? Ed

Hello - I'm probably missing something stupid, but I can't get a Utility Network downstream trace to exclude barriers from the result set. I'm setting the TraceConfiguration IncludeBarriersWithResults to FALSE -- see below. But the results returned always include the barrier features (which happen to be fuses my my use case.) Note that the equipment *below* the barrier *is* excluded, but not the barrier feature(s) themselves. Any pointers on what I am missing would be much appreciated. Thx, Ed ---------------------------------------------------------------------------------------- using (un) using (UtilityNetworkDefinition utilityNetworkDefinition = un.GetDefinition()) { using (NetworkSource networkSource = utilityNetworkDefinition.GetNetworkSource("ElectricDevice")) using (AssetGroup assetGroup = networkSource.GetAssetGroup(agName)) using (AssetType assetType = assetGroup.GetAssetType(atName)) { DomainNetwork domainNetwork = utilityNetworkDefinition.GetDomainNetwork("Electric"); Tier sourceTier = domainNetwork.GetTier("Electric Distribution"); TraceConfiguration traceConfiguration = sourceTier.GetTraceConfiguration(); traceConfiguration.IncludeStructures = false; traceConfiguration.IncludeBarriersWithResults = false; // proceed to get a tracer from the trace manager and execute a downstream trace with the // above trace configuration

Hi Narelle - Thanks for the feedback! I'll definitely check out the info provided. Ed

‎04-21-2026

@gis_KIWI4 Pretty interesting. Thanks much for the detail. We will check out these options!

‎04-20-2026

Hi @gis_KIWI4 ... thanks much for the feedback. I should have been clearer. For subnetwork change detection we *hope to* use the SE GDBM framework. Thing is, we also need to detect changes to other, non-Utility Network feature classes. This is, at the moment, what I'm most interested in. Ed

‎04-17-2026

... as a follow-up, and possibly clarify this question, we currently get differences between versions by using "version difference" queries.. mostly in FME. These things detect changes by looking at rows in the versioning A and D tables. With branch versioning there are no longer A and D tables, rather there are "born on" and "died on" date fields. So... to find out what has changed over the past period of time, will we request version differences? (and then reconcile when we're done.) Or will we perform "date difference" queries on the branch versioning classes? Ed

‎04-17-2026

Hi all - In our current implementation use use several "static" versions to assist with Geodatabase change detection. For example, there is a nightly process that compares a static version with SDE.Default to determine which feeders have changed in order to inform the OMS interface which feeders need to be extracted and updated in the OMS database. There are other static versions for other, somewhat similar purposes. For OMS we might be using ArcFM GDBM/Feeder Services to detect changes. But for other, non-feeder change purposes, we're wondering if we need to keep static versions around. Any thoughts/experiences on this would be much appreciated. Thanks, Ed

Online Status	Offline
Date Last Visited	Thursday

My Ideas

Latest Contributions by EdwardBlair

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

Re: Setting IncludeBarriersWithResults to FALSE does not seem to work

Re: Flow direction from Utility Network Edge Feature

Flow direction from Utility Network Edge Feature

Duplicating ConductorDetail rows on a Split

Re: Cross Bores in the UPDM

Cross Bores in the UPDM

Re: Stuck on Explore Tool While Editing

Setting IncludeBarriersWithResults to FALSE does not seem to work

Re: Create a UN Association in an Edit Event Handler

Re: Static Versions for Change Detection in the UN

Re: Static Versions for Change Detection in the UN

Re: Static Versions for Change Detection in the UN

Static Versions for Change Detection in the UN

Duplicating ConductorDetail rows on a Split

Cross Bores in the UPDM

Re: Apply Asset Package errors with "OID-based rel...

Re: Apply Asset Package errors with "OID-based rel...

Re: Gas CP Subnetwork Controllers