| Name | Explanation | Data Type |
Stops |
Specifies the locations the output route or routes will visit. You can add up to
10,000 stops and assign up to 150 stops to a single route. (Assign stops to routes using the RouteName attribute.) When specifying the stops, you can set properties for each—such as its name or service time— using the following attributes: Name The name of the stop. The name is used in the driving
directions. If the name is not specified, a unique name prefixed
with Location is automatically generated in the output stops, routes, and
directions. RouteName The name of the route to which the stop is assigned. Assigning the same route name to different stops causes those stops to be grouped together and visited by the same route. You can generate many routes in a single solve by assigning unique route names to different groups of stops. You can group up to 150 stops into one route. Sequence The output routes will visit the stops in the order you specify with this attribute. In a group of stops that have the same RouteName value, the sequence number should be greater than 0 but not greater than the total number of stops. Also, the sequence number should not be duplicated. If Reorder Stops To Find Optimal Routes is checked (True), all but possibly the first and last sequence values for each route name are ignored so the tool can find the sequence that minimizes overall travel for each route. (The settings for Preserve Ordering of Stops and Return to Start determine whether the first or last sequence values for each route are ignored.) AdditionalTime The amount of time spent at the stop, which is added to the total time of the route. The default value is 0. The units for this attribute value are specified by the Measurement Units parameter. The attribute value is included in the analysis only when the measurement units are time based. You can account for the extra time it takes at the stop to complete a task, such as to repair an appliance, deliver a package, or inspect the premises. AdditionalDistance The extra distance traveled at the stops, which is added to the total distance of the route. The default value is 0. The units for this attribute value are specified by the Measurement Units parameter. The attribute value is included in the analysis only when the measurement units are distance based. Generally, the location of a stop, such as a home, isn't exactly on the street; it is set back somewhat from the road. This attribute value can be used to model the distance between the actual stop location and its location on the street if it is important to include that distance in the total travel distance. AdditionalCost The extra cost spent at the stop, which is added to the total cost of the route. The default value is 0. This attribute value should be used when the travel mode for the analysis uses an impedance attribute that is neither time based nor distance based. The units for the attribute values are interpreted to be in unknown units. TimeWindowStart The earliest time the stop can be visited. By specifying a start and end time for a stop's time window, you are defining when a route should visit the stop. When the travel mode for the analysis uses an impedance attribute that is time based, by specifying time-window values the analysis will find a solution that minimizes overall travel and reaches the stop within the prescribed time window. Make sure you specify the value as a date and time value, such as 8/12/2015 12:15 PM. When solving a problem that spans multiple time zones, time-window values refer to the time zone in which the stop is located. This field can contain a null value; a null value
indicates that a route can arrive at any time before the time indicated in the TimeWindowEnd attribute. If a null value is also present in TimeWindowEnd, a route can visit the stop at any time. TimeWindowEnd The latest time the stop can be visited. By specifying a start and end time for a stop's time window, you are defining when a route will visit the stop. When the travel mode for the analysis uses an impedance attribute that is time based, specifying time-window values will cause the analysis to find a solution that minimizes overall travel and reaches the stop within the prescribed time window. Make sure you specify the value as a date and time value, such as 8/12/2015 12:15 PM. When solving a problem that spans multiple time zones, time-window values refer to the time zone in which the stop is located. This field can contain a null value; a null value
indicates that a route can arrive at any time after the time indicated in the TimeWindowStart attribute. If a null value is also present in TimeWindowStart, a route can visit the stop at any time. CurbApproach Specifies the direction a vehicle may arrive at and depart
from the stop. The field value is specified as one of the
following integers (use the numeric code, not the name in parentheses): - 0 (Either side of vehicle)—The vehicle can approach and depart the stop in either direction, so a U-turn is allowed at the stop. This setting can be chosen if it is possible and practical for a vehicle to turn around at the stop. This decision may depend on the width of the road and the amount of traffic or whether the stop has a parking lot where vehicles can enter and turn around.
- 1 (Right side of vehicle)—When the vehicle approaches and departs the stop, the curb must be on the right side of the vehicle. A U-turn is prohibited. This is typically used for vehicles such as buses that must arrive with the bus stop on the right-hand side.
- 2 (Left side of vehicle)—When the vehicle approaches and departs
the stop, the curb must be on the left side of the vehicle. A
U-turn is prohibited. This is typically used for vehicles such as buses that must arrive with the bus stop on the left-hand side.
- 3 (No U-Turn)—When
the vehicle approaches the stop, the curb can be on either side
of the vehicle, however, the vehicle must depart without turning
around.
The CurbApproach attribute is designed to work with both kinds of national driving standards: right-hand traffic (United States) and left-hand traffic (United Kingdom). First, consider a stop on the left side of a vehicle. It is always on the left side regardless of whether the vehicle travels on the left or right half of the road. What may change with national driving standards is your decision to approach a stop from one of two directions, that is, so it ends up on the right or left side of the vehicle. For example, if you want to arrive at a stop and not have a lane of traffic between the vehicle and the stop, choose 1 (Right side of vehicle) in the United States and 2 (Left side of vehicle) in the United Kingdom. LocationType Specifies the stop type. The field value is specified as one of the following integers (use the numeric code, not the name in the parentheses): - 0 (Stop)—A location that the route will visit. This is the default.
- 1 (Waypoint)—A location that the route will travel through without making a stop. Waypoints can be used to force the route to take a specific path (to go through the waypoint) without being considered an actual stop. Waypoints do not appear in directions.
Bearing The direction in which a point is moving. The units are degrees and are measured clockwise from true north. This field is used in conjunction with the BearingTol field. Bearing data is usually sent automatically from a mobile device equipped with a GPS receiver. Try to include bearing data if you are loading an input location that is moving, such as a pedestrian or a vehicle. Using this field tends to prevent adding locations to the wrong edges, which can occur when a vehicle is near an intersection or an overpass, for example. Bearing also helps the tool determine on which side of the street the point is. Learn more about bearing and bearing tolerance BearingTol The bearing tolerance value creates a range of acceptable bearing values when locating moving points on an edge using the Bearing field. If the Bearing field value is within the range of acceptable values that are generated from the bearing tolerance on an edge, the point can be added as a network location there; otherwise, the closest point on the next-nearest edge is evaluated. The units are in degrees, and the default value is 30. Values must be greater than 0 and less than 180. A value of 30 means that when Network Analyst attempts to add a network location on an edge, a range of acceptable bearing values is generated 15 degrees to either side of the edge (left and right) and in both digitized directions of the edge. Learn more about bearing and bearing tolerance NavLatency This field is only used in the solve process if the Bearing and BearingTol fields also have values; however, entering a NavLatency field value is optional, even when values are present in Bearing and BearingTol. NavLatency indicates how much cost is expected to elapse from the moment GPS information is sent from a moving vehicle to a server and the moment the processed route is received by the vehicle's navigation device. The units of NavLatency are the same as the units of the impedance attribute. | Feature Set |
Measurement_Units | Specifies the units that will be used to measure and report the total travel time or travel distance for the output routes. The units you choose for this parameter determine whether the tool will measure distance or time to find the best routes. Choose a time unit to minimize travel time for your chosen travel mode (driving or walking time, for instance). To minimize travel distance for the given travel mode, choose a distance unit. Your choice also determines in which units the tool will report total time or distance in the results. - Meters —The linear unit is meters.
- Kilometers —The linear unit is kilometers.
- Feet —The linear unit is feet.
- Yards —The linear unit is yards.
- Miles —The linear unit is miles.
- NauticalMiles —The linear unit is nautical miles.
- Seconds —The time unit is seconds.
- Minutes —The time unit is minutes.
- Hours —The time unit is hours.
- Days —The time unit is days.
| String |
Analysis_Region (Optional) | The region in which the analysis will be performed. If a value is not specified for this parameter, the tool
will automatically calculate the region name based on the location
of the input points. Setting the name of the region is required only if the automatic detection of the region name is not accurate for your inputs. To specify a region, use one of
the following values:
- Europe —The analysis region is Europe.
- Japan —The analysis region is Japan.
- Korea —The analysis region is Korea.
- MiddleEastAndAfrica —The analysis region is Middle East and Africa.
- NorthAmerica —The analysis region is North America.
- SouthAmerica —The analysis region is South America.
- SouthAsia —The analysis region is South Asia.
- Thailand —The analysis region is Thailand.
Legacy:The following region names are no longer supported and will be removed in future releases. If you specify one of the deprecated region names, the tool automatically assigns a supported region name for your region. - Greece redirects to Europe
- India redirects to SouthAsia
- Oceania redirects to SouthAsia
- SouthEastAsia redirects to SouthAsia
- Taiwan redirects to SouthAsia
| String |
Reorder_Stops_to_Find_Optimal_Routes (Optional) | Specifies whether to visit the stops in the order you define or the order the tool determines will minimize overall travel. - Checked (True)—Stops will be visited in the order determined by the tool to minimize overall travel distance or time. It can reorder stops and account for time windows at stops. Additional parameters allow you to preserve the first or last stops while allowing the tool to reorder the intermediary stops.
- Unchecked (False)—Stops are visited in the order you define. You can set the order of stops using a Sequence attribute in the input stops features or let the sequence be determined by the Object ID of the stops. This is the default.
Finding the optimal stop order and the best routes is commonly known as solving the traveling salesperson problem (TSP). | Boolean |
Preserve_Terminal_Stops (Optional) | Specifies how terminal stops will be preserved. When Reorder Stops to Find Optimal Routes is checked (or True), you can preserve the starting or ending stops, and the tool can reorder the rest. The first and last stops are determined by their Sequence attribute values or, if the Sequence values are null, by their Object ID values. - Preserve First —The tool won't reorder the first stop. Choose this option if you are starting from a known location, such as your home, headquarters, or current location.
- Preserve Last —The tool won't reorder the last stop. The output routes may start from any stop feature but must end at the predetermined last stop.
- Preserve First and Last —The tool won't reorder the first and last stops.
- Preserve None —The tool may reorder any stop, including the first and last stops. The route may start or end at any of the stop features.
Preserve Terminal Stops is ignored when Reorder Stops to Find Optimal Routes is unchecked (or False). | String |
Return_to_Start (Optional) | Specifies whether routes will start and end at the same location. With this option, you can avoid duplicating the first stop feature and sequencing the duplicate stop at the end. The starting location of the route is the stop feature with the lowest value in the Sequence attribute. If the Sequence values are null, it is the stop feature with the lowest Object ID value. - Checked (True)—The route will start and end at the first stop feature. When Reorder Stops to Find Optimal Routes and Return to Start are both checked (or True), Preserve Terminal Stops must be set to Preserve First. This is the default value.
- Unchecked (False)—The route won't start and end at the first stop feature.
| Boolean |
Use_Time_Windows (Optional) |
Specifies whether time windows will be honored. Check this option (or set it to True) if any input stops have time windows that specify when the route will reach the stop. You can add time windows to input stops by entering time values in the TimeWindowStart and TimeWindowEnd attributes. - Checked (True)—The input stops have time windows, and you want the tool to try to honor them.
- Unchecked (False)—The input stops don't have time windows, or if they do, you don't want the tool to try to honor them. This is the default value.
The tool will take slightly longer to run when Use Time Windows is checked (or True), even when none of the input stops have time windows, so it is recommended that you uncheck this option (set to False) if possible. | Boolean |
Time_of_Day (Optional) | The time and date the routes will
begin. If you are modeling the driving travel mode and specify the current date and time as the value
for this parameter, the tool will use live traffic conditions to
find the best routes, and the total travel time will be based
on traffic conditions. Specifying a time of day results in more accurate
routes and estimations of travel times because the
travel times account for the traffic conditions that are applicable
for that date and time. The Time Zone for Time of Day parameter specifies whether this time and date refer to UTC or the time zone in which the stop is located. The tool ignores this parameter when Measurement Units isn't set to a time-based unit. | Date |
Time_Zone_for_Time_of_Day (Optional) | Specifies the time zone of the Time of Day parameter.
- Geographically Local —The Time of Day parameter refers to the time zone in which the first stop of a route is located. If you are generating many routes that start in multiple time zones, the start times are staggered in coordinated universal time (UTC). For example, a Time of Day value of 10:00 a.m., 2 January, means a start time of 10:00 a.m. eastern standard time (UTC-3:00) for routes beginning in the eastern time zone and 10:00 a.m. central standard time (UTC-4:00) for routes beginning in the central time zone. The start times are offset by one hour in UTC. The arrive and depart times and dates recorded in the output Stops feature class will refer to the local time zone of the first stop for each route.
- UTC —The Time of Day parameter refers to UTC. Choose this option if you want to generate a route for a specific time, such as now, but aren't certain in which time zone the first stop will be located. If you are generating many routes spanning multiple time zones, the start times in UTC are simultaneous. For example, a Time of Day value of 10:00 a.m., 2 January, means a start time of 5:00 a.m. eastern standard time (UTC-5:00) for routes beginning in the eastern time zone and 4:00 a.m. central standard time (UTC-6:00) for routes beginning in the central time zone. Both routes start at 10:00 a.m. UTC. The arrive and depart times and dates recorded in the output Stops feature class will refer to UTC.
| String |
UTurn_at_Junctions (Optional) | Specifies the U-turn policy at junctions. Allowing U-turns implies the solver can turn around at a junction and double back on the same street.
Given that junctions represent street intersections and dead ends, different vehicles may be able to turn around at some junctions but not at others—it depends on whether the junction represents an intersection or dead end. To accommodate this, the U-turn policy parameter is implicitly specified by the number of edges that connect to the junction, which is known as junction valency. The acceptable values for this parameter are listed below; each is followed by a description of its meaning in terms of junction valency.
- Allowed —U-turns are permitted at junctions with any number of connected edges. This is the default value.
- Not Allowed —U-turns are prohibited at all junctions, regardless of junction valency. Note, however, that U-turns are still permitted at network locations even when this option is chosen; however, you can set the individual network locations' CurbApproach attribute to prohibit U-turns there as well.
- Allowed Only at Dead Ends —U-turns are prohibited at all junctions except those that have only one adjacent edge (a dead end).
- Allowed Only at Intersections and Dead Ends —U-turns are prohibited at junctions where exactly two adjacent edges meet but are permitted at intersections (junctions with three or more adjacent edges) and dead ends (junctions with exactly one adjacent edge). Often, networks have extraneous junctions in the middle of road segments. This option prevents vehicles from making U-turns at these locations.
This parameter is ignored unless Travel Mode is set to Custom. | String |
Point_Barriers (Optional) |
Use this parameter to specify one or more points that will act as temporary
restrictions or represent additional time or distance that may be
required to travel on the underlying streets. For example, a point
barrier can be used to represent a fallen tree along a street or
a time delay spent at a railroad crossing. The tool imposes a limit of 250 points that can be added
as barriers. When specifying point barriers, you can set properties for each, such as its name or barrier type, using the following attributes: Name The name of the barrier. BarrierType Specifies whether the point barrier restricts travel
completely or adds time or distance when it is crossed. The value
for this attribute is specified as one of the following
integers (use the numeric code, not the name in parentheses): -
0 (Restriction)—Prohibits travel through the barrier. The barrier
is referred to as a restriction point barrier since it acts as a
restriction.
2 (Added Cost)—Traveling through the barrier increases the travel
time or distance by the amount specified in the
Additional_Time, Additional_Distance, or Additional_Cost field. This barrier type is
referred to as an added cost point barrier.
Additional_Time The added travel time when the
barrier is traversed. This field is applicable only for added-cost
barriers and when the Measurement Units parameter value is time based. This field
value must be greater than or equal to zero, and its units must be the same as those specified in the
Measurement Units parameter. Additional_Distance The added distance when the
barrier is traversed. This field is applicable only for added-cost
barriers and when the Measurement Units parameter value is distance based. The field value
must be greater than or equal to zero, and its units must be the same as those specified in the
Measurement Units parameter. Additional_Cost The added cost when the
barrier is traversed. This field is applicable only for added-cost
barriers when the Measurement Units parameter value is neither time based nor distance based. FullEdge Specifies how the restriction point barriers are applied to the edge elements during the analysis. The field value is specified as one of the following integers (use the numeric code, not the name in parentheses): - 0 (False)—Permits travel on the edge up to the barrier but not through it. This is the default value.
- 1 (True)—Restricts travel anywhere on the associated edge.
CurbApproach Specifies the direction of traffic that is affected by the barrier. The field value is specified as one of the following integers (use the numeric code, not the name in parentheses): - 0 (Either side of vehicle)—The barrier affects travel over the edge in both directions.
- 1 (Right side of vehicle)—Vehicles are only affected if the barrier is on their right side during the approach. Vehicles that traverse the same edge but approach the barrier on their left side are not affected by the barrier.
- 2 (Left side of vehicle)—Vehicles are only affected if the barrier is on their left side during the approach. Vehicles that traverse the same edge but approach the barrier on their right side are not affected by the barrier.
Because junctions are points and don't have a side, barriers on junctions affect all vehicles regardless of the curb approach. The CurbApproach attribute works with both types of national driving standards: right-hand traffic (United States) and left-hand traffic (United Kingdom). First, consider a facility on the left side of a vehicle. It is always on the left side regardless of whether the vehicle travels on the left or right half of the road. What may change with national driving standards is your decision to approach a facility from one of two directions, that is, so it ends up on the right or left side of the vehicle. For example, to arrive at a facility and not have a lane of traffic between the vehicle and the facility, choose 1 (Right side of vehicle) in the United States and 2 (Left side of vehicle) in the United Kingdom. Bearing The direction in which a point is moving. The units are degrees and are measured clockwise from true north. This field is used in conjunction with the BearingTol field. Bearing data is usually sent automatically from a mobile device equipped with a GPS receiver. Try to include bearing data if you are loading an input location that is moving, such as a pedestrian or a vehicle. Using this field tends to prevent adding locations to the wrong edges, which can occur when a vehicle is near an intersection or an overpass, for example. Bearing also helps the tool determine on which side of the street the point is. Learn more about bearing and bearing tolerance BearingTol The bearing tolerance value creates a range of acceptable bearing values when locating moving points on an edge using the Bearing field. If the Bearing field value is within the range of acceptable values that are generated from the bearing tolerance on an edge, the point can be added as a network location there; otherwise, the closest point on the next-nearest edge is evaluated. The units are in degrees, and the default value is 30. Values must be greater than 0 and less than 180. A value of 30 means that when Network Analyst attempts to add a network location on an edge, a range of acceptable bearing values is generated 15 degrees to either side of the edge (left and right) and in both digitized directions of the edge. Learn more about bearing and bearing tolerance NavLatency This field is only used in the solve process if the Bearing and BearingTol fields also have values; however, entering a NavLatency field value is optional, even when values are present in Bearing and BearingTol. NavLatency indicates how much cost is expected to elapse from the moment GPS information is sent from a moving vehicle to a server and the moment the processed route is received by the vehicle's navigation device. The units of NavLatency are the same as the units of the impedance attribute. | Feature Set |
Line_Barriers (Optional) |
Use this parameter to specify one or more lines that prohibit travel anywhere
the lines intersect the streets. For example, a parade or protest
that blocks traffic across several street segments can be modeled
with a line barrier. A line barrier can also quickly fence off
several roads from being traversed, thereby channeling possible
routes away from undesirable parts of the street
network. The tool imposes a limit on the number of streets you can
restrict using the Line Barriers parameter. While there is no limit to
the number of lines you can specify as line barriers, the combined
number of streets intersected by all the lines cannot exceed
500. When specifying the line barriers, you can set name and barrier type properties for each using the following attributes: Name The name of the barrier. | Feature Set |
Polygon_Barriers (Optional) |
Use this parameter to specify polygons that either completely restrict travel or
proportionately scale the time or distance required to travel on
the streets intersected by the polygons. The service imposes a limit on the number of streets you
can restrict using the Polygon Barriers parameter. While there is
no limit to the number of polygons you can specify as polygon
barriers, the combined number of streets intersected by all the
polygons cannot exceed 2,000. When specifying the polygon barriers, you can set properties for each, such as its name or barrier type, using the following attributes: Name The name of the barrier. BarrierType Specifies whether the barrier restricts travel completely
or scales the cost (such as time or distance) for traveling through it. The field
value is specified as one of the following integers (use the numeric code, not the name in parentheses): 0 (Restriction)—Prohibits traveling through any part of the barrier.
The barrier is referred to as a restriction polygon barrier since it
prohibits traveling on streets intersected by the barrier. One use
of this type of barrier is to model floods covering areas of the
street that make traveling on those streets impossible. -
1 (Scaled Cost)—Scales the cost (such as travel time or distance) required to travel the
underlying streets by a factor specified using the ScaledTimeFactor or ScaledDistanceFactor field. If the streets are partially
covered by the barrier, the travel time or distance is apportioned
and then scaled. For example, a factor of 0.25 means that travel
on underlying streets is expected to be four times faster than
normal. A factor of 3.0 means it is expected to take three
times longer than normal to travel on underlying streets. This
barrier type is referred to as a scaled-cost polygon barrier. It
can be used to model storms that reduce travel speeds in specific
regions.
ScaledTimeFactor This is the factor by which the travel time of the streets
intersected by the barrier is multiplied. The field value must be greater than zero. This field is applicable only for scaled-cost
barriers and when the Measurement Units parameter is time-based. ScaledDistanceFactor This is the factor by which the distance of the streets
intersected by the barrier is multiplied. The field value must be greater than zero. This field is applicable only for scaled-cost
barriers and when the Measurement Units parameter is distance-based. ScaledCostFactor This is the factor by which the cost of the streets
intersected by the barrier is multiplied. The field value must be greater than zero. This field is applicable only for scaled-cost
barriers when the Measurement Units parameter is neither time-based nor distance-based. | Feature Set |
Use_Hierarchy (Optional) | Specifies whether hierarchy will be used when finding the shortest paths between stops. - Checked (True in Python)—Hierarchy will be used when finding routes. When
hierarchy is used, the tool identifies higher-order streets (such as
freeways) before lower-order streets (such as local roads) and can be used
to simulate the driver preference of traveling on freeways instead
of local roads even if that means a longer trip. This is especially
useful when finding routes to faraway locations, because drivers on long-distance trips tend to prefer traveling on freeways, where stops, intersections, and turns can be avoided. Using hierarchy is computationally faster,
especially for long-distance routes, as the tool identifies the
best route from a relatively smaller subset of streets.
- Unchecked (False in Python)—Hierarchy will not be used when finding routes. If
hierarchy is not used, the tool considers all the streets and doesn't
necessarily identify higher-order streets when finding the route. This is often
used when finding short routes within a city.
The tool automatically reverts to using hierarchy if the
straight-line distance between facilities and demand points is
greater than 50 miles (80.46
kilometers), even if this parameter is unchecked (set to False in Python). This parameter is ignored unless Travel Mode is set to Custom. When modeling a custom walking mode, it is recommended that you turn off hierarchy since hierarchy is designed for motorized vehicles. | Boolean |
Restrictions [Restrictions,...] (Optional) | The restrictions that will be honored by the tool when finding the best routes. A restriction represents a driving
preference or requirement. In most cases, restrictions cause roads
to be prohibited. For instance, using the Avoid Toll Roads restriction will result in a route that will include toll roads only when it is required to travel on toll roads to visit an incident or a facility. Height Restriction makes it possible to route around any clearances that are lower than the height of your vehicle. If you are carrying corrosive materials on your vehicle, using the Any Hazmat Prohibited restriction prevents hauling the materials along roads where it is marked illegal to do so. The values you provide for this parameter are ignored unless Travel Mode is set to Custom. Some restrictions require an additional value to be
specified for their use. This value must be associated
with the restriction name and a specific parameter intended to work
with the restriction. You can identify such restrictions if their
names appear in the AttributeName column in the Attribute
Parameter Values parameter. The ParameterValue field should be
specified in the Attribute Parameter Values parameter for the
restriction to be correctly used when finding traversable roads. Some restrictions are supported only in certain countries; their availability is stated by region in the list below. Of the restrictions that have limited availability within a region, you can determine whether the restriction is available in a particular country by reviewing the table in the Country list section of Network analysis coverage. If a country has a value of Yes in the Logistics Attribute column, the restriction with select availability in the region is supported in that country. If you specify restriction names that are not available in the country where your incidents are located, the service ignores the invalid restrictions. The service also ignores restrictions when the Restriction Usage attribute parameter value is between 0 and 1 (see the Attribute Parameter Value parameter). It prohibits all restrictions when the Restriction Usage parameter value is greater than 0. The tool supports the following restrictions: - Any Hazmat Prohibited —The results will not include roads
where transporting any kind of hazardous material is
prohibited. Availability: Select countries in North America and Europe
- Avoid Carpool Roads —The results will avoid roads that are
designated exclusively for car pool (high-occupancy)
vehicles. Availability: All countries
- Avoid Express Lanes —The results will avoid roads designated
as express lanes. Availability: All countries
- Avoid Ferries —The results will avoid ferries. Availability: All countries
- Avoid Gates —The results will avoid roads where there are
gates, such as keyed access or guard-controlled
entryways.Availability: All countries
- Avoid Limited Access Roads —The results will avoid roads
that are limited-access highways.Availability: All countries
- Avoid Private Roads —The results will avoid roads that are
not publicly owned and maintained.Availability: All countries
- Avoid Roads Unsuitable for Pedestrians —The results will avoid roads that are
unsuitable for pedestrians.Availability: All countries
- Avoid Stairways —The results will avoid all stairways on a pedestrian-suitable route.Availability: All countries
- Avoid Toll Roads —The results will avoid all toll
roads for automobiles.Availability: All countries
- Avoid Toll Roads for Trucks —The results will avoid all toll
roads for trucks.Availability: All countries
- Avoid Truck Restricted Roads —The results will avoid roads where trucks are not allowed, except when making deliveries.Availability: All countries
- Avoid Unpaved Roads —The results will avoid roads that are
not paved (for example, dirt, gravel, and so on). Availability: All countries
- Axle Count Restriction —The results will not include roads
where trucks with the specified number of axles are prohibited. The
number of axles can be specified using the Number of Axles
restriction parameter.Availability: Select countries in North America and Europe
- Driving a Bus —The results will not include roads where
buses are prohibited. Using this restriction will also ensure that
the results will honor one-way streets. Availability: All countries
- Driving a Taxi —The results will not include roads where
taxis are prohibited. Using this restriction will also ensure that
the results will honor one-way streets. Availability: All countries
- Driving a Truck —The results will not include roads where
trucks are prohibited. Using this restriction will also ensure that
the results will honor one-way streets. Availability: All countries
- Driving an Automobile —The results will not include roads
where automobiles are prohibited. Using this restriction will also
ensure that the results will honor one-way streets. Availability: All countries
- Driving an Emergency Vehicle —The results will not include
roads where emergency vehicles are prohibited. Using this
restriction will also ensure that the results will honor one-way
streets.Availability: All countries
- Height Restriction —The results will not include roads
where the vehicle height exceeds the maximum allowed height for the
road. The vehicle height can be specified using the Vehicle Height
(meters) restriction parameter. Availability: Select countries in North America and Europe
- Kingpin to Rear Axle Length Restriction —The results will
not include roads where the vehicle length exceeds the maximum
allowed kingpin to rear axle for all trucks on the road. The length
between the vehicle kingpin and the rear axle can be specified
using the Vehicle Kingpin to Rear Axle Length (meters) restriction
parameter. Availability: Select countries in North America and Europe
- Length Restriction —The results will not include roads
where the vehicle length exceeds the maximum allowed length for the
road. The vehicle length can be specified using the Vehicle Length
(meters) restriction parameter. Availability: Select countries in North America and Europe
- Preferred for Pedestrians —The results will use preferred routes suitable for pedestrian navigation. Availability: Select countries in North America and Europe
- Riding a Motorcycle —The results will not include roads
where motorcycles are prohibited. Using this restriction will also
ensure that the results will honor one-way streets.Availability: All countries
- Roads Under Construction Prohibited —The results will not
include roads that are under construction.Availability: All countries
- Semi or Tractor with One or More Trailers Prohibited —The
results will not include roads where semis or tractors with one or
more trailers are prohibited. Availability: Select countries in North America and Europe
- Single Axle Vehicles Prohibited —The results will not
include roads where vehicles with single axles are
prohibited.Availability: Select countries in North America and Europe
- Tandem Axle Vehicles Prohibited —The results will not
include roads where vehicles with tandem axles are
prohibited.Availability: Select countries in North America and Europe
- Through Traffic Prohibited —The results will not include
roads where through traffic (nonlocal) is prohibited.Availability: All countries
- Truck with Trailers Restriction —The results will not
include roads where trucks with the specified number of trailers on
the truck are prohibited. The number of trailers on the truck can
be specified using the Number of Trailers on Truck restriction
parameter.Availability: Select countries in North America and Europe
- Use Preferred Hazmat Routes —The results will prefer roads
that are designated for transporting any kind of hazardous
materials. Availability: Select countries in North America and Europe
- Use Preferred Truck Routes —The results will prefer roads
that are designated as truck routes, such as the roads that are
part of the national network as specified by the National Surface
Transportation Assistance Act in the United States, or roads that
are designated as truck routes by the state or province, or roads
that are preferred by truckers when driving in an
area.Availability: Select countries in North America and Europe
- Walking —The results will not include roads where
pedestrians are prohibited.Availability: All countries
- Weight Restriction —The results will not include roads
where the vehicle weight exceeds the maximum allowed weight for the
road. The vehicle weight can be specified using the Vehicle Weight
(kilograms) restriction parameter.Availability: Select countries in North America and Europe
- Weight per Axle Restriction —The results will not include
roads where the vehicle weight per axle exceeds the maximum allowed
weight per axle for the road. The vehicle weight per axle can be
specified using the Vehicle Weight per Axle (kilograms) restriction
parameter.Availability: Select countries in North America and Europe
- Width Restriction —The results will not include roads where
the vehicle width exceeds the maximum allowed width for the road.
The vehicle width can be specified using the Vehicle Width (meters)
restriction parameter.Availability: Select countries in North America and Europe
| String |
Attribute_Parameter_Values (Optional) | Use this parameter to specify additional values required by an attribute or restriction, such as to specify whether the restriction prohibits, avoids, or prefers travel on restricted roads. If the restriction is
meant to avoid or prefer roads, you can further specify the degree
to which they are avoided or preferred using this
parameter. For example, you can choose to never use toll roads, avoid them as much as possible, or prefer them. The values you provide for this parameter are ignored unless Travel Mode is set to Custom. If you specify the Attribute Parameter Values parameter from a
feature class, the field names on the feature class must match the fields as follows: - AttributeName—The name of the restriction.
- ParameterName—The name of the parameter associated with the
restriction. A restriction can have one or more ParameterName field
values based on its intended use.
- ParameterValue—The value for ParameterName used by the tool
when evaluating the restriction.
The Attribute Parameter Values parameter is dependent on the
Restrictions parameter. The ParameterValue field is applicable only
if the restriction name is specified as the value for the
Restrictions parameter. In Attribute Parameter Values, each
restriction (listed as AttributeName) has a ParameterName field
value, Restriction Usage, that specifies whether the restriction
prohibits, avoids, or prefers travel on the roads associated with
the restriction as well as the degree to which the roads are avoided or
preferred. The Restriction Usage ParameterName can be assigned any of
the following string values or their equivalent numeric values
listed in the parentheses: - PROHIBITED (-1)—Travel on the roads using the restriction is completely
prohibited.
- AVOID_HIGH (5)—It
is highly unlikely the tool will include in the route the roads
that are associated with the restriction.
- AVOID_MEDIUM (2)—It
is unlikely the tool will include in the route the roads that are
associated with the restriction.
- AVOID_LOW (1.3)—It
is somewhat unlikely the tool will include in the route the roads
that are associated with the restriction.
- PREFER_LOW (0.8)—It
is somewhat likely the tool will include in the route the roads
that are associated with the restriction.
- PREFER_MEDIUM (0.5)—It is likely the tool will include in the route the roads that
are associated with the restriction.
- PREFER_HIGH (0.2)—It is highly likely the tool will include in the route the roads
that are associated with the restriction.
In most cases, you can use the default value, PROHIBITED,
as the Restriction Usage value if the restriction is dependent on a
vehicle characteristic such as vehicle height. However, in some
cases, the Restriction Usage value depends on your routing
preferences. For example, the Avoid Toll Roads restriction has the
default value of AVOID_MEDIUM for the Restriction Usage attribute.
This means that when the restriction is used, the tool will try to
route around toll roads when it can. AVOID_MEDIUM also indicates
how important it is to avoid toll roads when finding the best
route; it has a medium priority. Choosing AVOID_LOW puts lower
importance on avoiding tolls; choosing AVOID_HIGH instead gives it a higher importance and thus makes it more acceptable for
the service to generate longer routes to avoid tolls. Choosing
PROHIBITED entirely disallows travel on toll roads, making it
impossible for a route to travel on any portion of a toll road.
Keep in mind that avoiding or prohibiting toll roads, and thus
avoiding toll payments, is the objective for some. In contrast,
others prefer to drive on toll roads, because avoiding traffic is
more valuable to them than the money spent on tolls. In the latter
case, choose PREFER_LOW, PREFER_MEDIUM, or PREFER_HIGH as
the value for Restriction Usage. The higher the preference, the
farther the tool will go out of its way to travel on the roads
associated with the restriction. | Record Set |
Route_Shape (Optional) | Specifies the type of route features that are output by the
tool. - True Shape —Return the exact shape of the resulting route
that is based on the underlying streets.
- True Shape with Measures —Return the exact shape of the resulting route that is based on the underlying streets. Additionally, construct measures so the shape can be used in linear referencing. The measurements increase from the first stop and record the cumulative travel time or travel distance in the units specified by the Measurement Units parameter.
- Straight Line —Return a straight line between two stops.
- None —Do not return any shapes for the routes. This value
can be useful, and return results quickly, in cases where you are only interested in determining
the total travel time or travel distance of a route.
When the Route Shape parameter is set to True Shape or True Shape with Measures, the
generalization of the route shape can be further controlled using
the appropriate value for the Route Line Simplification Tolerance parameter. No matter which value you choose for the Route Shape
parameter, the best route is always determined by minimizing the
travel time or the travel distance, never using the straight-line
distance between stops. This means that only the route shapes are different,
not the underlying streets that are searched when finding the
route.
| String |
Route_Line_Simplification_Tolerance (Optional) | Specify by how much you want to simplify the geometry of the output lines for routes, directions, and route edges. The tool ignores this parameter if the Route Shape parameter isn't set to True Shape. Simplification maintains critical
points on a route, such as turns at intersections, to define the
essential shape of the route and removes other points. The
simplification distance you specify is the maximum allowable offset
that the simplified line can deviate from the original line.
Simplifying a line reduces the number of vertices that are part of
the route geometry. This improves the tool execution
time. | Linear Unit |
Populate_Route_Edges (Optional) | Specifies whether the tool will generate edges for each route. Route edges represent the individual street features or other similar features that are traversed by a route. The output Route Edges layer is commonly used to see which streets or paths are traveled on the most or least by the resultant routes. - Checked (True)—Route edges will be generated. The output Route Edges layer is populated with line features.
- Unchecked (False)—Route edges will not be generated. The output Route Edges layer is returned, but it is empty.
| Boolean |
Populate_Directions (Optional) | Specifies whether the tool will generate driving directions for
each route. - Checked (True in Python)—Directions will be generated
and configured based on the values of the Directions Language,
Directions Style Name, and Directions Distance Units parameters.
- Unchecked (False in Python)—Directions will not be generated, and the tool
will return an empty Directions layer.
| Boolean |
Directions_Language (Optional) | The language that will be used when generating
travel directions. This parameter is used only when the Populate
Directions parameter is checked (True in Python). The parameter value can be
specified using one of the following two- or five-character language codes: - ar—Arabic
- bs—Bosnian
- ca—Catalan
- cs—Czech
- da—Danish
- de—German
- el—Greek
- en—English
- es—Spanish
- et—Estonian
- fi—Finnish
- fr—French
- he—Hebrew
- hr—Croatian
- hu—Hungarian
- id—Indonesian
- it—Italian
- ja—Japanese
- ko—Korean
- lt—Lithuanian
- lv—Latvian
- nb—Norwegian
- nl—Dutch
- pl—Polish
- pt-BR—Brazilian
Portuguese
- pt-PT—European
Portuguese
- ro—Romanian
- ru—Russian
- sl—Slovenian
- sr—Serbian
- sv—Swedish
- th—Thai
- tr—Turkish
- uk—Ukrainian
- vi—Vietnamese
- zh-CN—Simplified
Chinese
- zh-HK—Traditional Chinese (Hong Kong)
- zh-TW—Traditional Chinese (Taiwan)
The tool first searches for an exact match for the specified language including any language localization. If an exact match is not found, it tries to match the language family. If a match is still not found, the tool returns the directions using the default language, English. For example, if the directions language is specified as es-MX (Mexican Spanish), the tool will return the directions in Spanish, as it supports the es language code but not es-MX. Caution:If a language supports localization, such as Brazilian Portuguese (pt-BR) and European Portuguese (pt-PT), specify the language family and the localization. If you only specify the language family, the tool will not match the language family and instead return directions in the default language, English. For example, if the directions language specified is pt, the tool will return the directions in English since it cannot determine whether the directions should be returned in pt-BR or pt-PT. | String |
Directions_Distance_Units (Optional) | Specifies the units that will display travel distance in the
driving directions. This parameter is used only when the Populate
Directions parameter is checked (True in Python). - Miles —The linear unit is miles.
- Kilometers —The linear unit is kilometers.
- Meters —The linear unit is meters.
- Feet —The linear unit is feet.
- Yards —The linear unit is yards.
- NauticalMiles —The linear unit is nautical miles.
| String |
Directions_Style_Name (Optional) | Specifies the name of the formatting style for the
directions. This parameter is used only when the Populate Directions parameter is checked (True in Python). - NA Desktop —Turn-by-turn directions suitable
for printing.
- NA Navigation —Turn-by-turn directions designed
for an in-vehicle navigation device.
| String |
Travel_Mode (Optional) | The mode of transportation to model in the analysis. Travel modes are managed in ArcGIS Online and can be configured by the administrator of your organization to reflect your organization's workflows. You need to specify the name of a travel mode that is supported by your organization.
To get a list of supported travel mode names, use the same GIS server connection you used to access this tool, and run the GetTravelModes tool in the Utilities toolbox. The GetTravelModes tool adds the Supported Travel Modes table to the application. Any value in the Travel Mode Name field from the Supported Travel Modes table can be specified as input. You can also specify the value from the Travel Mode Settings field as input. This reduces the tool execution time because the tool does not have to find the settings based on the travel mode name. The default value, Custom, allows you to configure your own travel mode using the custom travel mode parameters (UTurn at Junctions, Use Hierarchy, Restrictions, Attribute Parameter Values, and Impedance). The default values of the custom travel mode parameters model traveling by car. You can also choose Custom and set the custom travel mode parameters listed above to model a pedestrian with a fast walking speed or a truck with a given height, weight, and cargo of certain hazardous materials. You can try different settings to get the analysis results you want. Once you have identified the analysis settings, work with your organization's administrator and save these settings as part of a new or existing travel mode so that everyone in your organization can run the analysis with the same settings. Caution:When you choose Custom, the values you set for the custom travel mode parameters are included in the analysis. Specifying another travel mode, as defined by your organization, causes any values you set for the custom travel mode parameters to be ignored; the tool overrides them with values from your specified travel mode. | String |
Impedance (Optional) | Specifies the
impedance, which is a value that represents the effort or cost of traveling along road segments or on other parts of the transportation network. Travel time is an impedance: a car may take 1 minute to travel a mile along an empty road. Travel times can vary by travel mode—a pedestrian may take more than 20 minutes to walk the same mile, so it is important to choose the right impedance for the travel mode you are modeling. Travel distance can also be an impedance; the length of a road in kilometers can be thought of as impedance. Travel distance in this sense is the same for all modes—a kilometer for a pedestrian is also a kilometer for a car. (What may change is the pathways on which the different modes are allowed to travel, which affects distance between points, and this is modeled by travel mode settings.) Caution:The value you provide for this parameter is ignored unless Travel Mode is set to Custom, which is the default value. Choose from the following impedance values: - TravelTime —Historical and live traffic data is used. This option is good for modeling the time it takes automobiles to travel along roads at a specific time of day using live traffic speed data where available. When using TravelTime, you can optionally set the TravelTime::Vehicle Maximum Speed (km/h) attribute parameter to specify the physical limitation of the speed the vehicle is capable of traveling.
- Minutes —Live traffic data is not used, but historical average speeds for automobiles data is used.
- TruckTravelTime —Historical and live traffic data is used, but the speed is capped at the posted truck speed limit. This is good for modeling the time it takes for the trucks to travel along roads at a specific time. When using TruckTravelTime, you can optionally set the TruckTravelTime::Vehicle Maximum Speed (km/h) attribute parameter to specify the physical limitation of the speed the truck is capable of traveling.
- TruckMinutes —Live traffic data is not used, but the smaller of the historical average speeds for automobiles and the posted speed limits for trucks is used.
- WalkTime —The default is a speed of 5 km/hr on all roads and paths, but this can be configured through the WalkTime::Walking Speed (km/h) attribute parameter.
- Miles —Length measurements along roads are stored in miles and can be used for performing analysis based on shortest distance.
- Kilometers —Length measurements along roads are stored in kilometers and can be used for performing analysis based on shortest distance.
- TimeAt1KPH —The default is a speed of 1 km/hr on all roads and paths. The speed cannot be changed using any attribute parameter.
- Drive Time —Models travel times for a car. These travel times are dynamic and fluctuate according to traffic flows in areas where traffic data is available. This is the default value.
- Truck Time —Models travel times for a truck. These travel times are static for each road and don't fluctuate with traffic.
- Walk Time —Models travel times for a pedestrian.
- Travel Distance —Stores length measurements along roads and paths. To model walk distance, choose this option and ensure Walking is set in the Restriction parameter. Similarly, to model drive or truck distance, choose Travel Distance here and set the appropriate restrictions so your vehicle travels only on roads where it is permitted to do so.
If you choose a time-based impedance, such as TravelTime, TruckTravelTime, Minutes, TruckMinutes, or WalkTime, the Measurement Units parameter must be set to a time-based value. If you choose a distance-based impedance, such as Miles or Kilometers, Measurement Units must be distance based. Legacy:Drive Time, Truck Time, Walk Time, and Travel Distance impedance values are no longer supported and will be removed in a future release. If you use one of these values, the tool uses the value of the Time Impedance parameter for time-based values and the Distance Impedance parameter for distance-based values. | String |
Time_Zone_for_Time_Windows (Optional) | Specifies the time zone for the time window values on stops. The time windows are specified as part of TimeWindowStart and TimeWindowEnd fields on stops. This parameter is applicable only when the Use Time Windows parameter is checked (or set to True).
- Geographically Local —The time window values associated with the stops are in the time zone in which the stops are located. For example, if the stop is located in an area that follows eastern standard time and has time window values of 8 AM and 10 AM, the time window values will be treated as 8 a.m. and 10 a.m eastern standard time. This is the default.
- UTC —The time window values associated with the stops are in coordinated universal time (UTC). For example, if the stop is located in an area that follows eastern standard time and has time window values of 8 AM and 10 AM, the time window values will be treated as 12 p.m and 2 p.m eastern standard time, assuming eastern standard time is obeying daylight saving time. Specifying the time window values in UTC is useful if you do not know the time zone in which the stops are located or if you have stops in multiple time zones and you want all the time windows to start simultaneously.
| String |
Save_Output_Network_Analysis_Layer (Optional) | Specifies whether the analysis settings will be saved as a network analysis layer file. You cannot directly work with this file even when you open the file in an ArcGIS Desktop application such as ArcMap. It is meant to be sent to Esri Technical Support to diagnose the quality of results returned from the tool.
- Checked (True in Python)—The output will be saved as a network analysis layer file. The file will be downloaded to a temporary directory on your machine. In ArcGIS Pro, the location of the downloaded file can be determined by viewing the value for the Output Network Analysis Layer parameter in the entry corresponding to the tool execution in the geoprocessing history of your project. In ArcMap, the location of the file can be determined by accessing the Copy Location option in the shortcut menu on the Output Network Analysis Layer parameter in the entry corresponding to the tool execution in the Geoprocessing Results window.
- Unchecked (False in Python)—The output will not be saved as a network analysis layer file. This is the default.
| Boolean |
Overrides (Optional) | Additional settings that can influence the behavior of the solver when finding solutions for the network analysis problems.
The value for this parameter must be specified in JavaScript Object Notation (JSON). For example, a valid value is of the following form: {"overrideSetting1" : "value1", "overrideSetting2" : "value2"}. The override setting name is always enclosed in double quotation marks. The values can be a number, Boolean, or string. 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. For a list of supported override settings
for each solver and their acceptable values, contact Esri Technical Support. | String |
Save_Route_Data (Optional) |
Specifies whether the output will include a .zip file
that contains a file geodatabase with 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. - Checked (True in Python)—The route data will be saved as a .zip file. 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 value for the Output Route Data parameter in the entry corresponding to the tool execution in the geoprocessing history of your project. In ArcMap, the location of the file can be determined by accessing the Copy Location option in the shortcut menu on the Output Route Data parameter in the entry corresponding to the tool execution in the Geoprocessing Results window.
- Unchecked (False in Python)—The route data will not be saved as a .zip file. This is the default.
| Boolean |
Time_Impedance (Optional) | The time-based impedance is a value that represents the travel time along road segments or on other parts of the transportation network. If the impedance for the travel mode, as specified using the Impedance parameter, is time based, the values for the Time Impedance and Impedance parameters must be identical. Otherwise, the service will return an error. - Minutes —Time impedance is minutes.
- TravelTime —Time impedance is travel time.
- TimeAt1KPH —Time impedance is time at one kilometer per hour.
- WalkTime —Time impedance is walk time.
- TruckMinutes —Time impedance is truck minutes.
- TruckTravelTime —Time impedance is truck travel time.
| String |
Distance_Impedance (Optional) | The distance-based impedance is a value that represents the travel distance along road segments or on other parts of the transportation network. If the impedance for the travel mode, as specified using the Impedance parameter, is distance based, the values for the Distance Impedance and Impedance parameters must be identical. Otherwise, the service will return an error. - Miles —Distance impedance is miles.
- Kilometers —Distance impedance is kilometers.
| String |
Output_Format (Optional) |
Specifies the format in which the output features will be created.
- Feature Set —The output features will be returned as feature classes and tables. This is the default.
- JSON File —The output features will be returned as a compressed file containing the JSON representation of the outputs. When this option is specified, the output is a single file (with a .zip extension) that contains one or more JSON files (with a .json extension) for each of the outputs created by the service.
- GeoJSON File —The output features will be returned as a compressed file containing the GeoJSON representation of the outputs. When this option is specified, the output is a single file (with a .zip extension) that contains one or more GeoJSON files (with a .geojson extension) for each of the outputs created by the service.
When a file-based output format, such as JSON File or GeoJSON File, is specified, no outputs will be added to the display because the application, such as ArcMap or ArcGIS Pro, cannot 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 value for the Output Result File parameter in the entry corresponding to the tool execution in the geoprocessing history of your project. In ArcMap, the location of the file can be determined by accessing the Copy Location option in the shortcut menu on the Output Result File parameter in the entry corresponding to the tool execution in the Geoprocessing Results window. | String |
Ignore_Invalid_Locations (Optional) | Specifies whether invalid input locations will be ignored.
- SKIP —Network locations that are unlocated will be ignored and the analysis will run using valid network locations only. The analysis will also continue if locations are on nontraversable elements or have other errors. This is useful if you know your network locations are not all correct, but you want to run the analysis with the network locations that are valid. This is the default.
- HALT —Invalid locations will not be ignored. Do not run the analysis if there are invalid locations. Correct the invalid locations and rerun the analysis.
| Boolean |
