Latest Contributions by EdwardBlair

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 ... View more

Thanks Robert - Our use case is this.   We currently represent substation internals in a geometric network separate (spatially and logically) from the distribution network.  As an initial step in our UN journey the thought was to include distribution features in the UN network, but put substation internals into a simpler trace network.  With a long-term goal of incorporating the internals into the UN. Seems to me, knowing what I've discovered about the trace network, this strategy will not work.  A better approach for us may be to include the sub internals in a separate utility network.   But we're still mulling this over. Ed ... View more

Not as far as I can tell.   We need to operate on a set of selected features and determined what they are connected to, with the possibility that they are not connected to anything. Someone had the idea that we could use a Trace Network for this, but it looks like that will not work. Ed ... View more

Again.. I'm not looking for how to perform a trace.   I see that.  What I'm looking for is a way to examine a selected feature that participates in the trace network and discover what other features it's connected to... without performing a trace.  The equivalent of the GN: ISimpleJunctionFeature::EdgeFeature Ed   ... View more

Thanks for this.   I've actually seen the post.   But its not really what I'm looking for.   I should have been more clear.    In the GN you can get a feature cast it to a network object, like a simple junction, and from that find out what its connected to.   You can take similar steps to find what connected to a given feature in the UN.   I need to do the same for features in a Trace Network. Thanks again, Ed ... View more

There you go!   That did it.   Thanks Robert! ... View more

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 ... View more

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.     ... View more

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 ... View more

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

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 ... View more