BoundingBox property as returned by a directions request

4 posts / 0 new
Last post
erwinb
BoundingBox property as returned by a directions request

I'm doing a directions request from (for instance) Figueres (Spain) to Aix-en-Province (France).

Figueres is on the right side of Spain, near Barcelona. Aix-en-Province is north east of Figueres, so the resulting route goes up and to the right. The resulting bounding box is as follows: 43.80852, 2.94059 - 42.26632, 5.44749.

If you look at the route, you'll see that the road first goes a bit northwest, then turning to northeast, and finally to the east. The bounding box, however, does not include the part where the road goes to the northwest. The longitude of the "ul" property seems to be based on the starting point, not on the shapes.

Is that by design? Should I calculate the correct bounding box myself? Or is this an issue with the MapQuest implementation of the boundingbox property? 


MQDennisClarke
RE: BoundingBox property as returned by a directions request
Our Geocode API is not recognizing Aix-en-Province, France. What HTTP request are you making for these directions?

erwinb
Sorry, my bad. It's Aix-en

Sorry, my bad. It's Aix-en-Provence.


erwinb
And the full request is http: