Output from Find Routes
Upon successful execution of FindRoutes, the service returns the best routes between the stops, and the status indicating whether the analysis was successful, using the output parameters described below.
output_routes
This provides access to the resulting routes.
The following table lists the fields returned for output routes:
|
Field |
Description |
|---|---|
|
|
The name of the route is based on the |
|
|
The number of stops assigned to the route. |
|
|
The start time of the route, reported in the time zone in which the first stop is located. |
|
|
The end time of the route, reported in the time zone in which the last stop is located. |
|
|
The start time of the route in coordinated universal time (UTC). |
|
|
The end time of the route in coordinated universal time (UTC). |
|
|
The cumulative travel time in minutes from the beginning of the first stop to the end of the last stop for a route. This includes any Note:An additional field, Note:Additional fields, |
|
|
The cumulative travel distance in miles from the beginning of the first stop to the end of the last stop for a route. This includes any Note:An additional field, Note:Additional fields, |
|
|
The cumulative travel distance in kilometers from the beginning of the first stop to the end of the last stop for a route. This includes any |
|
|
The cumulative travel cost in unknown units from the beginning of the first stop to the end of the last stop for a route. This includes any This field is included only when the travel mode used for the analysis has an impedance attribute that is neither time based nor distance based. Note:Additional fields, |
|
|
This field stores the route's overall wait time, which is the time spent at stops waiting for time windows to open. The field has a null value if time windows are not used in the analysis. Note:An additional field, Note:Additional fields, |
|
|
This field stores the route's overall violation time at stops. Violation time is added when the route arrives at a stop after the time window has ended; it's the difference between the The field has a null value if time windows are not used in the analysis. Note:An additional field, Additional fields, |
|
|
The unique identifier automatically generated by the analysis of the first stop on the route. |
|
|
The |
|
|
The unique identifier automatically generated by the analysis of the last stop on the route. |
|
|
The |
output_directions
This provides access to the turn-by-turn directions for each resulting route.
Legacy:
This output type has been superseded by the DirectionPoints and DirectionLines output classes, which should be used for all new scripts and workflows.
The shape for the directions feature is determined from the underlying streets included in the route.
The Directions Language, Directions Distance Units, and Directions Style Name parameters influence the travel directions. The parameter returns empty features if the Populate Directions parameter is set to False.
The following table lists the fields that are returned for output directions:
|
Field |
Description |
|---|---|
|
|
The name of the route to which the driving action applies. This value is the same as the |
|
|
The time of day to initiate the given driving action. If the route spans multiple days, the date and time of day are displayed. |
|
|
The type of maneuver that the directions feature represents or the type of the directions text. To determine whether
The Maneuver Types
Directions String Types
|
|
|
Specifies whether the
|
|
|
A text description of the travel directions. |
|
|
The time elapsed in minutes from when the current driving direction starts until the next one starts, or until the route ends for the last driving direction. |
|
|
The distance from where the current driving direction occurs to where the next one occurs, or to where the route ends for the last driving direction. The value is in the units specified by the This value is zero for driving directions that occur at the same location where the next one begins. For example, the |
output_direction_points
This is the output turn-by-turn directions for the routes calculated in the analysis, represented as point locations along the routes where specific direction events or maneuvers occur.
|
Field name |
Description |
|---|---|
|
|
The ObjectID of the output |
|
|
The sequence of the direction points for the route, starting with 1. |
|
|
Specifies the type of direction event or maneuver described by the point, designated by one of the values below.
|
|
|
The ObjectID of the stop with which this direction point is associated, if any. If the point does not represent a visit to a stop, the value is null. |
|
|
The directions text that will be displayed in the consuming application. |
|
|
The time the direction event occurs in coordinated universal time (UTC). |
|
|
The difference in minutes between the local time at the maneuver location and UTC time shown in the |
|
|
The name of the direction point. |
|
|
The highway exit name that appears in the directions instruction. |
|
|
The alternate source name that appears in the directions instruction. |
|
|
The name of the intersecting or cross street that appears in the directions instruction. |
|
|
The signpost branch name that appears in the directions instruction. |
|
|
The signpost toward destination name that appears in the directions instruction. |
|
|
The building level at which this direction event occurs. This value corresponds to the Learn more about the directions configuration of a network dataset |
|
|
The short text that will be used as voice guidance text in the consuming application. |
|
|
The additional text, including expanded abbreviations and plurals, that will be used as voice guidance text in the consuming application. |
|
|
The bearing in degrees of the vehicle departing this point. Zero indicates north. |
output_direction_lines
This is the output route lines calculated in the analysis sliced to represent each route segment between DirectionPoints events or maneuver locations.
|
Field name |
Description |
|---|---|
|
|
The ObjectID of the feature in the |
|
|
The ObjectID of the output |
|
|
Specifies the type of direction situation described by this line, designated by one of the following values:
|
|
|
The length of the line segment measured in meters. |
|
|
The travel time along the line segment in minutes. |
|
|
The building level at which this direction event begins. This value corresponds to the Learn more about the directions configuration of a network dataset |
|
|
The building level at which this direction event ends. This value corresponds to the |
output_stops
This provides access to the attributes of the stops that are visited by the routes as well as stops that cannot be reached by any of the routes.
You can use the attributes from this parameter, such as the Status field, to determine why a stop was not assigned to any routes.
The following table list the fields returned for output stops. In addition to these fields, the parameter also includes all the fields from the input feature class used as stops for the analysis.
|
Field |
Description |
|
|
The name of the stop visited by the route. The values for this field are copied from the |
|
|
The name of the route to which the stop is assigned. Input stops that have the same route name at the time the tool runs are grouped together and visited by one route, and the route is assigned that name. When more than one route name is present on the input stops, the tool can output multiple routes—one for each unique route name. If no name is provided, all the stops belong to the same route. |
|
|
The order in which the stops are visited by the assigned route, which is listed in the |
|
|
The earliest time the route can visit the stop. The values for this field are copied from the |
|
|
The latest time the route can visit the stop. The values for this field are copied from the |
|
|
The side of the vehicle the curb is on when arriving at the stop. |
|
|
The side of the vehicle the curb is on when departing from the stop. |
|
|
The date and time value indicating the arrival time at the stop. The time zone for this time-of-day value is taken from the network element on which the stop is located. |
|
|
The date and time value indicating the departure time from the stop. The time zone for this time-of-day value is taken from the network element on which the stop is located. |
|
|
The date and time value indicating the arrival time at the stop. The time zone for this time-of-day value is taken from the network element on which the stop is located. |
|
|
The date and time value indicating the departure time in coordinated universal time (UTC) |
|
|
The stop type. The values for this field are copied from the |
|
|
The numeric identifier of the network dataset source feature class on which the input point is located. |
|
|
The ObjectID of the feature in the source on which the input point is located. |
|
|
The position along the digitized direction of the source line feature. This value is stored as a ratio. This field is null if the network location references a junction. |
|
|
The side of the edge in relation to the digitized direction of the line feature. This field is limited to a domain of two values: Right Side (1) and Left Side (2). |
|
|
The direction a vehicle may arrive at and depart from the stop. The values for this field are copied from the |
|
|
Specifies the status of the point with respect to its location on the network and the outcome of the analysis. The possible values are the following:
|
|
|
The x-coordinate of the position on the network dataset where the point was located, in the coordinate system of the network dataset. |
|
|
The y-coordinate of the position on the network dataset where the point was located, in the coordinate system of the network dataset. |
|
|
The z-coordinate of the position on the network dataset where the point was located, in the coordinate system of the network dataset. The |
|
|
The distance in meters between the point's geographic location and the position where it was located on the network. |
|
|
The amount of time added to the total route time when this stop is visited. The values for this field are copied from the |
|
|
The amount of distance added to the total route distance when this stop is visited. The values for this field are copied from the |
|
|
The cost added to the total route cost when this stop is visited. The values for this field are copied from the |
|
|
The cumulative duration of the route in minutes from the origin to and including the stop. The value reported here is the cumulative route time to the stop, including any additional time at the stop and at any previous stops. For example, if a route analysis determines that it takes 10 minutes to visit two stops, and the second stop has an Note:An additional field, Note:Additional fields, |
|
|
The cumulative distance of the route in miles from the origin to and including the stop. The value reported here is the cumulative route distance to the stop, including any additional distance at the stop and at any previous stops. Note:An additional field, Note:Additional fields, |
|
|
The cumulative distance of the route in kilometers from the origin to and including the stop. The value reported here is the cumulative route distance to the stop, including any additional distance at the stop and at any previous stops. |
|
|
The cumulative cost of the route from the origin to and including the stop. The value reported here is the cumulative route cost to the stop, including any additional cost at the stop and at any previous stops. This field is included only when the travel mode used for the analysis has an impedance attribute that is neither time based nor distance based. The value is in unknown units. Note:Additional fields, |
|
|
This field stores the time spent waiting for the time window to open when the route arrives early at the stop. The field has a null value if time windows are not used in the analysis. Note:An additional field, Note:Additional fields, |
|
|
This field stores the sum of how much time has been spent waiting for time windows to open. It measures idle time. It includes the wait time from the current stop and all previous stops visited by the route. The field has a null value if time windows are not used in the analysis. Note:An additional field, Note:Additional fields, |
|
|
This field is a measure of how late the route arrived after the time window closed. Specifically, it stores the amount of time between the end of the time window and when the route arrived at the stop. The field has a null value if time windows are not used in the analysis. Note:An additional field, Additional fields |
|
|
This field stores the cumulative violation time from the current stop and all previous stops visited by the route. The field has a null value if time windows are not used in the analysis. Note:An additional field, Note:An additional field Additional fields |
|
|
The |
|
|
The values for this field are copied from the |
|
|
The values for this field are copied from the |
|
|
The values for this field are copied from the |
output_route_edges
This provides access to the individual network edges along which the routes travel.
This parameter has value only when the populate_route_edges parameter is set to True.
The following table lists the fields supported by the output route edges:
|
Field |
Description |
|---|---|
|
|
The name of the edge source feature class from which the line was generated. |
|
|
The |
|
|
The ID representing the edge that comprises the street feature. Since there can be more than one edge per street feature, the |
|
|
Specifies where the output
|
|
|
Specifies where the output
|
|
|
The |
|
|
The |
|
|
Uniquely identifies the route that traversed the edge. The |
|
|
The travel time in minutes of the traversed portion of the underlying street feature. Note:An additional field, |
|
|
The length in miles of the traversed portion of the underlying street feature. Note:An additional field, |
|
|
The length in kilometers of the traversed portion of the underlying street feature. |
|
|
The travel cost of the traversed portion of the underlying street feature. This field is included only when the travel mode used for the analysis has an impedance attribute that is neither time based nor distance based. The value is in unknown units. Note:Additional fields, |
|
|
The travel time in minutes of the route from its origin to the end of the traversed portion of this underlying street feature. Note:An additional field, Note:Additional fields, |
|
|
The length in miles of the route from its origin to the end of the traversed portion of this underlying street feature. Note:An additional field, Note:Additional fields, |
|
|
The length in kilometers of the route from its origin to the end of the traversed portion of this underlying street feature. |
|
|
The travel cost of the route from its origin to the end of the traversed portion of this underlying street feature. This field is included only when the travel mode used for the analysis has an impedance attribute that is neither time based nor distance based. The value is in unknown units. Note:Additional fields, |
|
|
Specifies whether the traversed edge used the soft restriction attribute referred to in this field's name.
For example, if the analysis was performed using the soft restriction called Avoid Toll Roads, a field called |
solve_succeeded
Use this parameter to determine if the analysis was successful.
output_result_file
Use this parameter to access the results from the analysis as a .zip file containing one or more files for each output. The format of the individual file is specified by the Output Format parameter. The parameter value is not populated when the Output Format parameter is set to Feature Set.
When a file-based output format—such as JSON File or GeoJSON File—is specified, no outputs are added to the display, since the application (such as ArcMap or ArcGIS Pro) does not draw the contents of the result file. Instead, the result file is downloaded to a temporary directory on your machine. In ArcGIS Pro, the location of the downloaded file can be determined by viewing the Output Result File parameter value in the entry corresponding to the tool operation in the geoprocessing history of the project. In ArcMap, the location of the file can be determined by accessing the Copy Location option in the shortcut menu of the Output Result File parameter in the entry corresponding to the tool operation in the Geoprocessing Results window.
output_route_data
Use this parameter to access a .zip file that contains a file geodatabase containing the inputs and outputs of the analysis in a format that can be used to share route layers with ArcGIS Online or Portal for ArcGIS. The parameter value is populated only when the Save Route Data parameter is set to True.
The file is downloaded to a temporary directory on your machine. In ArcGIS Pro, the location of the downloaded file can be determined by viewing the Output Route Data parameter value in the entry corresponding to the tool operation in the geoprocessing history of the project. In ArcMap, the location of the file can be determined by accessing the Copy Location option in the shortcut menu of the Output Route Data parameter in the entry corresponding to the tool operation in the Geoprocessing Results window.
output_network_analysis_layer
Use this parameter to access the network analysis layer file that stores the analysis settings and the inputs and outputs used for the analysis. The parameter value is populated only when the Save Output Network Analysis Layer parameter is set to True.
The file is downloaded to a temporary directory on your machine. In ArcGIS Pro, the location of the downloaded file can be determined by viewing the Output Network Analysis Layer parameter value in the entry corresponding to the tool operation in the geoprocessing history of the project. In ArcMap, the location of the file can be determined by accessing the Copy Location option in the shortcut menu of the Output Network Analysis Layer parameter in the entry corresponding to the tool operation in the Geoprocessing Results window.
Note:
You cannot work directly with this file even when you open the file in an ArcGIS Desktop application such as ArcMap since its data source will not be valid. The file is meant to be sent to Esri Technical Support to diagnose the quality of results returned from the tool.