Extra of unexpected calls of the geocoding api

7 posts / 0 new
Last post
javikr
Extra of unexpected calls of the geocoding api

Hello,

We are using only the directions api for route calculation. We have set the "doReverseGeocoding" to false and we don't use any api method of the geocoding services. The problem is that there are tons of transactions of the geocoding service registered in the developer panel and we don't know why. We have the Basic service plan.

Please, we need support asap because we are going to reach the 30.000 transactions limit very soon.

Best regards, Javier.

 

 

 

 


MQBrianCoakley
Can you post a sample request
Can you post a sample request (no key needed) to mapquestapi.com so we can see how the parameter is being set?

javikr
Hi!

Hi!

This is an example of get request for the directions api:

{
"ambiguities": "ignore",
"locations": [
{
"latLng": {
"lat": 40.4842,
"lng": -3.72677
}
},
{
"latLng": {
"lat": 40.47211,
"lng": -3.71307
}
},
{
"latLng": {
"lat": 40.41894,
"lng": -3.7075
}
},
{
"latLng": {
"lat": 40.42025,
"lng": -3.6979
}
},
{
"latLng": {
"lat": 40.42718,
"lng": -3.70077
}
},
{
"latLng": {
"lat": 40.41221,
"lng": -3.72703
}
},
{
"latLng": {
"lat": 40.4189,
"lng": -3.70786
}
},
{
"latLng": {
"lat": 40.41936,
"lng": -3.70026
}
},
{
"latLng": {
"lat": 40.42027,
"lng": -3.69832
}
},
{
"latLng": {
"lat": 40.4342,
"lng": -3.71048
}
},
{
"latLng": {
"lat": 40.42547,
"lng": -3.70458
}
},
{
"latLng": {
"lat": 40.41932,
"lng": -3.70753
}
},
{
"latLng": {
"lat": 40.4138,
"lng": -3.69767
}
},
{
"latLng": {
"lat": 40.39944,
"lng": -3.69851
}
},
{
"latLng": {
"lat": 40.44643,
"lng": -3.71063
}
},
{
"latLng": {
"lat": 40.42242,
"lng": -3.7001
}
},
{
"latLng": {
"lat": 40.42859,
"lng": -3.67096
}
},
{
"latLng": {
"lat": 40.41581,
"lng": -3.70247
}
},
{
"latLng": {
"lat": 40.4234,
"lng": -3.70942
}
},
{
"latLng": {
"lat": 40.44693,
"lng": -3.70752
}
},
{
"latLng": {
"lat": 40.42814,
"lng": -3.7013
}
},
{
"latLng": {
"lat": 40.42527,
"lng": -3.70728
}
},
{
"latLng": {
"lat": 40.44678,
"lng": -3.7146
}
},
{
"latLng": {
"lat": 40.41093,
"lng": -3.7124
}
},
{
"latLng": {
"lat": 40.42643,
"lng": -3.64176
}
},
{
"latLng": {
"lat": 40.41588,
"lng": -3.70161
}
},
{
"latLng": {
"lat": 40.40073,
"lng": -3.69641
}
},
{
"latLng": {
"lat": 40.41867,
"lng": -3.70825
}
},
{
"latLng": {
"lat": 40.42266,
"lng": -3.70174
}
},
{
"latLng": {
"lat": 40.42373,
"lng": -3.70185
}
}
],
"outFormat": "json",
"options": {
"unit": "k",
"locale": "es_ES",
"timeType": 1,
"generalize": 0,
"shapeFormat": "raw",
"routeType": "pedestrian",
"narrativeType": "html",
"enhancedNarrative": "false"
},
"doReverseGeocode": "false"
}


MQDennisClarke
doReverseGeocode option
Move the parameter for doReverseGeocode inside the options brackets.   "options": {"unit": "k","locale": "es_ES","timeType": 1,"generalize": 0,"shapeFormat": "raw","routeType": "pedestrian","narrativeType": "html","enhancedNarrative": "false","doReverseGeocode": "false" }

javikr
Thanks

Ok. Thank you. I will update the code.

Best regards,

Javier

 


acemary
I'm testing out the Reverse

I'm testing out the Reverse geocoding api and have a url string that initially looks like this:

But as it passes through the API, the lat/longs get shortened to only 5 decimal points, thus making the geocoding less than accurate. Of course, it's in the neighborhood, but is there a way to maintain the full length of the lat/longs to have even better accuracy?


MQBrianCoakley
There is no method to
There is no method to maintain more decimal places. The apis return 6 decimal places in all responses.