Latest Contributions by EdwardBlair

‎12-26-2018

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

‎12-26-2018

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

‎12-26-2018

Created a subnetwork controller for a pipeline distribution system (a custody transfer meter), tracked down and resolved validation errors and am trying to update the subnetwork. What I get is below. The server log shows the same, somewhat cryptic error. Is there a way to find what specific field or fields the Update Subnetwork GP tool was looking for that it can't seem to find? Not sure why there is a field it can't find in the first place as I'm using the UPDM 2018 asset package as my starting place. Any pointers would be much appreciated. Thx, Ed

‎12-24-2018

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

‎12-24-2018

Forgot to update this. I must have been using an old, outdated version of the UPDM model. When I re-started from scratch using the Gas Utility Network Service 2.0 and re-loaded my data I was able to set my subnetwork controller. Ed

‎12-24-2018

Have been wrestling with this one for a while with no progress, so figure its time to ask. I've got a gas distribution network with a network controller defined at a Meter/Customer Transfer device. When I run the "Update Subnetwork" GP tool it completes successfully but the resulting Subnet line stops just a few pipe segments below the controller at what seems to be an innocuous junction - a ConnectionPoint/ConnectionPoint. Here's what it looks like. Also, the trace proceeds through a junction with similar properties at an upstream segment. The junction *is* connected to the network: The junction *is* In Service: Any suggestions or pointers would be much appreciated. Thx, Ed

‎12-23-2018

Thanks Rich!

‎12-23-2018

This seems like a bug, but I may be missing something. Here are the steps I follow: 1. Change to a new version in my published utility network service. 2. Find I want to attempt a change that requires network topology to be disabled. 3. Execute the "Disable Network Topology" GP tool. This completes successfully. 4. Want to re-enable so I attempt to "Enable Network Topology" 5. This results in an error with the message "Operation is only supported on the DEFAULT version" 6. When I return to the DEFAULT version I see that Network Topology remains enabled, just like I left it. So it seems its possible to *disable* network topology on a version below DEFAULT but not possible to re-enable it. If I've missed something any pointers would be much appreciated. Thx, Ed

‎12-19-2018

Paul - Thanks for the clarification. Do we get pretty much the equivalent functionality by examining attributes of the Utility Network error layers? Ed

‎12-19-2018

Am trying to use the Error Inspector to review/repair Utility Network topology errors, however when I click the tool to panel only shows the message "Please select a map that contains error layers". Is this referring to the error layers associated with my Utility Network? If so, these are present (below). I must be missing something. Any pointers would be appreciated. Thx, Ed

‎12-18-2018

Hello - Am trying to modify a subnetwork controller with no luck. The error message says there is an "expected field [that] was not found or could not be retrieved properly". Is there a way for me to identify the field in question? Thx, Ed

‎12-18-2018

Hi Hussein - I originally started with an empty map and added to it layers, one-by-one from my client-server Geodatabase and then assigned symbology to asset groups/asset types that are actually present in my sample database. I added the utility network at the end and opted to not include layers as that would have duplicated layers I thought were already present. The attached PPT has layer-by-layer contents from the original map (that did not work) and the map started by adding in the utility network and associated layers (that did work). Contents look pretty much the same to me - but I hope this is helpful. Thanks, Ed

‎12-18-2018

Darris - Thank you for the suggestion! Pretty much at the same time Hussein offered a different set of steps that seem to work for me. Much appreciated, Ed

‎12-18-2018

Hussein - Thanks for the suggestion. These steps seem to work - as in, I can add the resulting feature service to ArcGIS Pro, edit things and the Utility Network toolbar is enabled. The attached has a blow-by-blow account. Am not sure what steps are different than what I had done before (and which failed). Other than the way the map was composed. In my work flow I included individual feature classes in the map one by one (PipelineLine, PipelineDevice, etc.) and then added the UtilityNetwork choosing to not add all layers -- they were already in the map. Wonder if this made a difference. Anyway, I seem to have a path to follow. Thank you very much! Ed

‎12-17-2018

Paul - Thanks for the feedback. Updated the images in previous post. Hopefully they show up now. If I just publish a brand new UN without the UPDM package the layers would be empty, true? So you're suggesting to test whether the empty feature service layer would show up? Ed

Online Status	Offline
Date Last Visited	‎02-04-2024 10:20 PM

My Ideas

Latest Contributions by EdwardBlair

Re: Update subnetwork - "expected field was not found"

Re: Update subnetwork - "expected field was not found"

Update subnetwork - "expected field was not found"

Re: Update Subnetwork Stops at an (arbitrary?) Junction

Re: UPDM 2018 Edition

Update Subnetwork Stops at an (arbitrary?) Junction

Re: Disable Network Topology in a Version

Disable Network Topology in a Version

Re: Error Inspector

Error Inspector

Re: UPDM 2018 Edition

Re: Failed to add Utility Network Feature Service Layers

Re: UPDM 2018 Edition

Re: Failed to add Utility Network Feature Service Layers

Re: UPDM 2018 Edition

Re: IZAware in ArcGIS Pro SDK

Re: Utility Network and Geographic Coordinate Syst...

Re: Failed to add Utility Network Feature Service ...

Re: ArcGIS Pro and ArcGIS 10.2.1

Re: Update Subnetwork Stops at an (arbitrary?) Jun...