Directions Api consistently using 1 Directions transaction and 2 Reverse Geocoding transactions..

4 posts / 0 new
Last post
amanda@hnf
Directions Api consistently using 1 Directions transaction and 2 Reverse Geocoding transactions..

Hi,

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 

 

 

doReverseGeoCode=false

previously it was 

doReverseGeocode=false

 

 

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 :-

 http://www.mapquestapi.com/directions/v2/route?key=##########&callback=r...

 

Can you tell me why we're being allocated Reverse Geocoding transactions for this type of call ?

Thanks,

Neil

 

 


MQBrianCoakley
Hi Neil,

Hi Neil,

 

The parameter is case sensitive and should be doReverseGeocode=false. Once this is corrected, options in the route response should indicate doReverseGeocode is indeed set to false and the reverse geocodes should stop being counted.

 

Brian


amanda@hnf
Hi Brian,

Hi Brian,

That didn't seem to work either (that was the way it had been for months).

I'll revert back and monitor again today and see waht happens..

By the way.. is there any way of getting detailed logs from your system rather than summary totals per day?

Thanks,

Neil

 


MQBrianCoakley
Hi Neil,

Hi Neil,

 

No, MapQuest does not provide detailed logs by default. You could talk to an account manager to plan a Professional Services project to pull logs. But this is not something generally offered.

 

Brian