Summary
Creates a trace configuration in the trace network.
Trace configurations allow you to configure and store the properties of complex traces for reuse and sharing. Trace configurations stored in a trace network can be loaded and executed from the Trace tool or shared through a map service consumed by a web map or field app.
Usage
The input trace network must be version 2 or later.
When working with an enterprise geodatabase, the input trace network must be from a trace network service.
The connected portal account is listed as the creator of the trace configuration.
Operating system authentication is used to store the creator of a trace configuration when working with a trace network in a file geodatabase.
Syntax
arcpy.tn.AddTraceConfiguration(in_trace_network, trace_config_name, trace_type, {description}, {tags}, {path_direction}, {shortest_path_network_attribute_name}, {include_barriers}, {validate_consistency}, {ignore_barriers_at_starting_points}, {allow_indeterminate_flow}, {condition_barriers}, {function_barriers}, {traversability_scope}, {functions}, {output_conditions}, {result_types})
Parameter | Explanation | Data Type |
in_trace_network | The trace network that will contain the new trace configuration. | Trace Network; Trace Network Layer |
trace_config_name | The name for the trace configuration. | String |
trace_type | Specifies the type of trace that will be configured.
| String |
description (Optional) | The description of the trace configuration. | String |
tags [tags,...] (Optional) | A set of tags used to identify the trace configuration. The tags can be used in searches and indexing. | String |
path_direction (Optional) | Specifies the direction of the trace path. The cost of traversing the path is determined by the shortest_path_network_attribute_name parameter value. This parameter is only honored when running a SHORTEST_PATH trace type.
| String |
shortest_path_network_attribute_name (Optional) | The name of the network attribute used to calculate the path. When running a shortest path trace type, the shortest path is calculated using a numeric network attribute such as shape length. Cost and distance based paths can both be achieved. This parameter is required when running a shortest path trace. | String |
include_barriers (Optional) | Specifies whether the traversability barrier features will be included in the trace results.
| Boolean |
validate_consistency (Optional) | Specifies whether an error will be returned if dirty areas are encountered in any of the traversed features. This is the only way to guarantee a trace is passing through features with consistent status in the network. To remove dirty areas, validate the network topology.
| Boolean |
ignore_barriers_at_starting_points (Optional) | Specifies whether barriers in the trace configuration will be ignored for starting points.
| Boolean |
allow_indeterminate_flow (Optional) | Specifies whether features that have indeterminate or uninitialized flow will be traced. This parameter is only honored when running an upstream or downstream trace.
| Boolean |
condition_barriers [[Name, Operator, Type, Value, Combine Using],...] (Optional) | Sets a traversability barrier condition on features based on a comparison to a network attribute. A condition barrier uses a network attribute, an operator and a type, and an attribute value. For example, stop a trace when a feature has the Code attribute equal to the specific value of ArtificialPath. When a feature meets this condition, the trace stops. If you're using more than one attribute, you can use the Combine Using component to define an And or an Or condition. Condition barrier components are as follows:
Operator components are as follows:
Type components are as follows:
Combine Using component are as follows:
| Value Table |
function_barriers [[Function, Attribute, Operator, Value, Use Local Values],...] (Optional) | Sets a traversability barrier on features based on a function. Function barriers can be used, for example, to restrict how far the trace travels from the starting point or to set a maximum value to stop a trace. For example, the length of each line traveled is added to the total distance traveled so far. When the total length traveled reaches the value specified, the trace stops. Function barrier components are as follows:
Function components are as follows:
Operator components are as follows:
Use Local Values components are as follows:
| Value Table |
traversability_scope (Optional) | Specifies whether traversability will be applied to junctions, edges, or both. For example, in a network of recreational trails, if a condition barrier is defined to stop the trace if the path type is gravel and traversability scope is set to junctions only, the trace will not stop even if it encounters a gravel path, because the path type is only applicable to edges. In other words, this parameter indicates to the trace whether to ignore junctions, ignore edges, or include both junctions and edges in the trace.
| String |
functions [[Function, Attribute, Filter Name, Filter Operator, Filter Type, Filter Value],...] (Optional) | The calculation function that will be applied to the trace results. Functions components are as follows:
Function component options are as follows:
For example, a starting point feature has a value of 20. The next feature has a value of 30. If you are using the MIN function, the result is 20. MAX is 30, ADD is 50, AVERAGE is 25, COUNT is 2, and SUBTRACT is -10. Filter Operator component options are as follows:
Filter Type component options are as follows:
| Value Table |
output_conditions [[Name, Operator, Type, Value, Combine Using],...] (Optional) | The types of features that will be returned based on a network attribute. For example, in a trace configured to filter out everything but Tap features, any traced features that do not have the Tap attribute assigned to them are not included in the results. Any traced features that do are returned in the result selection set. If using more than one attribute, you can use the Combine Using option to define an And or an Or condition. Output conditions components are as follows:
Operator component options are as follows:
Type component options are as follows:
Combine Using component options are as follows:
| Value Table |
result_types [result_types,...] (Optional) | Specifies the type of results that will be returned by the trace.
| String |
Derived Output
Name | Explanation | Data Type |
updated_trace_network | The updated trace network. | Trace Network |
Code sample
This sample script adds a trace configuration named Upstream_HUC12 to a trace network called HydroNetwork.
import arcpy
arcpy.AddTraceConfiguration_un(
r"HydroNetwork", "Upstream_HUC12", "UPSTREAM",
"Upstream trace for HUC12_allow indeterminate", "HUC12;Upstream",
"NO_DIRECTION", '', "INCLUDE_BARRIERS", "VALIDATE_CONSISTENCY",
"DO_NOT_IGNORE_BARRIERS_AT_STARTING_POINTS", "TRACE_INDETERMINATE_FLOW",
None, None, "BOTH_JUNCTIONS_AND_EDGES", None, None, None)
Environments
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes