Use binary search logic or similar to home in on an area before using bounds

[francisbarton]

It's a bit silly to use national and regional spatial boundaries to get the search process started.

Probably a good thing to do would be:

• use boundr to get bounds for all LADs in GB/ the UK
• create a list of the bboxes for these and store this as internal package data
• make the starting point of the search a which query that establishes which bbox(es) the point is within
• then do incremental search (LAD -> MSOA -> LSOA > OA) from there

This saves using boundr to look up national and regional boundary data, and saves getting all the LAD bounds for a region - instead you just get the handful (possibly just 1) LAD boundary that you need.

You could start with stored regional bboxes, and bboxes for Scotland and Wales too I suppose.

[francisbarton]

I mean, you could store bbox data all the way down, but I think querying using boundr makes more sense when you get down to sub-LAD level. You'll only have like 20 MSOAs in a LAD area to query.