---
title: "Get the feature collections in the dataset"
method: GET
path: "/collections"
tags: ["Features"]
---

# Get the feature collections in the dataset

`GET /collections`

A body of Feature Collections that belong or are used together with additional links.
Request may not return the full set of metadata per Feature Collection.

## Response `200`

The feature collections shared by this API.

The dataset is organized as one or more feature collections. This resource
provides information about and access to the collections.

The response contains the list of collections. For each collection, a link
to the items in the collection (path `/collections/{collectionId}/items`,
link relation `items`) as well as key information about the collection.
This information includes:

* A local identifier for the collection that is unique for the dataset;
* A list of coordinate reference systems (CRS) in which geometries may be returned by the server. The first CRS is the default coordinate reference system (the default is always WGS 84 with axis order longitude/latitude);
* An optional title and description for the collection;
* An optional extent that can be used to provide an indication of the spatial and temporal extent of the collection - typically derived from the data;
* An optional indicator about the type of the items in the collection (the default value, if the indicator is not provided, is 'feature').

- Collections
  - `links` Link[], required
    - `href` string, uri, required — The location of the resource
    - `rel` string, required — Relation type of the link
    - `type` string — The media type of the resource
    - `title` string — Title of the resource
    - `method` 'GET' | 'POST' — Specifies the HTTP method that the resource expects
    - `headers` object — Object key values pairs they map to headers
    - `body` object — For POST requests, the resource can specify the HTTP body as a JSON object.
    - `merge` boolean — This is only valid when the server is responding to POST request. If merge is true, the client is expected to merge the body value into the current request body before following the link. This avoids passing large post bodies back and forth when following links, particularly for navigating pages through the `POST /search` endpoint. NOTE: To support form encoding it is expected that a client be able to merge in the key value pairs specified as JSON `{"next": "token"}` will become `&next=token`.
  - `collections` Collection[], required
    - `stac_version` string, required
    - `stac_extensions` union[]
      - union
        - string, uri
        - string
    - `type` string, required
    - `id` string, required — identifier of the collection used, for example, in URIs
    - `title` string — human readable title of the collection
    - `description` string, required — Detailed multi-line description to fully explain the catalog or collection. [CommonMark 0.29](http://commonmark.org/) syntax MAY be used for rich text representation.
    - `keywords` string[] — List of keywords describing the collection.
    - `license` string, required — License(s) of the data as a SPDX [License identifier](https://spdx.org/licenses/). Alternatively, use `proprietary` if the license is not on the SPDX license list or `various` if multiple licenses apply. In these two cases links to the license texts SHOULD be added, see the `license` link relation type. Non-SPDX licenses SHOULD add a link to the license text with the `license` relation in the links section. The license text MUST NOT be provided as a value of this field. If there is no public license URL available, it is RECOMMENDED to host the license text and link to it.
    - `extent` Extent, required — The extent of the features in the collection. In the Core only spatial and temporal extents are specified. Extensions may add additional members to represent other extents, for example, thermal or pressure ranges. The first item in the array describes the overall extent of the data. All subsequent items describe more precise extents, e.g., to identify clusters of data. Clients only interested in the overall extent will only need to access the first item in each array.
      - `spatial` object, required — The spatial extent of the features in the collection.
        - `bbox` array[], required — One or more bounding boxes that describe the spatial extent of the dataset. The first bounding box describes the overall spatial extent of the data. All subsequent bounding boxes describe more precise bounding boxes, e.g., to identify clusters of data. Clients only interested in the overall spatial extent will only need to access the first item in each array.
          - number[] — Each bounding box is provided as four or six numbers, depending on whether the coordinate reference system includes a vertical axis (height or depth): * Lower left corner, coordinate axis 1 * Lower left corner, coordinate axis 2 * Minimum value, coordinate axis 3 (optional) * Upper right corner, coordinate axis 1 * Upper right corner, coordinate axis 2 * Maximum value, coordinate axis 3 (optional) The coordinate reference system of the values is WGS 84 longitude/latitude (http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate reference system is specified in `crs`. For WGS 84 longitude/latitude the values are in most cases the sequence of minimum longitude, minimum latitude, maximum longitude and maximum latitude. However, in cases where the box spans the antimeridian the first value (west-most box edge) is larger than the third value (east-most box edge). If the vertical axis is included, the third and the sixth number are the bottom and the top of the 3-dimensional bounding box. If a feature has multiple spatial geometry properties, it is the decision of the server whether only a single spatial geometry property is used to determine the extent or all relevant geometries.
        - `crs` 'http://www.opengis.net/def/crs/OGC/1.3/CRS84' — Coordinate reference system of the coordinates in the spatial extent (property `bbox`). The default reference system is WGS 84 longitude/latitude. In the Core this is the only supported coordinate reference system. Extensions may support additional coordinate reference systems and add additional enum values.
      - `temporal` object, required — The temporal extent of the features in the collection.
        - `interval` array[], required — One or more time intervals that describe the temporal extent of the dataset. The first time interval describes the overall temporal extent of the data. All subsequent time intervals describe more precise time intervals, e.g., to identify clusters of data. Clients only interested in the overall extent will only need to access the first item in each array.
          - string[] — Begin and end times of the time interval. The timestamps are in the coordinate reference system specified in `trs`. By default this is the Gregorian calendar. The value `null` is supported and indicates an open time interval.
        - `trs` 'http://www.opengis.net/def/uom/ISO-8601/0/Gregorian' — Coordinate reference system of the coordinates in the temporal extent (property `interval`). The default reference system is the Gregorian calendar. In the Core this is the only supported temporal reference system. Extensions may support additional temporal reference systems and add additional enum values.
    - `providers` object[] — A list of providers, which may include all organizations capturing or processing the data or the hosting provider. Providers should be listed in chronological order with the most recent provider being the last element of the list.
      - `name` string, required — The name of the organization or the individual.
      - `description` string — Multi-line description to add further provider information such as processing details for processors and producers, hosting details for hosts or basic contact information. [CommonMark 0.29](http://commonmark.org/) syntax MAY be used for rich text representation.
      - `roles` string[] — Roles of the provider. The provider's role(s) can be one or more of the following elements: * licensor: The organization that is licensing the dataset under the license specified in the collection's license field. * producer: The producer of the data is the provider that initially captured and processed the source data, e.g. ESA for Sentinel-2 data. * processor: A processor is any provider who processed data to a derived product. * host: The host is the actual provider offering the data on their storage. There should be no more than one host, specified as last element of the list.
      - `url` string, url — Homepage on which the provider describes the dataset and publishes contact information.
    - `links` Link[], required
      - `href` string, uri, required — The location of the resource
      - `rel` string, required — Relation type of the link
      - `type` string — The media type of the resource
      - `title` string — Title of the resource
      - `method` 'GET' | 'POST' — Specifies the HTTP method that the resource expects
      - `headers` object — Object key values pairs they map to headers
      - `body` object — For POST requests, the resource can specify the HTTP body as a JSON object.
      - `merge` boolean — This is only valid when the server is responding to POST request. If merge is true, the client is expected to merge the body value into the current request body before following the link. This avoids passing large post bodies back and forth when following links, particularly for navigating pages through the `POST /search` endpoint. NOTE: To support form encoding it is expected that a client be able to merge in the key value pairs specified as JSON `{"next": "token"}` will become `&next=token`.
    - `summaries` object — Summaries are either a unique set of all available values *or* statistics. Statistics by default only specify the range (minimum and maximum values), but can optionally be accompanied by additional statistical values. The range can specify the potential range of values, but it is recommended to be as precise as possible. The set of values must contain at least one element and it is strongly recommended to list all values. It is recommended to list as many properties as reasonable so that consumers get a full overview of the Collection. Properties that are covered by the Collection specification (e.g. `providers` and `license`) may not be repeated in the summaries.

## Other responses

- `500` — A server error occurred.

---

[API](https://skmtc.net/radiantearth/apis/stac-api.md) · [All operations](https://skmtc.net/radiantearth/apis/stac-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/radiantearth/stac-api/versions/11248209cf8c/schema)