Is boundingBox really boundingLine?

4 posts / 0 new
Last post
kingsleyraspe
Is boundingBox really boundingLine?

Hi, 

Firstly, thanks for a great service! 15,000 free calls is incredible! 

I'm looking up traffic incidents in an area of lat/lon that I've defined. I'm also doing a few other things with this area. It's a good 50 miles x 50 miles, but in a sort of shield shape, not a box.

If I query Mapquest with the entire bounds, it returns 0 results: https://www.mapquestapi.com/traffic/v2/incidents?&outFormat=json&boundin...

However, if I define bounding box as a straight line, and not a "box" that I have defined, such as: https://www.mapquestapi.com/traffic/v2/incidents?&outFormat=json&boundin..., it has construction defined. Even though those coordinates are included in my bounding box above, they are never included. 

Even in the example: https://developer.mapquest.com/documentation/traffic-api/incidents/get/, boundingBox is defined as two comma seperated lat/lons, and not multi point/polygon. 

Is this the case? Or am I doing something incorrectly?

Appreciate it


MQBrianCoakley
The parameter, as labeled, is
The parameter, as labeled, is a box. The coordinates provided should be the upper left and lower right corners of the box. Polygons are not supported by the traffic API. It is intended to display incidents within the view of a map - thus, the box.

kingsleyraspe
Ah, that makes great sense

Ah, that makes great sense now!

I was confused as there were only two points, not four, so I thought it was missing the 3 sides of the box, but now you mentioned from upper left to lower right, it makes sense why it's boundingBox. 

Appreciate your quick reply! 


MQBrianCoakley
Cool. I'm glad it helped.
Cool. I'm glad it helped.