You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we can query for N records within X miles of a postalCode.
However, it would be helpful to request matches nearest a lat/long so that a browser's location API can be used to source the end-users location center.
Using a Lat/Long Center
/nearest/{count}/{sourceType}/to/{latitude}/{longitude}/within/{miles}
or
/nearest/{count}/{sourceType}/to/{latitude_longitude}/within/{miles}
The format of the lat/long could either be as separate parameters or perhaps it needs to be in a single parameter formatted like (32.947560, -96.839760) if the route parser can't disambiguate between other route paths.
The text was updated successfully, but these errors were encountered:
Currently, we can query for
N
records withinX
miles of apostalCode
.However, it would be helpful to request matches nearest a lat/long so that a browser's location API can be used to source the end-users location center.
Using a Lat/Long Center
The format of the lat/long could either be as separate parameters or perhaps it needs to be in a single parameter formatted like
(32.947560, -96.839760)
if the route parser can't disambiguate between other route paths.The text was updated successfully, but these errors were encountered: