We've been analysing the use of transactions and have recently updated a parameter which m,ay have had an incorrect case and set it now to
previously it was
it seems to have made no difference.
we always GET the directions api calls with Lat/Lng so we're confused as to the transaction counts for reverse Geocoding.
Here's a sample call :-
Can you tell me why we're being allocated Reverse Geocoding transactions for this type of call ?