Unable to stop geocoding transactions in directions api

2 posts / 0 new
Last post
xenitel
Unable to stop geocoding transactions in directions api

I am unable to stop the geocoding transactions from bloating my daily transaction counts using the directions api. All I am trying to do is calculate the mileage between 2 city state locations. Is there a way to stop geocoding (doReverseGeocode=false is not working) or an easier api to use that does not exponentially drive up my transaction counts?


MQBrianCoakley
If locations for a route are
If locations for a route are a string address, then those locations need to be geocoded before getting directions. So if the route is from Toledo, OH to Detroit, MI then that request will count two geocodes and one route. If the locations are lat/lngs and doReverseGeocode is set to false, then no geocodes or reverse geocodes are counted and only one route transaction is counted. It looks like on most days there is a distinct 2:1 transaction count for Geocoding:Directions for your key. There are some days that's not the case though (May 16-23).