Latest Contributions by EdwardBlair

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

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

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

Don't know if this is a question/issue specific to UPDM or if its general to the Utility Network, but going to give it a try.   (Tom D - please let me know if I should post elsewhere.) I've loaded my own sample data into a UPDM 2018-based asset package -- first changing the spatial reference and then appending data to the pipeline feature classes.  Validated the network topology and only a handful of topology errors remain.   Published map/feature services.   Now I can open and edit feature services in the Enterprise "Map Viewer", which I take as a good sign.  Here's the feature layer as I see it in Enterprise:   And here is the data as displayed in "Map Viewer":       However, when I try to add these services to ArcGIS Pro I get nothing.  Examining the server log shows  a bunch of "operation was attempted on an empty geometry" errors (below).  I've triple checked the source data and there are no features that have an empty geometry.   Also, I checked the service and it *is* enabled for the Utility Network (below). Scratching my head here.   - Is Pro sensitive to lines with parametric curves?  There was one in the source data.  I deleted it and still get these errors. - The database is SQL*Server 2017.  Is there something about geometry data storage in this database that Pro doesn't like? - Some features have no data - StructureJunctions, for example.  Does Pro not like this? - There is one table in the map service - its part of the Utility Network and called ValveInspection.  Is this an issue? - Is there something about the coordinate system?  My data is in UTM meters - UTM 1983 Zone 16N.   I usually attempt to add data to an empty ArcGIS Pro map, and the map seems to take on the coordinate system of my data.  I've also tried changing the map coordinate system to the data coordinate system before adding it.  Same results. - I'm getting my ArcGIS Pro license from ArcGIS Online but my portal in on the local test machine I've set up - would this be an issue? Any pointers would be appreciated. Ed     ... View more

Wonder if this could be related to the Error Layers that are associated with the Utility Network that's in the map?  I've tried publishing the service with these things turned on and turned off and have seen no difference.   ... View more

Yep.. Seems to be https://pro.arcgis.com/en/pro-app/help/data/databases/database-requirements-sqlserver.htm ... View more

Michael - As I've spoken with Tech Support (a couple times now) this was not mentioned as a problem. Guess I can double-check. Thanks for the feedback. Ed ... View more

A little more info here.  Rebuilt the source database with a smaller set of data.   Validated the network topology and only a handful of topology errors remain.   Re-published map/feature services. Now I can open and edit feature services in the Enterprise "Map Viewer", which I take as a good sign. However, when I try to add these services to ArcGIS Pro I get nothing.  Examining the server log shows  a bunch of "operation was attempted on an empty geometry" errors (below).   Scratching my head here.   - Is Pro sensitive to lines with parametric curves? - The database is SQL*Server 2017.  Is there something about geometry data storage in this database that Pro doesn't like? - Some features have no data - StructureJunctions, for example.  Does Pro not like this? If anyone has seen this kind of thing any pointers would be appreciated. Thx, Ed ... View more

Found that there are no truly "empty" geometries in the data, though there are some lines that are quite short.   Need to find out what geometry characteristics that server uses to conclude that a feature geometry is "empty"... ... View more

I think I found my problem.  Its at least *one* problem anyway.  Checked the server log and found that it was choking on a feature with an empty geometry.   Need to see if I can find and resolve the offending feature. Ed ... View more

Xander - Thanks for the feedback. I followed the steps in Gas Utility Network Configuration <http://solutions.arcgis.com/gas/help/gas-utility-network-configuration/> to the best of my ability. Though I admit that I'm not sure if the results of the deployment tool <http://solutions.arcgis.com/shared/help/deployment-tool/#what-you-get> were complete or correct. I was just hoping that the error message I got when trying to add the feature service layers would have a little more info. Ed ... View more

It seems to be that when the data from the asset package is loaded (appended) into the utility network feature class the '0' GlobalIDs all get updated with new, valid GlobalID values.  At least that's my initial experience.  Would be good to hear from Esri on this, though. Ed ... View more

Remi - Thanks for the info. It was a data migration partner who said that their tools would not work with data in a geographic coordinates. I guess on reflection this wouldn't mean that UN itself doesn't support data in geographic coordinates. Thanks again, Ed ... View more