Get Dataset Collection
const url = 'https://example.com/collections/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';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-32D5F69181C0Per-dataset OGC collection metadata with extent, CRS, and items link.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Query Parameters
Section titled “Query Parameters ”Responses
Section titled “ Responses ”Successful Response
Per-dataset collection metadata per OGC API Features.
object
Coordinate reference systems supported for items in this collection.
Stable collection identifier (typically the dataset ID).
Type of items in the collection: ‘feature’ for vector feature collections, ‘coverage’ for raster/VRT collections (which expose tiles instead of feature items).
Collection navigation links (self, items, queryables, etc.).
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’).
Human-readable collection title.
Example
{ "crs": [ "http://www.opengis.net/def/crs/OGC/1.3/CRS84" ], "itemType": "feature"}Bad request — invalid query parameters or payload
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