Skip to content
This repository has been archived by the owner on Oct 4, 2023. It is now read-only.

HSDA Proximity Search Parameters (latitude, longitude, radius) #89

Open
kinlane opened this issue Oct 11, 2018 · 3 comments
Open

HSDA Proximity Search Parameters (latitude, longitude, radius) #89

kinlane opened this issue Oct 11, 2018 · 3 comments

Comments

@kinlane
Copy link
Contributor

kinlane commented Oct 11, 2018

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

@boxfoot
Copy link
Contributor

boxfoot commented Oct 12, 2018

@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
Copy link
Contributor Author

kinlane commented Jan 28, 2019

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
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants