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 facet parameters for the occurrence API include facetOffset and facetLimit and the documentation states that these are to allow paging requests through large number numbers of facet values.
Please can this be similarly implemented for facets? I think the response could look something like this - where offset, limit, endOfRecords and count are specified within the facet element. (But maybe endOfRecords would be better named endOfFacets?)
The facet parameters for the occurrence API include
facetOffset
andfacetLimit
and the documentation states that these are to allow paging requests through large number numbers of facet values.The limit and offset values for result paging are documented with maximum values (https://techdocs.gbif.org/en/openapi/v1/occurrence#/Searching%20occurrences/searchOccurrence), and the JSON response includes a result count to enable the user to determine how many paging calls are required.
Please can this be similarly implemented for facets? I think the response could look something like this - where
offset
,limit
,endOfRecords
andcount
are specified within the facet element. (But maybeendOfRecords
would be better namedendOfFacets
?)The text was updated successfully, but these errors were encountered: