Latest Contributions by JonDeRose

@GIS_Solutions Are you running into this issue with UN on File Geodatabase or Enterprise? I beleive this is file... The issue is likely with the index on SubnetLine.  Could be a result of the current update adding a very large subnetwork to a class previously populated with much smaller features.  Agree with @Anonymous User above that dropping the spatial index, running Update Subnetwork, and then recreating the index should allow you to move past this. ... View more

Good morning @RandyCasey  If I am reading your post correctly...there is no requirement to downgrade ArcGIS Pro to manage earlier versions of the utility network dataset.  We are in the process of updating the matrix you reference to clarify compatible releases as it can be read that management of a dataset such as UNv3 is tied to a specific version of Pro (but this is not the case).  When this matrix was authored, the intent was to display the UN version created using the listed combination of companion releases (i.e Pro 2.5 creates a version 3 UN which requires ArcGIS Enterprise 10.7 or later.)  This would be better represented by stating that the compatible versions for a Utility Network Version 3 are Pro 2.4 and later and Enterprise 10.7 and later. Two general rules from ArcGIS Platform Compatibility Later versions of ArcGIS Enterprise can share earlier versions of the utility network. Later versions of ArcGIS Pro can be used to view and edit earlier versions of the utility network. You can use any version of ArcGIS Pro to connect and work with the utility network in ArcGIS Enterprise as long as the Utility Network Version is supported by that release. To provide a couple examples, I could ArcGIS Pro 2.9 with a Utility Network Version 4 in ArcGIS Enterprise 10.8.1 or later because both Pro and Enterprise are compatible with version 4 UN's.  Earlier releases cannot open utility network datasets that participate in newer functionality. For example, you cannot use ArcGIS Enterprise 10.7 to share a Utility Network Version 4 or consume a Utility Network Version 5 using ArcGIS Pro 2.6.     Likewise I could use ArcGIS Pro 2.8 with a Utility Network Version 3 in ArcGIS Enterprise 10.9 because this version of the UN dataset is supported with Pro 2.4 and later as well as Enterprise 10.7 and later. Beginning with ArcGIS Pro 2.7 in an enterprise deployment,  the version of ArcGIS Pro and ArcGIS Enterprise determines the Utility Network Version when you create a new utility network or upgrade and existing one; however, this only governs the version created, not the versions that can be used to interact with the dataset.  Let's say you were using ArcGIS Pro 2.7, an earlier version of the UN dataset (such as Utility Network version 4) could still be created if you were connected to an earlier version of ArcGIS Enterprise (such as Enterprise 10.8.1).   I hope that helps to clarify, if I have misunderstood please let me know. Jon     ... View more

Hi Robert, Yes, the fix for this issue was included with 2.9 and the recent 2.8.2 patch. ... View more

Hello Bryce, I have not come across this when converting geometric networks.  Are you still encountering this issue?  Is this reproducible? ... View more

@GavinRunyon While it sounds as though it has the potential to cause confusion when placing trace locations and  interpreting trace results due to the duplication of features, the current method of modeling would not flag these as errors as the two lines would not technically be connected, each would remain modeled as its own edge feature.   ... View more

@curtvprice We have a couple of ArcGIS Learn lessons in the planning stages at the moment to cover various usage scenarios.  Within one, we aim to cover the conversion process, taking an NHD dataset and converting the existing geometric network into a trace network.   Is this what you refer to when you mention a  "tutorial of how to load NHD into the trace network." ? ... View more

When you have an edge (line) connected to another edge midspan, as long as they share the same AG/AT the same principle applies because we are focused on edge elements instead of the line (edge) feature itself. In scenario 1 and 3, a system junction is placed (hidden) midspan on the line, updating the line to be composed of multiple edge elements.  So, in this scenario the two edge elements share the same endpoint. For connectivity to be established midspan in the first place you need to ensure the line feature supports midspan connectivity by setting the edge connectivity policy for the AG/AT.  A picture using your example 3 might explain it better: Another way of looking at it.  When a line in the utility network has another feature connected midspan, it creates another edge element for the line.  Edge elements compose the logical component of edge (or line) features in a utility network. A complex edge (which all UN line features are)... is a feature is associated with a set of junction and edge elements in the logical network. Hope that helps to clarify.   ... View more

@GavinRunyon If two edge elements share the same endpoint and have the same Asset group and Asset type, these features can connect without a user-defined intermediate junction or network rule. In this situation, a system junction is created and connectivity is established when the network topology is validated or enabled. If I understood your question properly, it sounds like your Water Line subtype Services share the same Asset group and Asset type.  As a result they could be connected to each other without the creation of a specific network rule to model the split. The feature restrictions topic covers this in a little more detail.   Thanks, Jon ... View more

Emerson,  Is this a reproducible from a backup?  From the error it appears as though the upgrade is attempting to add the SUPPORTEDSUBNETWORKNAME field as a non-nullable field; however I am not sure why that would be the case.   When upgrading a UN from v3 to v4 this field would be added to classes as a nullable field.   How does this UN dataset differ from the other two that succeed? What is more concerning is the reference you made about the upgrade process unregistering your data as versioned.  It would be interesting to investigate this further. I found the support case you referenced.  If this remains reproducible I recommend that you work with the analyst through that case to provide the backup and reproducible case for analysis. Jon   ... View more

@NickHarvey I'm glad that Alex was able to provide you with the solution.  This also highlighted an oversight in the documentation that should have been updated with the ArcGIS Pro 2.8 release.  We've made the change for the next release.  While the note still holds true when tracing through loops without directional devices, the updated note should read:  "When loops are encountered during an upstream or downstream trace, trace results will return all features in a loop unless devices with a directional terminal configuration are present." ... View more

@DavidDamian I am not able to reproduce the issue you reference in testing on Pro 2.7 or more recent releases.  If the issue persists please reach out to Esri Support to investigate this issue. - Jon ... View more

There are no plans for future development in ArcMap.  It is possible to edit a Trace Network in ArcGIS Pro while projected on the fly, however. The trace network shares a common framework with the utility network but was designed with existing nonutility users of the geometric network in mind.   Existing geometric networks can be easily converted into a trace network starting with ArcGIS Pro 2.6.  ... View more

Which Pro version are you using when this is encountered and are there any additional details reported in the server manager logs or via Fiddler when the issue is encountered?   The error itself points to an issue with a recent geometry update, are any similar issues encountered with Validate?   Jon ... View more