Latest Contributions by EdwardBlair

Hi Anne-Yvonne- This makes sense. I'll give it a try. Thanks! Ed

FWIW - We've decided to continue our current Delete History detection process going forward with the UN. Even though we could probably find these in the branch versioned tables, the combination of having the information in one known place, plus not needing to worry about the effects of pruning make us feel best about keeping the same process. Ed

Hi – I’m seeing unexpected behavior after I add a new “Network Attribute” to a Trace network. Here are my steps. 1. Disable Trace Network Topology 2. Add a new Network Attribute named “NormalPosition” of data type Long 3. Use Set Network Attribute to assign this network attribute to a (Long) field named NORMALPOSITION_A 4. Enable Trace Network Topology 5. Change the value of NORMALPOSITION_A on a feature from “Closed (1)” to “Open (0)”. Save edits and validate topology. 6. Perform a trace with a barrier defined to stop at NormalPosition = “Open”. The trace stops at the newly opened device, as expected. All good. 7. Change the value of NORMALPOSITION_A on the same feature back to “Closed.” Save edits and validate topology. 8. Perform a trace with the same barrier condition and it STILL STOPS at the device which was changed to “Closed” Any suggestions on what I might be missing would be much appreciated. Thx, Ed

Dan - Thanks much for the reply. Right. I should have mentioned that after creating the features I saved the edits *and* validated the topology. No difference in results. I also tried the "Apply To Diagrams" tool on the "Trace Network" toolbar. Also no luck. Ed

I created a network diagram from a Trace Network. Then tried to apply updates made to trace network features to the network diagram. While attribute updates are applied and show up on the network diagram elements, newly added features do not. I'm probably missing something. Here is my workflow. 1. Network diagram fragment. 2. Add new features to source Trace Network (shown as selected) 3. Run the "Update Diagram" GP tool from the map. There is no change to the network diagram. Any suggestions would be much appreciated. Thanks, Ed

Hello - In our current (ArcMap/GN) implementation we have a process that runs nightly uses version differences to detect any features that have been deleted from SDE.Default in the previous day. Any features found are written to a "DeleteHistory" file geodatabase. Features are never removed from the DeleteHistory database. I won't enumerate, but there are all kinds of cases where a feature/features can get unintentionally deleted. The process has certainly saved my bacon. It seems like branch versioning will retain history of what has been deleted... up until the point where we need to perform a "prune". At least it seems so. My understanding is that "prune" will remove any archived features no longer associated with a version -- meaning it will remove rows that would otherwise describe what was deleted. If this is true, has anyone developed processes to retain delete history beyond the "prune" operation? We're thinking that this *might* be accomplished simply by creating a file geodatabase snapshot before the prune occurs.. though, if we have to search back over multiple "prune" operations we would have to search over multiple FGDB snapshots. Any thoughts or suggestions would be much appreciated. Thanks, Ed

Google Gemini says I should be able to get a reference to a Trace Network using the following code. TraceNetwork traceNetwork = gdb.OpenDataset<TraceNetwork>("MyNetwork"); (see below) I don't see "TraceNetwork" as a valid definition for a geodatabase object when I try this. Am I missing something, or is there another way to do this? Thx, Ed

Hi - Our source data has *many* cases where a surface structure (pedestal, junction box, cabinet, etc.) is connected to an underground structure line (conduit or duct bank) at a mid-span vertex. We were advised by one party that retaining this configuration (allowing connections to "any vertex") in the UN could have adverse downstream consequences. In limited testing in a test mobile geodatabase, this configuration seems to work fine. We create the junction, re-build the subnetwork, move the junction and have the structure line adjust its shape, re-build the subnetwork, and all seems to work hunky dory. Should we be concerned about pursuing this path? The alternative would be to split *many* UG structure lines either in the source or the migration process, which we would prefer not having to do. Any feedback would be much appreciated. Thanks, Ed

Sorry Mike.... I'm an idiot. I had my query on GlobalIDs screwed up. The issue was not with the Pressure Recording device, but rather with Test points... which were *not* in the subnetwork definition. Thanks a bunch for your reply. Sometimes it takes saying the problem out load, or wring it out, to actually fix it. Ed

Hi Mike - Thanks for the reply. I thought it *had* to be in the parent tier to be present in the "child" tier. Anyway, yes, the "Pressure Recording Device/Unknown" is present in both the "System" and "Pressure" tiers. Ed

All - Sorry if I am missing something simple here, but when I try to update a pipeline isolation subnetwork I get an error that process encountered an "invalid device" when I'm certain that device is present in the subnetwork definition. Here are the details. First, here's the error message: I then search for the offending features in the PipelineDevice class using the GlobalIDs listed in the error. Here's what I get (why there are 5 GlobalID values in the error and only one feature returned on the query is another question... but one step at a time.) The offending feature's Asset Group is "Pressure Recording Device" and Asset Type is "Unknown". So I check the subnetwork definition and see this: The Asset Group/Asset Type seems to be present in the Isolation tier subnetwork definition. Any pointers on what I am missing would be greatly appreciated. Thanks, Ed

NM. I should have Googled before posting. Apparently this is an ArcPro SDK convention that indicates the table is defined with traditional versioning. Ed

Hi - I'm just trying to understand what's going on here. I have a stand-alone table from an Oracle database in my TOC named MAXIMO.ZXQSERVPOINT. See below. When, in code, I iterate through the tables present in the TOC the name is returned as "MAXIMO.%ZXQSERVPOINT". See below. What's the deal with the "%" ?? Any info would be appreciated. Thx, Ed

Of COURSE .... its in the next release. You're killing me man. Anyway, thanks for the info. Ed

Hey @RobRob and/or @RichRuh - As documented in the article you reference above, the export subnetwork JSON describes an "un-directed graph" of the subnetwork. Without writing one's own equivalent of a ForwardStar, is there some way to define directionality on this? Currently in the UN we use the ArcFM FeederTrace to create a device hierarchy for a feeder. That is, each device knows its parent device. I was hoping to create the same from a subnetwork export, but am currently stuck on the "un-directed" part. Thx, Ed

Online Status	Online
Date Last Visited	Friday

My Ideas

Latest Contributions by EdwardBlair

Re: "Update Diagram" GP Tool does not add new features

Re: Geodatabase Pruning and Delete History

Add Network Attribute (Trace Network) Issues

Re: "Update Diagram" GP Tool does not add new features

"Update Diagram" GP Tool does not add new features

Geodatabase Pruning and Delete History

Get Reference to a "Trace Network" in a Geodatabase

Adverse effects from setting StructureLine connectivity to "AnyVertex"?

Re: Pipeline Isolation Subnetwork Confusion

Re: Pipeline Isolation Subnetwork Confusion

Pipeline Isolation Subnetwork Confusion

Re: Table Name from TOC returned prefaced with a "%"

Table Name from TOC returned prefaced with a "%"

Re: ForwardStar or something like that

Re: ForwardStar or something like that

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