Routing to Access Points

The Navigation SDK for Android offers enhanced ways to specify waypoints, providing more accurate routing and a better arrival experience, especially for destinations with multiple entrances or specific access points. You can route to precise locations using a navigationPointToken or by combining latitude and longitude coordinates with a Place ID for added context. The destination highlighting feature will continue to be performed if applicable.

Background

Prior to v7.4, you could define a Waypoint using either latitude and longitude coordinates or a Place ID. While effective for most use cases, routing solely to a latitude and longitude can sometimes lead to suboptimal drop-off or pick-up points, particularly for large venues, parks, or buildings with multiple entrances. The result might snap to the nearest road segment, which may not be the most convenient or correct access point.

The enhanced waypoint options address this by allowing more context to be provided.

Combine Place ID and Latitude and Longitude

Starting with v7.4, you can provide both a Place ID and latitude and longitude coordinates when creating a Waypoint. This method is useful when you want to specify a precise point (the lat/lng) while still providing the context of the overall place (the Place ID). This allows the Navigation SDK to provide a richer arrival experience by highlighting the destination building or showing nearby points of interest related to the Place ID.

// Assuming 'placeId' is the Place ID String
// Assuming 'lat' and 'lng' are the double values for latitude and longitude
// Assuming 'destinationName' is a String title for the waypoint

Waypoint waypointWithPlaceIdAndLatLng = Waypoint.builder()
    .setTitle(destinationName)
    .setPlaceIdString(placeId)
    .setLatLng(lat, lng)
    .build();

// Use this waypoint in navigator.setDestinations()

Considerations:

When you provide both placeId and latlng:

• The route primarily targets the specified latlng.
• The placeId is used as context to enhance the arrival experience.
• Fallback: If the SDK determines that the provided placeId corresponds to a feature that is too far from the given latlng, the placeId will be ignored. In this scenario, routing will proceed to the latlng only, and the place-specific arrival experience enhancements won't be available.

Use a Navigation Point token

For the most precise routing to specific access points like entrances, loading docks, or designated pick-up areas, you can use a navigationPointToken. This token is obtained by calling the destinations method of the Geocoding API. It represents a specific, routable navigation point associated with a place.

To specify a Navigation Point token:

1. Obtain a navigationPointToken from the Destinations method of the Geocoding API response.
2. Create a Waypoint using the setNavigationPointToken() method in the builder.

Note: When using setNavigationPointToken(), you cannot simultaneously use setLatLng() or setPlaceIdString(). These methods are mutually exclusive with setNavigationPointToken().

// Assuming 'navPointToken' is a String obtained from the destinations method of the Geocoding API
// Assuming 'destinationName' is a String title for the waypoint

Waypoint waypointWithToken = Waypoint.builder()
    .setTitle(destinationName)
    .setNavigationPointToken(navPointToken)
    .build();

// Use this waypoint in navigator.setDestinations()

Summary of Valid Waypoint Configurations