Latest Contributions by JonDeRose

‎09-08-2020

Correct Robert Thomson‌ You can simply delete the trace network and recreate this using complex edges.

‎09-04-2020

Hi Rafael - SOURCEID is a long integer field and FEATUREGLOBALID is a guid. Please note that you must supply the Source ID and Feature Global ID value for the feature on which you are placing the starting point.

‎09-03-2020

Good morning Robert Thomson‌ - Is the issue in this case that you cannot select the features which correspond with the point errors or that there is no corresponding point feature with a GUID matching that displayed in the Origin Global ID field? Error 25 can generally be resolved by selecting the two points at that location and either relocating or deleting one of the two. If you turn off the point errors sublayer are there any point features displayed in that location and are they set as selectable? Thanks, Jon

‎08-13-2020

Introducing the new trace network dataset with ArcGIS Pro 2.6. This is one of the videos shared as part of the ArcGIS Blog Introducing the Trace Network with ArcGIS Pro 2.6

‎08-13-2020

Explore the various trace operations, concepts, and options available with the trace network in ArcGIS Pro. This is one of the videos shared as part of the ArcGIS Blog Introducing the Trace Network with ArcGIS Pro 2.6

‎08-13-2020

Understand how the network topology improves performance and maintains data integrity in the trace network. This is one of the videos shared as part of the ArcGIS Blog Introducing the Trace Network with ArcGIS Pro 2.6

‎08-12-2020

Learn how network attributes enable greater control over traversability and filtering of trace results in the trace network. This is one of the videos shared as part of the ArcGIS Blog Introducing the Trace Network with ArcGIS Pro 2.6

‎07-30-2020

Simpy Jaiswal‌ Are you still encountering this behavior? I am curious what you see in the point and line error features and dirty areas attribute tables when this issue is present. Are you able to re-create the issue by generating a scenario with error 36? When you validate the extent are error features created in the toaster at the top right of the screen or does it indicate that no dirty areas exist? If reproducible could you provide some screenshots to display the issue and provide the version of ArcGIS Pro/ Enterprise are you using when this is encountered? Thanks, Jon

‎07-30-2020

Jamal NUMAN‌ @Manoj and @Hamed are correct. Please reference my response in the related thread here for additional detail. https://community.esri.com/thread/257080-arcgis-pro-25-the-utility-network-no-junction-edge-rule-error-is-popped-up

‎07-28-2020

Hi Jamal NUMAN‌ - The rule states that L1 can be connected with L1 via D2. However, in the sample above, L1 is connected to L1 without D2, nevertheless, the “validate network topology” tool fails to catch this error In the case you mention above, am I correct in assuming that each L1 feature has the same Asset group/Asset type? If so, this would not create an error on validate or enable as connectivity is supported between edge features with the same asset group/asset type. These connect via a System Junction in the topology. This is mentioned in the Feature restrictions topic here: Feature restrictions—ArcGIS Pro | Documentation Thanks, Jon

‎07-20-2020

Jamal NUMAN‌ Thank you for reaching out with this issue. The reason for this error is that you are using a feature class for starting points that does not posess the necessary schema. Any feature class can be used as a Starting Point or Barrier as long as the feature class has SOURCEID and FEATUREGLOBALID fields which are populated with info from the associated network feature. For example, in the below screenshot I have created a new feature class to store my starting points. This contains two records with points that lay upon a pipeline layer with SOURCEID = 10. Only one of the two is populated with a FEATUREGLOBALID however which corresponds with the GLOBALID of the feature on which it is placed. Starting points without both the SOURCEID and FEATUREGLOBALID populated are ignored, while feature classes input as Starting Points in the trace tool without thee fields will cause the trace to fail. TERMINALID is optional. From this error, I can see that this needs to be communicated more clearly and we will update the error as well as the topics that discuss Starting Points and Barriers in more detail to address this. I hope that helps, please let me know if you have any issues. Thanks, Jon

‎07-16-2020

HiBrad Jones‌ - Glad to hear of the interest in moving to ArcGIS Pro and the Trace Network. Unfortunately, branch versioning is not supported for use in ArcMap. With the initial release in 2.6, it is important to note that the trace network is supported in the file geodatabase alone. It is on our plan to extend support for Enterprise and enable multi-user editing with branch versioning for the trace network in the next release. Thanks, Jon

‎07-07-2020

This document is intended to respond to commonly asked questions received from users of the trace network. Please contact the trace network space owners to request additional questions to be added to the FAQ. (Last updated July 14, 2021) What is the trace network, and who is it for? The trace network was released with the ArcGIS Pro 2.6 release in July 2020 and was designed as a path forward for geometric network users who are not utilities or telecoms (those users should move to the utility network). The new network type uses a simple approach to network modeling with the benefits of the updated environment and implementation you find with ArcGIS Pro. The target audiences for the trace network are hydrology (streams), rail, and other disciplines. Capabilities of the trace network with the ArcGIS Pro 2.6 release include: Tools to migrate directly from a geometric network, or to start from scratch with a new network. Full editing capabilities against the network features including rubberbanding of connected edges. Ability to set flow direction based on the digitized direction of the lines Tracing capabilities based on flow direction for connected, upstream, downstream, and shortest path traces using network attributes (weights). Ability to create network diagrams (schematics) from selected features in the network. File geodatabase support. The ArcGIS Pro 2.7 release introduced support for enterprise deployments with ArcGIS Enterprise 10.9 as well as named trace configuration capabilities to enable the storage and sharing of complex trace configurations in Pro and through web maps. How does the trace network differ from the ArcGIS Utility Network? There are many similarities between the trace and utility network; however, key differences in functionality are present due to the different use cases targeted for each dataset. The below table outlines the key pieces of functionality which differentiate the trace network from the utility network with the ArcGIS Pro 2.7 release: Plans exist to add the following capabilities in later releases: For the trace network: Connectivity and containment associations For the utility network: Trace by Flow Direction

‎06-17-2020

Welcome and thanks for joining the Trace Network GeoNet community Let’s get started! To begin, we invite you to first review the group features on the overview page and familiarize yourself with the group info, space owners, and GeoNet terms of use. As you explore the group, you'll also find tools to connect and collaborate. We encourage you to use the Trace Network GeoNet community space to ask/answer questions, share files, and participate in discussions. We invite you to post a comment below to say "hello" and introduce yourself or share what you are looking forward to working on with this initial release of the trace network. We're excited to connect and collaborate with you and we look forward to seeing your contributions. - The Geodatabase team

‎02-28-2020

Rachel, I’ve updated the compatibility note you mentioned to indicate that adding contingent values to a table or feature class will make it incompatible with ArcMap and have moved this to the top of the help topic for better visibility. Additional help topics are under development to clarify situations such as this where schema changes impact the backward compatibility in ArcGIS Pro and/or usage in ArcMap. Adding Contingent Values to a feature class updates the schema in a way that makes the dataset incompatible with previous versions of Pro and Enterprise that do not share the associated libraries. This same limitation prevents ArcMap from using the updated feature classes. There are not currently any plans to enable the use of contingent values in ArcMap; however, work is underway to expose these capabilities in Runtime so that Runtime clients can read and open datasets with contingent values and expose them. This will pave the way for expanded usage in editor apps beyond ArcGIS Pro.

Online Status	Offline
Date Last Visited	‎04-08-2026 01:25 PM

My Ideas

Latest Contributions by JonDeRose

Re: Change simple edge to complex edge?

Re: ArcGIS Pro 2.5: Utility network tracing with “connected” type ends up with “invalid tracing locations schema” error,

Re: Dirty Areas that can't be resolved

Overview of the Trace Network in ArcGIS Pro 2.6

Explore Trace Operations in the Trace Network

Network Topology in the Trace Network

Network Attributes in the Trace Network

Re: Can we have Line or Point Error without Dirty Area while fixing Topology error in UN?

Re: ArcGIS Pro 2.5: The utility network “validate” tool fails to catch violation of connectivity rules,

Re: ArcGIS Pro 2.5: The utility network “no junction edge rule” error is popped up,

Re: ArcGIS Pro 2.5: Utility network tracing with “connected” type ends up with “invalid tracing locations schema” error,

Re: Editing in ArcMap

Trace Network - FAQ

Welcome to the Trace Network community

Re: Adding Contingent Values to database in ArcPro makes feature class totally unusable in ArcMap? Really?

Re: Add Telecom domain network

Re: Add Telecom domain network

Re: Trace Network Creator vs Publisher (error 0026...

Re: Apply Asset Package on UnTools/Pro 3.3 require...

Re: junction-edge from/to connectivity and relati...