{
 "currentVersion": 11.1,
 "cimVersion": "3.1.0",
 "serviceDescription": "Traces upstream or downstream based on Arc Hydro standard attributes.  Two possible sets of Arc Hydro attributes are used in tracing and must exist in the input trace feature class.\u201cFrom_Node\u201d and \u201cTo_Node\u201d\u201d.  This will normally be associated with line features.  The \u201cFrom_Node\u201d indicates upstream of the trace feature, \u201cTo_Node\u201d\u201d indicated downstream of the trace feature.  This pair will allow tracing through systems with flow splits (braided and non-dendritic systems).\u201cHydroID\u201d and \u201cNextDownID\u201d.  This can be associated with any type of features (points, lines, polygons).  This tool does not use flow split table if one exists, so using these attributes will produce trace results that pick only one branch at flow splits (the one indicated by NextDownID).  This can be used to return only the main flow path in a braided system.  Note that NextDownID has to point to the HydroID of the main path downstream feature.Only one of the sets must be present in the feature class, but it is valid to have both.  The tool will first look for from-to node set and if not present, will use HydroID-NextDownID set.  If parameter \u201cPropagation Count\u201d is set to 1, HydroID-NextDownID will be used if present.For systems that are non-dendritic to trace through all downstream paths use from-to node attribute pair and set \u201cTrace Propagation Count\u201d parameter to 0.  To trace only through main flow path set \u201cTrace Propagation Count\u201d parameter to 1.  That will default to use of HydroID-NextDownID set for tracing.  You have to ensure that NextDownID stored in the input trace feature class is HydroID of the downstream main path. The start and barrier points can be either entered interactively or be in a point feature class.  One or many points can be used to initiate the trace (barrier points are optional).  If entered interactively, they are stored in a temporary feature class that will be overwritten each time the tool is run.  If you want to keep points from the previous run and just add to them, or change direction of trace, rerun the tool using \u201cResults\u201d instead of running the tool through toolbox \u2013 this will maintain existing interactive points.  Or persist the points by exporting them into a permanent feature class before running the tool and then use that as the input. Selection of start and barrier trace features is based on spatial selection from start and barrier input points using \u201cSearch Distance\u201d parameter.  Any trace features found within search distance from input points will be used as start or barrier features.  To precisely control the trace features to use, best practice is to snap the point onto the trace feature and set the \u201cSearch Distance\u201d to 0.  The trace result is stored as a feature layer called \u201cts_result\u201d.  After each run, this layer is refreshed, so only the last trace results are maintained.  To make that permanent, you have to save the layer into a feature class.\u201cTrace Propagation Count\u201d parameter can be used to limit the upstream or downstream trace through each trace feature.  It indicates how many upstream or downstream features will be maintained at each feature when tracing.  The value set to 0 will use ALL found upstream/downstream features, so there will be no limit on the trace propagation.  Value of 1 will keep only one feature (randomly selected from the set if more than one is found). 2 will keep 2 (if available), and so on.  For example, if \u201cTrace Propagation Count\u201d is set to 1 and you do:Downstream trace.  If there is a flow split (divergence) at a feature, only one of the downstream diverging features will be selected and trace will continue only through it.Upstream trace.  In a typical dendritic system, every feature will have more than one upstream feature (unless they are head features or there are pseudonodes in the system).  In this case only one (random) upstream branch will be used to continue trace upstream.",
 "tasks": [
  "Advanced Trace by AH Attribute"
 ],
 "executionType": "esriExecutionTypeAsynchronous",
 "resultMapServerName": "",
 "maximumRecords": 10000,
 "capabilities": "",
 "schema": {
  "json-schema": {"url": "https://cw-gis-trn.waterboards.ca.gov/hosted/rest/directories/arcgisoutput/StreamTrace/tracetolocatevip_s20_GPServer/StreamTrace_tracetolocatevip_s20/spec/json-schema.json"}
 }
}