This product or feature is in the pre-GA Experimental launch stage (pre-GA). Pre-GA products and features might have limited support, and changes to pre-GA products and features might not be compatible with other pre-GA versions. Pre-GA Offerings are covered by the Google Maps Platform Service Specific Terms. For more information, see the launch stage descriptions.

Release notes (Automotive)

2024week25 release

This release brings the Automotive-specific features listed below from Experimental to Preview. This feature set offers capabilities that allow Automotive OEMs to build their own Maps-like navigation experience with access to some cutting-edge capabilities that aren't yet available in Maps itself.

Deprecated fields. The following fields are either deprecated or are not currently used by Routes, and as such are staying in Experimental:
- VehicleInfo.totalAxleCount (not ready for Preview)
- VehicleInfo.trailerInfo (not ready for Preview)
- ExtraComputation.PREDICTED_SPEED_ON_POLYLINE_20KPH_BUCKETS (deprecated in favor of ExtraComputation.PREDICTED_SPEED_ON_POLYLINE_10KPH_BUCKETS)
- ComputeRoutes.routeToken (deprecated in favor of routeTokenOptions)
Avoid using these fields in your production code to avoid future breaking changes.
RouteTokenOptions for directions across requests. You can specify a route token by specifying RouteTokenOptions to get consistent directions across requests, similar to the way trip updates occur in Google Maps navigation. Look for RouteTokenUpdateFidelity in the response to understand how the generated route relates to the provided token.
VehicleInfo to get clearance. When attached to a trailer and using the DRIVE travel mode, you can specify the overall dimensions of your vehicle using VehicleInfo to get routes with sufficient clearance. The response will contain information on road height restrictions when the restriction is close to the vehicle's height or prevents the vehicle's passage in PolylineDetails.restrictionInfo. If a route without clearance doesn't exist, no routes will be returned.
Tunnel RouteModifiers. You can choose to avoid tunnels where possible with RouteModifiers.avoidTunnels. The response will contain information on tunnels we couldn't avoid in PolylineDetails.tunnelInfo.
Vignette RouteModifiers. You can choose to avoid vignette roads in specific countries, based on the passes the end user has paid for. To use this feature, specify RouteModifiers.avoidVignettes. The response will contain information on vignette roads we couldn't avoid in PolylineDetails.vignetteInfo and RouteTravelAdvisory.vignetteInfo.
Vignette RouteModifers. You can choose to avoid vignette roads in specific countries, based on the passes the end user has paid for. To use this feature, specify RouteModifiers.avoidVignettes. The response will contain information on vignette roads we couldn't avoid in PolylineDetails.vignetteInfo and RouteTravelAdvisory.vignetteInfo.
HOV roads RouteModifiers. You can choose to allow routing on HOV roads using RouteModifiers.hovPreference. Routes will use HOV lanes where possible, and the response will provide info on HOV segments along the route in PolylineDetails.hovInfo.
Finer-grained travel speed estimates. You can receive fine-grained travel speed estimates and incidents along the route by including PolylineDetails.predictedSpeeds and PolylineDetails.incidentInfo in your field mask and setting ExtraComputation.PREDICTED_SPEED_ON_POLYLINE_10KPH_BUCKETS.
Place ID information on polyline. You can request information on the placeId values that make up the route, for referencing against other Google APIs. To receive this information, include PolylineDetails.segmentInfo in your field mask.
Altitude along route. You can request information on the altitude along the route. To receive this information, include PolylineDetails.altitudeInfo in your field mask.
Ferries/Highways/Tolls RouteModifiers information. When using the pre-existing options to avoid ferries/highways/tolls, you can request information on the ferries, highways, and tolls that couldn't be avoided along the returned routes. To receive this information, include PolylineDetails.ferryInfo, PolylineDetails.highwayInfo, and PolylineDetails.tollInfo in your field mask.
Specify session ID. You can specify ComputeRoutes.navigationSessionId in your requests.

Documentation updates

In Generate client libraries with Bazel (Automotive) the Git method for merging repositories was removed in favor of the copy method. Additionally, an error with one of the copy directories was corrected in the commands.

2023week50 Release

Get dynamic traffic data for paths using annotatePaths

You can get dynamic traffic data for paths that you request using the annotatePaths method. By specifying the routes and traffic attributes you want to include, annotatePaths returns the input paths enriched with predicted levels of service. The paths are segmented into smaller sections to provide granular data for each segment. This traffic information can help optimize routing, enhance safety, and more. To learn more, see the following:

Use annotatePaths to get path annotations
annotatePaths (REST reference)

To authorize your requests to the annotatePaths, you must use the OAuth method described here: Use OAuth (Automotive).