Get Collection Items
const url = 'https://example.com/collections/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/items?limit=10&offset=0&include_geometry=true';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://example.com/collections/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/items?limit=10&offset=0&include_geometry=true'OGC API Features items endpoint — returns GeoJSON FeatureCollection for a dataset.
Note: datetime is accepted per OGC API Features Core but acts as a
no-op for per-dataset feature queries. Per-dataset feature tables contain
user-uploaded data with no standard temporal column, so the spec provision
“if the collection does not include temporal information, the datetime
parameter SHALL be ignored” applies (OGC 17-069r4 §7.15.5).
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Query Parameters
Section titled “Query Parameters ”Page size for bulk GeoJSON export. The maximum is an admin-configurable ceiling (default 1000; Network settings tab, ogc_items_max_page_size) rather than the 200 used by offset-paged list endpoints, because this route pages via the constant-time after_gid keyset cursor. Per OGC API Features Core /req/core/fc-limit-response-1(C) a value above the ceiling is clamped to it, not rejected.
Page size for bulk GeoJSON export. The maximum is an admin-configurable ceiling (default 1000; Network settings tab, ogc_items_max_page_size) rather than the 200 used by offset-paged list endpoints, because this route pages via the constant-time after_gid keyset cursor. Per OGC API Features Core /req/core/fc-limit-response-1(C) a value above the ceiling is clamped to it, not rejected.
Legacy offset-based pagination. Prefer after_gid keyset cursor (via the next link) — offset is retained for backward compatibility but is O(N) at high values.
Legacy offset-based pagination. Prefer after_gid keyset cursor (via the next link) — offset is retained for backward compatibility but is O(N) at high values.
Include geometry in response. Set to false for attribute-only queries.
Include geometry in response. Set to false for attribute-only queries.
Responses
Section titled “ Responses ”Successful Response
FeatureCollection response as defined by OGC API - Features.
object
GeoJSON object type.
ISO 8601 timestamp the response was generated.
Total number of features matching the query (across all pages).
Number of features in this response page.
GeoJSON features returned by the query.
object
Pagination and self-reference links.
object
Target URL of the link.
Link relation type per RFC 8288 (e.g. ‘self’, ‘next’, ‘prev’, ‘data’, ‘collection’).
Media type of the linked resource (e.g. ‘application/json’, ‘application/geo+json’).
Example
{ "type": "FeatureCollection"}Example generated
exampleBad request — invalid query parameters or payload
Unauthenticated — a credential was supplied and could not be resolved (expired, revoked, or malformed). Sending no credential at all is not an error on these operations; they answer anonymously with the public subset. Neither is sending an unresolvable credential alongside a capability that authorizes the request on its own — a valid X-Embed-Token or a valid signed tile template (sig, exp, scope). Those are served and the unrelated credential is ignored.
Not found
Too many requests — retry after the advertised interval
Headers
Section titled “Headers ”Seconds until the request may be retried
Internal server error
Service unavailable — the database could not serve the request