Find Routes Tools
How to use Find Routes Tool in Arc Toolbox ArcMap ArcGIS??
 |
| Find Routes |
Path to access the tool
:
Find
Routes Tool, Server Toolset, Network Analyst Tools Toolbox
Find Routes
Finding a route analysis
can mean determining the quickest or shortest way to travel between locations.
You might want to use this tool to generate driving directions to visit
multiple stops or to measure the distance or travel time between locations. The
tool is capable of finding routes for one or more vehicles each time it runs,
so you can determine the best routes for several drivers to visit preassigned
stops, for instance, or measure in a single solve the distance of home-to-work
trips for many commuters.
The Find Routes and Make
Route Layer tools are similar,
but they are designed for different purposes.
Use Find Routes if you are setting up a geoprocessing service; it simplifies
the setup process; otherwise, use Make Route Layer.
To create a routing
geoprocessing service using Find Routes, you only need to set up one tool, and
you can publish the tool directly as a service. In contrast, you need to create
a model with the Make Routes Layer tool, properly connect it to various other
tools, and publish the model to create a geoprocessing service. See Overview of
the Network Analyst geoprocessing service examples to learn how to set up a
closest facility service using tutorial data.
One other option to
consider is the ArcGIS Online Find Routes service. the service runs like a
geoprocessing tool in ArcMap, can be accessed from other applications, and
includes high-quality road data for much of the world.
1. Stops
This tool routes between
the stops specified in this parameter. A minimum of two stops are necessary to
solve an analysis.
When specifying the
stops, you can set properties for each one, such as its name or service time,
by using attributes. The stops can be specified with the following attributes:
- OBJECTID—The system-managed ID field.
- SHAPE—The geometry field indicating the geographic location of the incident.
- 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. With this tool 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. Within a group of stops that have the same route name 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 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. The default value is 0.
- 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.
- AdditionalDistance—The extra distance traveled at the stops, which is added to the total distance of the route. 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. The default value is 0.
- 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.
- TimeWindowStart—The earliest time the stop can be visited. Make sure you specify the value as a date and time value, such as 8/12/2015 12:15 PM. By specifying a start and end time for a stop's time window, you are defining when a route should visit the stop. As long as Use Time Windows is checked and you've chosen a time-based unit for Measurement Units, the tool will try to find a solution that minimizes overall travel and reaches the stop within the prescribed time window.
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 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. Make sure you specify the value as a date and
time value, such as 8/12/2015 12:15 PM. By specifying a start and end time for
a stop's time window, you are defining when a route should visit the stop. As
long as Use Time Windows is checked and you've chosen a time-based unit for Measurement
Units, the tool will try to find a solution that minimizes overall travel and
reaches the stop within the prescribed time window.
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 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 your 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 stop 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
property 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, you would choose
Right side of vehicle (1) in the United States but Left side of vehicle (2) in
the United Kingdom.
2. Measurement Units
Specify the units that
should 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. The choices include the following:
- Meters
- Kilometers
- Feet
- Yards
- Miles
- NauticalMiles
- Seconds
- Minutes
- Hours
- Days
The tool chooses whether
to use the network cost attribute specified in the Time Attribute or Distance
Attribute parameter depending on whether the chosen measurement units are time
or distance based.
The tool performs the
necessary unit conversion when the Measurement Units value differs from the
units of the corresponding time or distance cost attribute.
3. Network Dataset
The network dataset on
which the analysis will be performed. Network datasets most often represent
street networks but may represent other kinds of transportation networks as
well. The network dataset needs at least one time-based and one distance-based
cost attribute.
4. Output Geodatabase
The output workspace.
This workspace must already exist. The default output workspace is in_memory.
5. Output Routes Name
The name of the output
feature class containing routes or the lines that connect stops. This feature
class also contains, as an attribute, the total travel time or distance.
Output from Find Routes
describes the schema of this output feature class.
6. Output Route Edges Name
The name of the output
feature class containing the route edges. Route edges represent the individual
street features that are traversed by a route.
Output from Find Routes
describes the schema of this output feature class.
7. Output Directions Name
The name of the output
feature class containing directions.
Output from Find Routes
describes the schema of this output feature class.
8. Output Stops Name
The name of the output
feature class containing the output stops.
Output from Find Routes
describes the schema of this output feature class.
9. Reorder Stops to Find Optimal Routes (optional)
Specify whether to visit the stops in the order you define or the order the tool determines will minimize overall travel.
- Checked (True): The tool determines the sequence that will 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): The stops are visited in the order you define. This is the default option. 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.
Finding the optimal stop
order and the best routes is commonly known as solving the traveling salesman
problem (TSP).
10. Preserve Terminal Stops (optional)
When Reorder Stops to
Find Optimal Routes is checked (or True), you have options to 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_BOTH—Preserves the first and last stops by input order as the first and last stops in the route.
- PRESERVE_FIRST—Preserves the first stop by input order as the first stop in the route, but the last stop is free to be reordered.
- PRESERVE_LAST—Preserves the last stop by input order as the last stop in the route, but the first stop is free to be reordered.
- PRESERVE_NONE—Frees both the first and last stop to be reordered.
Preserve Terminal Stops
is ignored when Reorder Stops to Find Optimal Routes is unchecked (or False).
11. Return to Start (optional)
Choose whether routes
should 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 should start and end at the first stop feature. This is the default value.
- Unchecked (False) - The route won't start and end at the first stop feature.
12. Travel Mode (optional)
Choose the mode of
transportation for the analysis. Custom is always a choice. For other travel
mode names to appear, they must be present in the network dataset specified in
the Network Dataset parameter.
A travel mode is defined on a network dataset and provides override values for parameters that, together, model cars, trucks, pedestrians, or other modes of travel. By choosing a travel mode here, you don't need to provide values for the following parameters, which are overridden by values specified in the network dataset:
- UTurn Policy
- Time Attribute
- Time Attribute Units
- Distance Attribute
- Distance Attribute Units
- Use Hierarchy in Analysis
- Restrictions
- Attribute Parameter Values
- Route Line Simplification Tolerance
- CUSTOM—Define a travel mode that fits your specific needs. When Custom is chosen, the tool does not override the travel mode parameters listed above. This is the default value.
14.
Barriers
15.
Custom Travel Mode
16.
Network Dataset
17.
Network Location
18.
Output
19. Service Capabilities
All the seven additional categories are explained in detail, click here to access their explanation
Comments
Post a Comment