Latest Contributions by EdwardBlair

Well yes. I presume that Append uses the Python API. Was just wondering if a similar thing was present in the .NET API. Apparently not. Thanks for the info! Ed ... View more

Hey Rich - I was hoping to be able to create UN features in an edit operation and be able to assign a global ID value from a source feature. Reason being would be that this could preserve global ID values set in a staging database that were used for building associations. Without this I'm thinking I would need to build staging database associations and then post-process to update from/to global ID values in the associations. As below. (And as always, I may be missing something) await QueuedTask.Run(() => { var createOperation = new EditOperation(); createOperation.Name = "Load features"; createOperation.SelectNewfeatures = false; var atts = new Dictionary<string, object>(); atts.Add("SHAPE", myShape); atts.Add("GlobalID", myGlobalID); createOperation.Create(myfeatureLayer, atts); return createOperation.Execute(); } Thx, Ed ... View more

Looks good. Thanks Charlie! ... View more

Please note, I'm aware of the documentation that describes fetching features from an element -- and that describes many other cool utility network functions as well.  What I can't seem to find is the process to go in the other direction -- that is, get network element(s) from a given feature. Thx, Ed ... View more

So... for some reason I really don't understand when I applied my asset package the subnetwork fields (systemsubnetname, pressuresubnetname and isolationsubnetname) did not get added to all of my Pipeline classes.    What I did to resolve the issue was to back out all the way - removing feature services and deleting the feature dataset, then staging a new utility network and applying the same asset package.  Then loaded data, configured subnetwork controllers and resolved *all* validation errors.  At that point I got "Update Subnetwork" to work. A couple points: 1.  The first (failed) time through I know I reordered fields in the Pipeline classes to make things more readable -- for example, moving LIFECYCLESTATUS to the top.   It *may* have been the case that I changed the visibility of a critical field as well -- I don't think I did, but can't say it wasn't possible.  The second time (that worked) I made no changes to Pipeline class fields at all. 2.  Rather than having to resolve *all* validation errors it may have been the case that I could have set some trace barriers to isolate the "good" part of the network from the "bad" and thus followed a piecemeal approach to validation. 3.  It would still be good when receiving an error message that says "Expected field could not be found" that the software would also tell you *which* field it was looking for. Got some pointers from Esri tech support along the way - for which I say "thank you"! Ed ... View more

Mark - Am curious how the CP subnetwork definition has gone.  In a small test I added anodes and test points connected to steel pipe by bond wire.   When I then tries to update my distribution subnetwork I got errors about finding invalid devices -- the anodes and test points.   Did you somehow exclude bond wire from the distribution subnetwork? Thanks, Ed Blair ... View more

I'll try.. but I didn't change field visibility, just the field order. ... View more

For what it's worth, I re-ordered fields in the PipelineLine and PipelineDevice classes before publishing the feature service.   For example, moved the LIFECYCLESTATUS field closer to the top so its easier to see.  Would this make a difference? Thx, Ed ... View more

Paul - Thanks for the reply.  Yes,actually it seems I can run a subnetwork trace. Ed ... View more

Totally a data error and my bad.  While the junction at the end of the pipe had a life cycle status of In Service, several connection points along the pipe, where services connect, had a life cycle status of Unknown.  Once this was resolved the trace completed as expected. Ed ... View more