ArcGIS Runtime SDK can be used to find a route between two or more locations across a transportation network. The route result can include estimated travel time and distance, as well as driving directions for traversing the route. The navigation API allows you to further enhance the routing experience using the current device location to track progress and provide navigation instructions (maneuvers) as the user travels the route. You can integrate driving directions with your device's text-to-speech capability and automatically recalculate a new route when the user leaves the current one.
The route tracker object provides the following functionality using the current device location and an appropriate route result:
- Progress information relative to the next stop, to the next maneuver, or along the entire route
- Guidance for navigation as it's needed (when approaching a maneuver, for example)
- Automatic recalculation of a route if the device location goes off route
The route result used for navigation must include stops and directions. To enable route recalculation while navigating, you must also provide the route task and routing parameters used to generate the route.
Track progress along a route
Once a route has been calculated that includes at least two stops (a start location and one or more destinations, in other words) and driving directions, you can use the route tracker to track progress as the user traverses the route. To track the current device location, you must listen for location change events on the map view location display. As the device moves, pass the new location to the route tracker to update things such as the estimated remaining travel time and distance.
- Create a route between specified locations. Generally, the route starts at the user's current location. In the route parameters, make sure to include stops and driving directions in the results.
- To show progress along a route, display two polylines: one to represent the portion of the route that has been traveled (from the start to the current location) and another to show the portion that remains (from the current location to the destination). Add these geometries to the map view as graphics (using distinct symbols) and update them from the route tracker as the route changes.
- Create a route tracker and pass in a route to travel. Handle the tracking status changed event to provide information such as the distance or time remaining to the destination. To update driving instructions when they are needed, handle the new voice guidance event.
- To enable rerouting, you must verify that the route task supports it. You must then provide the route task and parameters that were used to create the original route.
Use RouteTask.routeTaskInfo.isSupportsRerouting() to see if the underlaying route service or dataset supports recalculation of routes.
- Enable location display on the map view and handle device location updates by passing the new location to the route tracker. The tracker will update the status when it gets a new location, including whether the user is off route.
To test or demonstrate navigation functionality, you can use a simulated location data source to follow points along a predefined path. See Simulate device location updates in the "Show device's location" topic for details. To test successfully navigating a route, for example, you could use the route geometry (polyline) as the path to follow in the simulated location data source.
- In the tracking status changed event handler, create a status update for the user. This might be UI updates that include the travel time or distance remaining for the route or until the next maneuver (turn, for example). You can also warn the user if they are off route (especially if rerouting is not enabled). See the Report progress section for more information about the types of progress provided by the route tracker.
- Use the new voice guidance event handler to give driving instructions to the user. The voice guidance object that's passed into the event contains text that you can pass to a text-to-speech engine or use to update instructions shown in the UI.
- If route recalculation is enabled, you can handle the route tracker's reroute completed event to update the route (a graphic, for example) displayed in the map view. See the Handle rerouting section for more information.
The route tracker's TrackingStatus object provides values that you can use to report progress as the user traverses a route. This object is available from the route tracker directly or when the tracking status changes, allowing you to evaluate route progress any time it changes. The basic status it provides is whether the user is still traveling the route. If rerouting is enabled for the tracker, a new route will be created whenever this value is false (if the current location is on the network).
The tracking status object also provides progress relative to the following parts of the route:
- Destination—Describes progress to the next stop in the route
- Maneuver—Describes progress to the next maneuver (driving instruction, for example)
- Route—Describes progress along the entire route
Each of these types of progress is represented by the TrackingProgress object with the following information:
- Remaining distance—The distance remaining to the relevant location (next stop, next maneuver, or route end)
- Remaining geometry—A polyline representing the portion of the route between the current location and the relevant location (next stop, next maneuver, or route end)
- Remaining time—The time remaining to the relevant location (next stop, next maneuver, or route end)
- Traversed geometry—A polyline representing the portion of the route between the start of the route and the current location
The tracking status also allows you access to the route that's being traversed. Using the current maneuver index, you can find the current maneuver from the route's list of directions.
To give instructions to the user as they are approaching a maneuver, you can handle the new voice guidance event. Voice guidance notifications are generated at the time they are needed while traveling the route. You can use the text provided by the voice guidance to play the instruction using an available text-to-speech engine, or update driving instructions text in the UI.
The current speed, distance to the next maneuver, and the time required to enunciate an instruction are all considered when generating text for voice guidance. The driving directions text from the route and the distance to the maneuver can be used in the guidance, such as "in 300 meters, turn right on VENICE BLVD". Voice guidance text can be categorized as one of the following types of notifications:
- Long—Occurring immediately after a maneuver starts to describe the next one, it is formatted using the full directions text. "Go straight along Main Street, and in one mile turn right on First Street", for example.
- Moderate—Occurring 20 to 30 seconds before the maneuver, it is formatted using a parsed down form of the direction text. "In half a mile, turn right on First Street", for example.
- Short—Occurring approximately 10 seconds before the maneuver, it is formatted using a terse form of the direction text. "Turn right on First Street", for example.
- Combined—Two consecutive short maneuvers can be combined into a single voice guidance. "Turn right on First Street, then left", for example.
For any particular maneuver, one or more of these types of notifications can be generated. Abbreviations in directions text can be expanded when the voice guidance is created. "W Carolina destination is ahead" can be generated as "West Carolina destination is ahead", for example. Characters that are used it text directions, such as slashes, dashes, and so on, can be dropped from the voice guidance text.
You can enable rerouting for a route tracker only if the underlying route data (online service or local dataset) supports rerouting. Currently, rerouting is only supported for routes created from a local network dataset. You can check the route task information to verify that rerouting is supported. If it is, you can enable rerouting on the route tracker. To enable rerouting, you need the following:
- The original route task that was used to calculate the route used by the tracker
- The original route task parameters used to calculate the tracker route
- One of the following rerouting strategy values to use for the creation of new routes
- Resequence stops only—Optimize the new route for the remaining stops.
- To next stop—Reroute to the next unvisited stop in the original order.
- To next waypoint—Reroute to the next unvisited waypoint, rest break, or stop.
- Knowledge of whether the first stop in the route must be visited when creating the new route
Rerouting occurs when the user is off route and the current location is on the network. If, for example, the current location is in a parking lot that is not part of the network, a new route will not be calculated unless the user approaches the network while still off the original route. This avoids unnecessary rerouting calculations.
You can cancel rerouting while a new route is being calculated and disable rerouting to turn that functionality off. Route tracker events allow you to respond when calculation of a new route begins and when it completes. You can use the completion event to display the new route in the map view.