Advanced Trace by AH Attribute

Input points to be used as starting points for the trace. They are used to select the trace features that will originate the trace. One or many can be defined. They should be placed on or near the trace feature to make sure correct selection is made. The point needs to be within ‘Search Distance’ from a trace feature to be used in tracing. Points can be defined either interactively or as a feature class. If defined interactively, they will be stored in temporary feature class ‘ts_start_points’ in scratch geodatabase. Interactive points are transient in nature. Next run of the tool will overwrite them.{ "displayFieldName": "", "features": [ { "attributes": { "OBJECTID": 1 }, "geometry": { "x": -13539581, "y": 4462328 } } ], "fieldAliases": { "OBJECTID": "OBJECTID" }, "fields": [ { "alias": "OBJECTID", "name": "OBJECTID", "type": "esriFieldTypeOID" } ], "geometryType": "esriGeometryPoint", "spatialReference": { "latestWkid": 3857, "wkid": 102100 } }

Input points to be used as barriers for the trace. They are used to select the trace features that will prevent propagation of the trace. One or many can be defined. They should be placed on or near the trace feature to make sure correct selection is made. The point needs to be within ‘Search Distance’ from a trace feature to be barrier for tracing.Points can be defined either interactively or as a feature class. If defined interactively, they will be stored in temporary feature class ‘ts_barriers’ in scratch geodatabase. Interactive points are transient in nature. Next run of the tool will overwrite them.

“Upstream” or “Downstream”Both would trace in Both upstream and downstream direction.

Distance used to perform spatial selection of trace features used as start and barrier features based on input points. To precisely control the trace features to use, best practice is to snap the point onto the trace feature and set the ‘Search Distance’ to 0. Larger search distance can be used to make multiple feature selections with a single point.

Number of downstream/upstream features at each feature used to propagate the trace:0 – all encountered downstream/upstream features will be used to propagate the trace.1 – only 1 feature will be used to propagate the trace. If trace feature class has fields HydroID and NextDownID, these will be used for tracing, otherwise from-node and to-node attributes will be used.Feature class to be used for tracing. Any type of feature class can be used to trace through as long as it has appropriate fields identifying downstream elements, typically, [HYDROID, NextDownID] or [From_Node, To_Node]. will be used to propagate the trace.

Snap Input Points