Fetch mapit boundary data on search page

Assigns an `@authorities` hash to the view with `DIS` and `CTY` boundaries - or a `UTA` boundary in the case of a Unitary authority (e.g. Southampton - `SO14 OAB`).

Includes an `NPA` boundary if also covered by the South Downs or New Forest National Parks Authorities (e.g. `SO21 1PL`, `SO42 7QH`)

Passes the original query through to the search results page as an address or a postcode param
Ah I see, perhaps a neater way would be to just `select` on data['areas'],
since we know that's where the areas will be anyway?

On 29 September 2014 13:45, Liz Conlan <notifications@github.com> wrote:

> In lib/themes/hampshire/controllers/applications_controller.rb:
>
> >        return false
> >      end
> > +
> > +    protected
> > +
> > +    def find_planning_authorities(data)
> > +      return [] if data.blank?
> > +      result = []
> > +      data.delete_if { |key, value| key == "debug_db_queries" }
>
> It breaks the select on the hash on the following line
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mysociety/planningalerts-app/pull/49/files#r18150859>.
>