HSDA Proximity Search Parameters (latitude, longitude, radius)

[kinlane]

Adding proximity search for HSDA, across all the core resources (organization, locations, and services).

• Issue: /search #46 (comment)
• OpenAPI: https://gist.github.com/kinlane/d412b5adbd69fae2b5f6a761e1bfdef3

[boxfoot]

@kinlane is there a way to see the changes associated with this proposal as a PR or diff so it's easier to zero in on what changed? (similar comment for many of the issues, BTW). Thanks so much for everything you're doing on this!

[kinlane]

That is the next step of the process, is to produce the full OpenAPI for HSDA, HSDA Search, and HSDA Taxonomies, then we can do a diff between entire documents. It will limit the individual feature (issue) conversation thread, which is why I went to the individual issue + OpenAPI snippet. Will publish when ready.

[MikeThacker1]

Just a note that we've had a request to do a proximity search based on latitude and longitude in the UK. So far we've recommended filtering by postcode and proximity in meters.

Postcode may be seen as an alternative to latitude and longitude as it covers quite a precise area in the UK and its centroid is easily available.

A user is likely to know a postcode. If that is sent to the API, it can do the work of converting to lat/long. However some tools would put that in a different layer.