Available with Network Analyst license.
Directions are turn-by-turn instructions on how to navigate a route. They can be created for any route that is generated from a network analysis as long as the network dataset supports them. The minimum requirements for a network dataset to support directions are as follows:
- A length attribute with length units
- At least one edge source
- At least one text field on the edge source
The directions generated when a route is computed are customizable at the network dataset level. This means that the street names used for reporting directions, shields, and boundary information are stored with the network dataset schema. These settings can be modified to customize the directions.
You can change these settings from the Network Directions Properties dialog box, which is accessed by clicking the Directions button in either the New Network Dataset wizard or on the Directions tab of the Network Dataset Properties dialog box.
Network Directions Properties dialog box
The units used to report directions and the fields used to identify streets can be modified on the General tab, which is shown in the graphic below.
Directions Settings frame
Display Length Units is where you choose the units used to report the length. For example, if miles are chosen, all directions generated for this network dataset would be reported in miles. The ArcGIS Network Analyst extension supports the following five length units: feet, kilometers, meters, miles, and yards.
Length Attribute is used to calculate the length of each segment of the route for which the directions are reported. Any cost attribute can be selected as the length attribute. ArcGIS automatically searches through the network attributes and tries to assign the relevant cost attribute.
Time Attribute is used to calculate the time taken to traverse each segment during the reporting of directions.
Signpost Feature Class and Signpost Streets Table provide the text of the highway signs that a driver would typically see when traveling along the route. This highway sign text usually includes the exit number, name of the road, and the destination where the road leads. This text can be incorporated into the directions text to facilitate navigation—for example, Take ramp and go on US-59 N toward Springfield.
Learn more about the signpost feature class and streets table
Street Name Fields frame
Street name fields can be set up for each edge source in the network. These are the names that are used to report directions. For instance, the name of the street (First Ave) is obtained from this field to report directions, such as, "Turn left onto First Ave." The Name column displays a drop-down list of text fields for the source, from which a street name field can be chosen.
Some feature classes have directional modifiers (N or S) and street types (Ave, St, or Dr) in separate fields. In such cases, the entire street name resides in the three different fields.
Some feature classes have alternate names of streets listed in different fields. These can be set up by increasing the Number of Alternate Names value and setting up the Name field along with the optional Prefix and Suffix fields.
Landmarks are point features designed to represent clearly visible objects along the network. Turn-by-turn directions can reference landmarks to help whoever is navigating a route identify turns and verify the correct route is being followed.
Network Analyst notes landmarks in directions when landmark feature classes are configured on the network dataset, on the Landmarks tab, and a route passes within the search tolerance of a landmark feature.
Landmarks are associated with specific edge sources. It's possible to have a landmark near two edge sources, but the landmark will only be referred to in directions when the route traverses the edge source related to the landmark. Use the Network Source property to choose an edge source.
Two kinds of landmark feature classes exist: turn landmarks and confirmation landmarks. Turn landmarks represent objects near junctions that help identify turns; for example, the purple wall in "Turn right at the purple wall." is a turn landmark. Confirmation landmarks are objects along edges used to reaffirm the navigator he or she is on course; for example, the A-frame building in "Pass by the A-frame building. It will be on your right." is a confirmation landmark. You set turn and confirmation landmarks in the respective frames: Turn Landmarks and Confirmation Landmarks.
Add a landmark feature class by clicking an Add Data button on the right, and delete one using a Delete button . The tables in the Turn Landmarks and Confirmation Landmarks frames have the same fields. They are listed and described below.
The point feature class added as a landmark source.
The text field in the landmark feature class that describes the landmark. This field might contain values such as Alan's Hardware Store for driving directions or the printer station for walking directions, so that directives might appear as Turn right at Alan's Hardware Store or Pass by the printer station. It will be on your left.
This field is typically used with walking directions to associate landmarks with a specific floor level of a building.
This Yes/No field lets you specify whether the landmark feature class should use a custom search radius or the default, which is 50 feet. (The 50-foot default search radius can be changed through ArcObjects, so it is recommended that you set a search tolerance for each landmarks source.)
The size of the search radius. In general, when a route passes by a landmark within the search radius, it is reported in the directions. The units for this field are specified under Units.
The units of the Tolerance value that specify a search radius. In general, when a route passes by a landmark within the search radius, it is reported in the directions.
Road Detail tab
The Road Detail tab is split into two frames: Network Attribute Mappings and Field Mappings.
Network Attribute Mappings frame
Road Class Attribute provides specific directions for different types of roads and other linear features. It is a descriptor attribute of type integer whose values are as follows:
|Road class value||Type of road class||Example directions text|
Turn left on Main St.
Go east on I-55.
Take ramp and go on US-59 N.
Take Lake Expy ferry.
Take roundabout and proceed south on Main St.
Turn left on Redlands Blvd.
Turn left and go through M1w Hallway.
Take the stairs up.
Take the escalator up.
Take the elevator up.
Take the ramp up to level 2.
ManeuverClass Attribute identifies to the driving directions small connecting roads inside of or adjacent to the street intersection. It is a descriptor attribute of type integer whose values are shown in the following table:
|ManeuverClass value||ManeuverClass type||Description|
Default value assigned to streets outside of street intersections.
Street segments internal to an intersection of double-digitized roads.
Street segments forming a turning slip lane (often found where streets intersect at a sharp angle).
Field Mappings frame
Administrative Area—Some edge sources have an administrative area field that denotes what region each edge is in. For instance, a highway source could have a state field that denotes what state the highway segment is in. This is useful in generating directions such as "Enter California" when crossing the state line. While generating directions, any change in the value of the administrative area value is reported.
LevelNumber—The edge sources representing the hallways of a multi-story building may have an integer field that indicates the level number of the building where each hallway is located. For example, this field may have a value of 3 for a hallway on the third floor, or a value -1 for a hallway on the first underground level. This is useful for identifying all the hallways along a route are on each building's level by number. For transition edges spanning levels, set the From-To Field and To-From Field to reference the two fields holding the level information for each end of the edge.
FloorName—The edge sources representing floor transitions within a building, such as elevators, stairways, and escalators, may have a pair of text fields that indicates the names of the floors these transitions connect. For example, there may be a stairway that connects the Mezzanine Level to the Promenade Level. These fields would then have values of "Mezzanine Level" and "Promenade Level".
When generating directions, the FloorName fields are used together with the numeric LevelNumberfields to instruct the reader to go up or down to the appropriate level by its name. In the previous example, generating directions for that stairway will instruct the reader to "Take the stairs down to the Mezzanine Level" or "Take the stairs up to the Promenade Level".
Shields are signs that display highway numbers. Some edge sources have shield information (for example, I-15, CA-72, or OH-10) that can be used to report directions. For instance, if you have a freeway source that has interstates and state highways, the road shield descriptions can be specified for this source. For example, the Santa Ana Freeway has a shield description of I-5. Both the street name field (which contains Santa Ana Freeway) and the road description field (I-5) can be used to report directions.
Some sources have road shield descriptions in one field (I-10 or CA-63). In such a case, choose Single Field and choose the field containing road shield descriptions.
A source can also have shield descriptions in two fields: one is the shield type (containing values such as I, CA, or TN) and the other is the number (5 or 43). Together, they give the complete road shield description. In such a case, choose Pair of Fields and set Type Field and Number Field.
If your data splits the type and number into a pair of fields, the shield type (I, CA, or TN) can be associated with shield descriptions (Interstate, California, or Tennessee). This would result in directions such as "Take Interstate 10 for 155 miles."