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
The current API specification includes a /services call that can be filtered by proximity.
The results are all matching services with all their locations so long as at least one is within the given proximity. The specification makes no recommendation on the sort order of responses although some implementations order according to relevance based on all search/filter parameters.
FutureGov has added a method for searching on service-at_location in order to return services in order of proximity to a given point, with the same service potentially appearing multiple times - once per location.
Is this something that should be added to the standard or should it be addressed differently through the existing /services method?
The text was updated successfully, but these errors were encountered:
The current API specification includes a /services call that can be filtered by proximity.
The results are all matching services with all their locations so long as at least one is within the given proximity. The specification makes no recommendation on the sort order of responses although some implementations order according to relevance based on all search/filter parameters.
FutureGov has added a method for searching on service-at_location in order to return services in order of proximity to a given point, with the same service potentially appearing multiple times - once per location.
Is this something that should be added to the standard or should it be addressed differently through the existing /services method?
The text was updated successfully, but these errors were encountered: