Extensions proposed by the English Local Government Association (LGA) and the local government OpenCommunity project to the OpenReferral standard for human services data. Schema generator code is given to express the schema in various formats. Data conversion routines to make it conform to the standard. API that serves the data in a format compliant with the standard.
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 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?