Solve Route

The response format. The default response format is html.

Values: html | json

The set of stops loaded as network locations during analysis. Stops can be specified using a simple comma/semicolon-based syntax or as a JSON structure. If stops are not specified, preloaded stops from the map document are used in the analysis.

Syntax and Examples:

Simple syntax:

You can use a simple comma/semicolon-based syntax if you need to specify only stop point geometries in the default spatial reference or WGS84.

Syntax: stops=x1,y1; x2, y2; ...; xn, yn

Example: stops=-122.4079, 37.78356; -122.404, 37.782

JSON structures:

Using JSON structures, you can specify two types of stops:

• Features—Stop geometries and attributes expressed as a feature set.
• Layer—Stops referencing a data layer in the map service.

Features

You can specify stop geometries as well as attributes using a more comprehensive JSON structure.

The JSON structure can include the following properties:

• features—Optional. An array of features. Either the features or url property should be specified.
• This option was added at 10.1.

  url—Optional. REST Query request to a feature, map, or geoprocessing service returning a JSON feature set. Either the features or url property should be specified.

• type—Optional. The default type is features.
• doNotLocateOnRestrictedElements—Optional. If true, the features will only be located on streets that are traversable, not on roads that are restricted due to restriction attributes or barriers. Default is true.
• hasZ—Optional. Indicates if the features geometry contain z-values.

Each feature in this array represents a stop and it contains the following fields:

• geometry—Specifies the stop geometry. The structure for the geometry is the same as the structure of the standard ArcGIS REST API point geometry.
• attributes—Key-value pairs where the key is the name of the specified field, and the value is the value for the corresponding field.

Syntax 1: Using features:

{ 
"type" : "features",
"hasZ": <true|false>,
"features"  : [
{
  "geometry" : {<geometry1>},
  "attributes" : {"<field1>" : <value11>, "<field2>" : <value12>}
},
{
  "geometry" : {<geometry2>},
  "attributes" : {"<field1>" : <value21>, "<field2>" : <value22>}
}
],
"doNotLocateOnRestrictedElements" : true | false
}

Example:

{ 
"features"  : [
{
  "geometry" : {"x" : -122.4079, "y" : 37.78356},
  "attributes" : {"Name" : "From", "RouteName" : "Route A"}
},
{
  "geometry" : {"x" : -122.404, "y" : 37.782},
  "attributes" : {"Name" : "To", "RouteName" : "Route A"}
}
]
}

Syntax 2: Using url: (This option was added at 10.1.)

{ 
  "type" : "features",
  "url" : "<url>",
  "doNotLocateOnRestrictedElements" : true | false
}

Example:

{ 
  "type" : "features",
  "url" : "https://sampleserver3.arcgisonline.com/ArcGIS/rest/services/Network/USA/MapServer/1/query?where=1%3D1&outFields=Name,RouteName&f=json",
  "doNotLocateOnRestrictedElements" : true
}

Layer

You can specify stops by referencing a data layer in the map service. Attribute and spatial filters can also be applied on the layer.

The JSON structure can include the following properties:

• type—The type should be set to layer to indicate that the user is specifying the stops by referencing a layer.
• layerName—The name or ID of the data layer in the map service that is being referenced.
• where—Optional. A where clause for the query filter. Any legal SQL where clause operating on the fields in the layer is allowed.
• geometry—Optional. The geometry to apply as the spatial filter. The structure of the geometry is the same as the structure of the json geometry objects returned by the ArcGIS REST API.

  The geometry type is specified using the geometryType property.

• geometryType—Optional. The type of geometry specified by the geometry property. The geometry type can be envelope, point, line, or polygon. The default geometry type is envelope.

  Values: esriGeometryPoint | esriGeometryMultipoint | esriGeometryPolyline | esriGeometryPolygon | esriGeometryEnvelope

• spatialRel—Optional. The spatial relationship to be applied on the input geometry. The supported spatial relationships include intersects, contains, envelope intersects, within, and so on. The default spatial relationship is intersects (esriSpatialRelIntersects).

  Values: esriSpatialRelIntersects | esriSpatialRelContains | esriSpatialRelCrosses | esriSpatialRelEnvelopeIntersects | esriSpatialRelIndexIntersects | esriSpatialRelOverlaps | esriSpatialRelTouches | esriSpatialRelWithin

• doNotLocateOnRestrictedElements—Optional. If true, restricted network elements should be considered when finding network locations.

  Default is false.

Syntax:

{ 
  "type" : "layer",
  "layerName" : "<layerName>",
  "where" : "<whereClause>",
  "geometry" : {<geometry>},
  "geometryType" : "<geometryType>",
  "spatialRel" : "<spatialRel>",
  "doNotLocateOnRestrictedElements" : true | false
}

Example:

{ 
  "type" : "layer",
  "layerName" : "PointsOfInterest",
  "where" : "CITY = 'San Francisco'"
}

The set of barriers loaded as network locations during analysis. Barriers can be specified using a simple comma/semicolon-based syntax or as a JSON structure. If barriers are not specified, preloaded barriers from the map document are used in the analysis. If an empty JSON object is passed ('{}'), preloaded barriers are ignored.

Syntax and Examples:

Simple syntax:

You can use a simple comma/semicolon-based syntax if you need to specify only barrier point geometries in the default spatial reference or WGS84.

Syntax: barriers=x1,y1; x2, y2; ...; xn, yn

Example: barriers=-122.406, 37.7831; -122.405, 37.7827

JSON structures:

Using JSON structures, you can specify two types of barriers:

• Features—Barrier geometries and attributes expressed as a feature set.
• Layer—Barriers referencing a data layer in the map service.

Features

You can specify barrier geometries as well as attributes using a more comprehensive JSON structure.

The JSON structure can include the following properties:

• features—Optional. An array of features. Either the features or url property should be specified.
• url—Optional. REST Query request to a feature, map, or geoprocessing service returning a JSON feature set. Either the features or url property should be specified.
• type—Optional. The default type is features.
• hasZ—Optional. Indicates if the features geometry contain z-values.

Each feature in this array represents a barrier, and it contains the following fields:

• geometry—Specifies the barrier geometry. The structure for the geometry is the same as the structure of the standard ArcGIS REST API point geometry.
• attributes—Key-value pairs where the key is the name of the specified field, and the value is the value for the corresponding field.

Syntax 1: Using features:

{ 
"type" : "features",
"hasZ": <true|false>,
"features"  : [
{
  "geometry" : {<geometry1>},
  "attributes" : {"<field1>" : <value11>, "<field2>" : <value12>}
},
{
  "geometry" : {<geometry2>},
  "attributes" : {"<field1>" : <value21>, "<field2>" : <value22>}
}
]
}

Example:

{ 
"features"  : [
{
  "geometry" : {"x" : -122.406, "y" : 37.7831},
  "attributes" : {"Name" : "Barrier 1"}
},
{
  "geometry" : {"x" : -122.405, "y" : 37.7827},
  "attributes" : {"Name" : "Barrier 2"}
}
]
}

Syntax 2: Using url: (This option was added at 10.1.)

{ 
  "type" : "features",
  "url" : "<url>"
}

Example:

{ 
  "type" : "features",
  "url" : "https://sampleserver3.arcgisonline.com/ArcGIS/rest/services/Network/USA/MapServer/0/query?where=1%3D1&returnGeometry=true&f=json"
}

Layer

You can specify barriers by referencing a data layer in the map service. Attribute and spatial filters can also be applied on the layer.

The JSON structure can include the following properties:

• type—The type should be set to layer to indicate that the user is specifying the barriers by referencing a layer.
• layerName—The name or ID of the data layer in the map service that is being referenced.
• where—Optional. A where clause for the query filter. Any legal SQL where clause operating on the fields in the layer is allowed.
• geometry—Optional. The geometry to apply as the spatial filter. The structure of the geometry is the same as the structure of the json geometry objects returned by the ArcGIS REST API.

  The geometry type is specified using the geometryType property.

• geometryType—Optional. The type of geometry specified by the geometry property. The geometry type can be envelope, point, line, or polygon. The default geometry type is envelope.

  Values: esriGeometryPoint | esriGeometryMultipoint | esriGeometryPolyline | esriGeometryPolygon | esriGeometryEnvelope

• spatialRel—Optional. The spatial relationship to be applied on the input geometry. The supported spatial relationships include intersects, contains, envelope intersects, within, and so on. The default spatial relationship is intersects (esriSpatialRelIntersects).

  Values: esriSpatialRelIntersects | esriSpatialRelContains | esriSpatialRelCrosses | esriSpatialRelEnvelopeIntersects | esriSpatialRelIndexIntersects | esriSpatialRelOverlaps | esriSpatialRelTouches | esriSpatialRelWithin

Syntax:

{ 
  "type" : "layer",
  "layerName" : "<layerName>",
  "where" : "<whereClause>",
  "geometry" : {<geometry>},
  "geometryType" : "<geometryType>",
  "spatialRel" : "<spatialRel>"
}

Example:

{ 
  "type" : "layer",
  "layerName" : "TrafficAccidents",
  "where" : "SEVERITY > 0"
}

The set of polyline barriers loaded as network locations during analysis. If polyline barriers are not specified, preloaded polyline barriers from the map document are used in the analysis. If an empty JSON object is passed ('{}'), preloaded polyline barriers are ignored.

Syntax and Examples:

JSON structures:

Using JSON structures, you can specify two types of barriers:

• Features—Polyline barrier geometries and attributes expressed as a feature set.
• Layer—Polyline barriers referencing a data layer in the map service.

Features

You can specify polyline barrier geometries as well as attributes using a more comprehensive JSON structure.

The JSON structure can include the following properties:

• features—Optional. An array of features. Either the features or url property should be specified.
• url—Optional. REST Query request to a feature, map, or geoprocessing service returning a JSON feature set. Either the features or url property should be specified.
• type—Optional. The default type is features.
• hasZ—Optional. Indicates if the features geometry contain z-values.

Each feature in this array represents a barrier and it contains the following fields:

• geometry—Specifies the barrier geometry. The structure for the geometry is same as the structure of the standard ArcGIS REST API polyline geometry.
• attributes—Key-value pairs where the key is the name of the specified field, and the value is the value for the corresponding field.

Syntax 1: Using features:

{ 
"type" : "features",
"hasZ": <true|false>,
"features"  : [
{
  "geometry" : {<polyline1>},
  "attributes" : {"<field1>" : <value11>, "<field2>" : <value12>}
},
{
  "geometry" : {<polyline2>},
  "attributes" : {"<field1>" : <value21>, "<field2>" : <value22>}
}
]
}

Example:

{ 
"features"  : [
{
  "geometry" : {
     "paths" : [ 
     [ [-97.06138,32.837], [-97.06133,32.836], [-97.06124,32.834], [-97.06127,32.832] ], 
     [ [-97.06326,32.759], [-97.06298,32.755] ]
    ],
    "spatialReference" : {"wkid" : 4326}
    },
  "attributes" : {"Name" : "Barrier 1"}
},
{
  "geometry" : {
     "paths" : [ 
     [ [-97.06138,32.837], [-97.06133,32.836], [-97.06124,32.834], [-97.06127,32.832] ], 
     [ [-97.06326,32.759], [-97.06298,32.755] ]
    ],
    "spatialReference" : {"wkid" : 4326}
   },
  "attributes" : {"Name" : "Barrier 2"}
}
]
}

Syntax 2: Using url: (This option was added at 10.1.)

{ 
  "type" : "features",
  "url" : "<url>"
}

Example:

{ 
  "type" : "features",
  "url" : "https://sampleserver3.arcgisonline.com/ArcGIS/rest/services/Network/USA/MapServer/6/query?where=1%3D1&returnGeometry=true&f=json"
}

Layer

You can specify polyline barriers by referencing a data layer in the map service. Attribute and spatial filters can also be applied on the layer.

The JSON structure can include the following properties:

• type—The type should be set to layer to indicate that the user is specifying the polyline barriers by referencing a layer.
• layerName—The name of the data layer in the map service that is being referenced.
• where—Optional. A where clause for the query filter. Any legal SQL where clause operating on the fields in the layer is allowed.
• geometry—Optional. The geometry to apply as the spatial filter. The structure of the geometry is the same as the structure of the json geometry objects returned by the ArcGIS REST API.

  The geometry type is specified using the geometryType property.

• geometryType—Optional. The type of geometry specified by the geometry property. The geometry type can be envelope, point, line, or polygon. The default geometry type is envelope.

  Values: esriGeometryPoint | esriGeometryMultipoint | esriGeometryPolyline | esriGeometryPolygon | esriGeometryEnvelope

• spatialRel—Optional. The spatial relationship to be applied on the input geometry. The supported spatial relationships include intersects, contains, envelope intersects, within, and so on. The default spatial relationship is intersects (esriSpatialRelIntersects).

  Values: esriSpatialRelIntersects | esriSpatialRelContains | esriSpatialRelCrosses | esriSpatialRelEnvelopeIntersects | esriSpatialRelIndexIntersects | esriSpatialRelOverlaps | esriSpatialRelTouches | esriSpatialRelWithin

Syntax:

{ 
  "type" : "layer",
  "layerName" : "<layerName>",
  "where" : "<whereClause>",
  "geometry" : {<geometry>},
  "geometryType" : "<geometryType>",
  "spatialRel" : "<spatialRel>"
}

Example:

{ 
  "type" : "layer",
  "layerName" : "PolylineBarrier"
}

The set of polygon barriers loaded as network locations during analysis. If polygon barriers are not specified, preloaded polygon barriers from the map document are used in the analysis. If an empty JSON object is passed ('{}'), preloaded polygon barriers are ignored.

Syntax and Examples:

JSON structures:

Using JSON structures, you can specify two types of barriers:

• Features—Polygon barrier geometries and attributes expressed as a feature set.
• Layer—Polygon barriers referencing a data layer in the map service.

Features

You can specify polygon barrier geometries as well as attributes using a more comprehensive JSON structure.

The JSON structure can include the following properties:

• features—Optional. An array of features. Either the features or url property should be specified.
• url—Optional. REST Query request to a feature, map, geoprocessing service returning a JSON feature set. Either the features or url property should be specified.
• type—Optional. The default type is features.
• hasZ—Optional. Indicates if the features geometry contain z-values.

Each feature in this array represents a barrier and it contains the following fields:

• geometry—Specifies the barrier geometry. The structure for the geometry is the same as the structure of the standard ArcGIS REST API polygon geometry.
• attributes—Key-value pairs where the key is the name of the specified field, and the value is the value for the corresponding field.

Syntax:

{ 
"type" : "features",
"features"  : [
{
  "geometry" : {<polygon1>},
  "attributes" : {"<field1>" : <value11>, "<field2>" : <value12>}
},
{
  "geometry" : {<polygon3>},
  "attributes" : {"<field1>" : <value21>, "<field2>" : <value22>}
}
]
}

Example:

{ 
"features"  : [
{
  "geometry" : {
     "rings" : [ 
     [ [-97.06138,32.837], [-97.06133,32.836], [-97.06124,32.834], [-97.06127,32.832], [-97.06138,32.837] ], 
     [ [-97.06326,32.759], [-97.06298,32.755], [-97.06153,32.749], [-97.06326,32.759] ]
    ],
    "spatialReference" : {"wkid" : 4326}
    },
  "attributes" : {"Name" : "Barrier 1"}
},
{
  "geometry" : {
    "rings" : [ 
     [ [-97.06138,32.837], [-97.06133,32.836], [-97.06124,32.834], [-97.06127,32.832], [-97.06138,32.837] ], 
     [ [-97.06326,32.759], [-97.06298,32.755], [-97.06153,32.749], [-97.06326,32.759] ]
    ],
    "spatialReference" : {"wkid" : 4326}
    },
  "attributes" : {"Name" : "Barrier 2"}
}
]
}

Syntax 2: Using url: (This option was added at 10.1.)

{ 
  "type" : "features",
  "url" : "<url>"
}

Example:

{ 
  "type" : "features",
  "url" : "https://sampleserver3.arcgisonline.com/ArcGIS/rest/services/Network/USA/MapServer/7/query?where=1%3D1&returnGeometry=true&f=json"
}

Layer

You can specify polygon barriers by referencing a data layer in the map service. Attribute and spatial filters can also be applied on the layer.

The JSON structure can include the following properties:

• type—The type should be set to layer to indicate that the user is specifying the polygon barriers by referencing a layer.
• layerName—The name or ID of the data layer in the map service that is being referenced.
• where—Optional. A where clause for the query filter. Any legal SQL where clause operating on the fields in the layer is allowed.
• geometry—Optional. The geometry to apply as the spatial filter. The structure of the geometry is the same as the structure of the json geometry objects returned by the ArcGIS REST API.

  The geometry type is specified using the geometryType property.

• geometryType—Optional. The type of geometry specified by the geometry property. The geometry type can be envelope, point, line, or polygon. The default geometry type is envelope.

  Values: esriGeometryPoint | esriGeometryMultipoint | esriGeometryPolyline | esriGeometryPolygon | esriGeometryEnvelope

• spatialRel—Optional. The spatial relationship to be applied on the input geometry. The supported spatial relationships include intersects, contains, envelope intersects, within, and so on. The default spatial relationship is intersects (esriSpatialRelIntersects).

  Values: esriSpatialRelIntersects | esriSpatialRelContains | esriSpatialRelCrosses | esriSpatialRelEnvelopeIntersects | esriSpatialRelIndexIntersects | esriSpatialRelOverlaps | esriSpatialRelTouches | esriSpatialRelWithin

Syntax:

{ 
  "type" : "layer",
  "layerName" : "<layerName>",
  "where" : "<whereClause>",
  "geometry" : {<geometry>},
  "geometryType" : "<geometryType>",
  "spatialRel" : "<spatialRel>"
}

Example:

{ 
  "type" : "layer",
  "layerName" : "PolygonBarrier"
}

Added at 10.4.

Travel modes provide override values that help you quickly and consistently model a vehicle or mode of transportation. By setting a travel mode, you don't need to explicitly set values for the following parameters:

• impedanceAttributeName
• attributeParameterValues
• restrictUTurns
• useHierarchy
• restrictionAttributeNames
• outputGeometryPrecision
• outputGeometryPrecisionUnits

Caution:

When setting travelMode, the service overrides the values of the parameters listed above with those defined in the travel mode, even if you specify their values explicitly in the request.

Example:

To use an existing travel mode that was preconfigured in the service, the typical workflow would be as follows:

1. Find what travel modes have been preconfigured for the service by making a call to the retrieveTravelMode operation on the service. For example, http://<my server>:6080/arcgis/rest/services/<service name>/NAServer/Route/retrieveTravelModes?f=pjson

2. In the JSON that is returned, look up the supportedTravelModes name, whose value is an array containing the various travel modes.

   Example supportedTravelModes value.

   {
    "defaultTravelMode": "1",
    "supportedTravelModes": [
     {
      "name": "Driving Time",
      "id": "1",
      "type": "AUTOMOBILE",
      "description": "Finds the best route in a car minimizing time.",
      "timeAttributeName": "TravelTime",
      "distanceAttributeName": "Meters",
      "impedanceAttributeName": "TravelTime",
      "restrictionAttributeNames": [
       "Oneway",
       "Driving an Automobile"
      ],
      "attributeParameterValues": [
       {
        "attributeName": "Oneway",
        "parameterName": "Restriction Usage",
        "value": "Prohibited"
       },
       {
        "attributeName": "Driving an Automobile",
        "parameterName": "Restriction Usage",
        "value": "Prohibited"
       },
       {
        "attributeName": "Driving a Truck",
        "parameterName": "Restriction Usage",
        "value": "Prohibited"
       }
      ],
      "useHierarchy": true,
      "uturnAtJunctions": "esriNFSBAtDeadEndsAndIntersections",
      "simplificationTolerance": 10,
      "simplificationToleranceUnits": "esriMeters"
     },
     {
      "name": "Trucking Distance",
      "id": "2",
      "type": "TRUCK",
      "description": "Finds the best route in a truck minimizing distance.",
      "timeAttributeName": "Minutes",
      "distanceAttributeName": "Meters",
      "impedanceAttributeName": "Meters",
      "restrictionAttributeNames": [
       "Driving a Truck",
       "Oneway"
      ],
      "attributeParameterValues": [
       {
        "attributeName": "Oneway",
        "parameterName": "Restriction Usage",
        "value": "Prohibited"
       },
       {
        "attributeName": "Driving an Automobile",
        "parameterName": "Restriction Usage",
        "value": "Prohibited"
       },
       {
        "attributeName": "Driving a Truck",
        "parameterName": "Restriction Usage",
        "value": "Prohibited"
       }
      ],
      "useHierarchy": true,
      "uturnAtJunctions": "esriNFSBNoBacktrack",
      "simplificationTolerance": 10,
      "simplificationToleranceUnits": "esriMeters"
     }
    ] 
   }
   

3. The defaultTravelMode tag has the id of the travel mode that was configured to be used by default. So, in the above example, you would get the travel mode with "id" : "1" if you wanted the default travel mode.

4. Pass the JSON for the travel mode as the travelMode parameter value. In the case where you wanted to pass in the default travel mode, you would pass in the following:

   Example: travelMode parameter value.

   {
      "name": "Driving Time",
      "id": "1",
      "type": "AUTOMOBILE",
      "description": "Finds the best route in a car minimizing time.",
      "timeAttributeName": "TravelTime",
      "distanceAttributeName": "Meters",
      "impedanceAttributeName": "TravelTime",
      "restrictionAttributeNames": [
       "Oneway",
       "Driving an Automobile"
      ],
      "attributeParameterValues": [
       {
        "attributeName": "Oneway",
        "parameterName": "Restriction Usage",
        "value": "Prohibited"
       },
       {
        "attributeName": "Driving an Automobile",
        "parameterName": "Restriction Usage",
        "value": "Prohibited"
       },
       {
        "attributeName": "Driving a Truck",
        "parameterName": "Restriction Usage",
        "value": "Prohibited"
       }
      ],
      "useHierarchy": true,
      "uturnAtJunctions": "esriNFSBAtDeadEndsAndIntersections",
      "simplificationTolerance": 10,
      "simplificationToleranceUnits": "esriMeters"
     }
   

   Note:

   It is not required to pass in the same exact information as an existing travel mode. You can start from an existing travel mode and just change some of the settings prior to passing it in. Or, you can create your own travel mode JSON with whatever values you want as long as it conforms to the correct schema.

A set of attribute parameter values that can be parameterized to determine which network elements can be used by a vehicle.

The parameter holding a vehicle characteristic is compared to a value coming from a descriptor attribute to determine whether or not a network element is traversable. For example, a parameterized restriction attribute can compare the height of your vehicle with a descriptor attribute that holds the clearance under overpasses through tunnels. If the vehicles height is greater than the clearance, the edge is restricted.

Parameterized cost attributes that can reference other cost attributes and scale them can also be used. This is useful when inclement weather, such as ice, fog or heavy rain, descends on the study area and hinders normal flow of traffic. By having a parameter already outfitted on a cost attribute, travel-time expectations and traversable network paths can be adjusted with respect to changes in traffic speeds.

Syntax:

[ 
{
  "attributeName" : "<attribute1>",
  "parameterName" : "<parameter1>",
  "value" : "<value1>"
}, 
{
  "attributeName" : "<attribute2>",
  "parameterName" : "<parameter2>",
  "value" : "<value2>"
}
]

Example:

[
{ 
  "attributeName" : "Time",
  "parameterName" : "65 MPH",
  "value" : "5.0"
}
]

If true, directions will be generated and returned with the analysis results. Default is true.

The directions are available in the directions property of the JSON response.

Values: true | false

If true, routes will be returned with the analysis results. Default is true.

The routes are available in the routes property of the JSON response.

Values: true | false

If true, stops will be returned with the analysis results. Default is false.

The stops are available in the stops property of the JSON response.

Values: true | false

If true, barriers will be returned with the analysis results. Default is false.

The barriers are available in the barriers property of the JSON response.

Values: true | false

If true, polyline barriers will be returned with the analysis results. Default is false.

The polyline barriers are available in the polylineBarriers property of the JSON response.

Values: true | false

If true, polygon barriers will be returned with the analysis results. Default is false.

The polygon barriers are available in the polygonBarriers property of the JSON response.

Values: true | false

The spatial reference of the geometries returned with the analysis results.

The spatial reference can be specified as either a well-known ID or as a spatial reference json object.

If outSR is not specified, the geometries are returned in the spatial reference of the map.

If true, the solver will ignore invalid locations. Otherwise, it will raise an error. The default is as defined in the network layer.

Values: true | false

The type of output lines to be generated in the result. The default is as defined in the network layer.

Values: esriNAOutputLineNone | esriNAOutputLineStraight | esriNAOutputLineTrueShape | esriNAOutputLineTrueShapeWithMeasure

If true, the solver should re-sequence the route in the optimal order. The default is as defined in the network layer.

Values: true | false

If true, the solver should keep the first stop fixed in the sequence. The default is as defined in the network layer.

Values: true | false

If true, the solver should keep the last stop fixed in the sequence. The default is as defined in the network layer.

Values: true | false

If true, the solver should consider time windows. The default is as defined in the network layer.

Values: true | false

The time the route begins. If not specified, the solver will use the default as defined in the network layer.

The time should be specified as a numeric value representing the milliseconds since midnight January 1, 1970. It can be a negative number.

You can also specify a value of none to indicate that a start time should not be used.

Example: startTime=1227663551096 (Wed Nov 26 2008 01:39:11 UTC)

This option was added at 10.2.1.

The time zone of the startTime parameter.

By setting this parameter to false, which is the default value, the startTime parameter refers to the time zone in which the first stop is located. (Even though startTime is set as the number of milliseconds since midnight January 1, 1970 UTC to the target start time and date UTC, the UTC time zone is ignored and replaced with the time zone in which the first stop is located. For example, a time of 2:00 a.m. today UTC would become 2:00 a.m. today Eastern time if the first stop is located in the Eastern time zone.)

A true value for startTimeIsUTC indicates the startTime parameter refers to Coordinated Universal Time (UTC). Choose this option if you want to solve the analysis for a specific time, such as now, but aren't certain in which time zone the facilities or demand points will be located.

When solving a route analysis that spans across multiple time zones and setting a start time, preserveFirstStop must be true.

Values: true | false

The list of network attribute names to be accumulated with the analysis. The default is as defined in the network layer.

The value should be specified as a comma separated list of attribute names.

You can also specify a value of none to indicate that no network attributes should be accumulated.

Example: accumulateAttributeNames=WalkingMinutes,Meters

The network attribute name to be used as the impedance attribute in analysis. The default is as defined in the network layer.

Example: impedanceAttributeName=DrivingMinutes

The list of network attribute names to be used as restrictions with the analysis. The default is as defined in the network layer.

The value should be specified as a comma separated list of attribute names.

You can also specify a value of none to indicate that no network attributes should be used as restrictions.

Example: restrictionAttributeNames=Oneway

Specifies how U-Turns should be restricted in the analysis. The default is as defined in the network layer.

Values: esriNFSBAllowBacktrack | esriNFSBAtDeadEndsOnly | esriNFSBNoBacktrack | esriNFSBAtDeadEndsAndIntersections

If true, the hierarchy attribute for the network should be used in analysis. The default is as defined in the network layer.

Values: true | false

The language to be used when computing directions. The default is as defined in the network layer. The list of supported languages can be found in the REST layer description.

Example: directionsLanguage=en

Defines content, verbosity of returned directions. The default is esriDOTStandard.

Values: esriDOTComplete | esriDOTCompleteNoEvents | esriDOTFeatureSets | esriDOTInstructionsOnly | esriDOTStandard | esriDOTSummaryOnly

The style to be used when returning the directions. The default is as defined in the network layer. The list of supported styles can be found in the REST layer description.

Example: directionsStyleName=NA Navigation

The length units to use when computing directions. The default is as defined in the network layer.

Values: esriNAUFeet | esriNAUKilometers | esriNAUMeters | esriNAUMiles | esriNAUNauticalMiles | esriNAUYards | esriNAUUnknown

The name of the network attribute to use for the drive time when computing directions. The default is as defined in the network layer.

Example: directionsTimeAttributeName=DriveTime

The precision of the output geometry after generalization. If 0, no generalization of output geometry is performed. The default is as defined in the network service configuration. If present and positive, it represents the MaximumAllowableOffset parameter —generalization is performed according to IPolycurve.Generalize.

Example: outputGeometryPrecision=0.5

The units of the output geometry precision. The default value is esriUnknownUnits.

Values: esriUnknownUnits | esriCentimeters | esriDecimalDegrees | esriDecimeters | esriFeet | esriInches | esriKilometers | esriMeters | esriMiles | esriMillimeters | esriNauticalMiles | esriPoints | esriYards

This option was added at 10.1.

Description: If true, z-values will be included in the returned routes and compressed geometry if the network dataset is z-aware. The default is false.

Specifies additional settings that can influence the behavior of the solver when finding solutions for the network analysis problems.

The value for this parameter needs to be specified in JavaScript Object Notation (JSON). The values can be number, Boolean, or string.

{
"overrideSetting1" : "value1", 
"overrideSetting2" : "value2"
}

The default value for this parameter is no value, which indicates not to override any solver settings.

Overrides are advanced settings that should be used only after careful analysis of the results obtained before and after applying the settings. A list of supported override settings for each solver and their acceptable values can be obtained by contacting EsriTechnical Support.