You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Google Maps has a new(ish) service called the Routes API:
Routes API is the next generation, performance optimized version of the existing Directions API and Distance Matrix API. It helps you find the ideal route from A to Z, calculates ETAs and distances for matrices of origin and destination locations, and also offers new features.
The Routes API provides improved performance for calculating directions, distance, and travel time, making it worthwhile to replace apps that currently use Directions API and Distance Matrix API. Most of the functionality of Routes API is backward compatible with both Directions API and Distance Matrix API.
It would be great for this gem to add support for the new Routes API. It doesn't necessarily mean support needs to be dropped for the older APIs – as far as I can tell, Google has no plans to shut them down. But I think it would be great to have the flexibility to specify which API the gem uses. It sounds like there's good feature parity between the old and new APIs.
While the new Routes API is supposedly more performant, it's also worth bearing in mind that it's billed differently and needs to be enabled independently of the Directions and Distance Matrix APIs. So it seems reasonable for people to have a preference over which API is used.
The text was updated successfully, but these errors were encountered:
Google Maps has a new(ish) service called the Routes API:
Google actively recommends that developers migrate to the new API:
It would be great for this gem to add support for the new Routes API. It doesn't necessarily mean support needs to be dropped for the older APIs – as far as I can tell, Google has no plans to shut them down. But I think it would be great to have the flexibility to specify which API the gem uses. It sounds like there's good feature parity between the old and new APIs.
While the new Routes API is supposedly more performant, it's also worth bearing in mind that it's billed differently and needs to be enabled independently of the Directions and Distance Matrix APIs. So it seems reasonable for people to have a preference over which API is used.
The text was updated successfully, but these errors were encountered: