Trace results

Results from a trace operation can be returned in a number of ways through configuration of the Result Types parameter on the Trace tool.

The Aggregated Geometry, Selection, Connectivity, Elements, Features, and Containment and attachment associations result types can be specified independently or concurrently to generate output geometries, create a selection set for a trace operation, return a connectivity graph of network features connected through either geometric coincidence or connectivity associations, return feature-based information, return feature-based information with geometry, network attribute, and field information, or return features that are associated through containment and structural attachment associations to a .json file, respectively.

Results from a trace include any features or objects that meet the tracing criteria between a starting point or subnetwork controller and a barrier or the end of a path (no more connected network features).

When working with nonspatial objects, trace results may be impacted if editing tools are active when executing a trace. For example, if the Move tool is active when executing a trace, the results do not include junction and edge objects.

The criteria of a trace are controlled by the subnetwork trace configuration and can be altered using the Trace tool. Trace configurations on the Trace tool allow you to control the type of network features returned in the results based on network attributes, asset group and asset types, and association roles. To learn more, see Configure a trace.

When a line feature is traced and returned, the entire line is returned by default in a selection set. When nonspatial edge or junction objects are returned in the trace result, the corresponding row in the object's table is selected. The Result Types option Aggregated Geometry can be specified to return partial feature results in an output multipart geometry class.

If a network feature with terminals is traced, the entire device or junction object is returned. In a source-based network, for example, a subnetwork controller trace is run on a radial distribution subnetwork. The trace travels from the starting point all the way up to the subnetwork controller terminal on a feature, for example, a circuit breaker device. The circuit breaker has two terminals, one to model the logical connection to the source power (transmission), and one to model the delivery of that power (distribution). Although only the terminal that delivers power on the device is traced, the entire point is returned as a selected point feature.


Summaries support apportionable results, for example, calculating the length of part of a pipe (a single line element). To learn more, see Subnetwork trace configuration.

The results of a trace are not guaranteed to be consistent if dirty areas are present in the traceable area. Use the Validate Consistency check box on the Trace tool to look for dirty areas before the trace is executed. When this check box is checked and dirty areas are present in the traceable area, the Trace tool will fail and return an error. This check box is checked by default. It is recommended that you execute traces with validate consistency enabled. To learn more, see Ensure network consistency.

Tools are provided to transfer the selected network features or rows in a result from a trace to another map or diagram view. The Apply To Maps tool is used to propagate the selection set in a map view to another map view; the same network features selected on the parent map become selected on the child map. The Apply To Diagrams tool is used to propagate the selection set in a map view to a diagram view. To learn more, see Propagate trace results.