Latitude longitude filter

Latitude/Longitude filter:

This filter let you define points and a radius in order to define areas. Then, the filter could discard bid requests not belonging to those areas.

Agent config example to use the filter:

{
...
"latLongDevFilter": [{"lat": 37.123, "radius": 15.5, "long": -92.456}]
...
} 

Regarding the MBR, did you mean to use a particular MBR for each latlongFilter (typically for each agent config/campaign) as they would be generally close ?

About the data-structures: the thing is that in our particular use case, we did not contemplate the case of having a lot of points. The main idea was to just put a few points (1 or 2) per filter. Like, i want all the BR near this shop (located in a particular place) or something like that.
Although, now that i am thinking a bit more, did you mean to have a data-structure (like quad-tree) for indexing all the points of all the configs ? In that case i think it would be helpfull.
Unfortunately my priorities at work does not include this issue at the top list and this does not look so easy to implement. But contributions are welcome :).