---
title: "Fetch a single collection asset"
method: GET
path: "/collections/{collectionId}/assets/{assetId}"
tags: ["Data"]
---

# Fetch a single collection asset

`GET /collections/{collectionId}/assets/{assetId}`

Fetch the collection asset with id `assetId` of the collection with id `collectionId`.

## Path parameters

- `collectionId` string, required
- `assetId` string, required

## Headers

- `If-Match` string
- `If-None-Match` string

## Response `200`

The response is a document consisting of one asset of the collection.

- CollectionAsset — The `property name` defines the ID of the Asset.
  - `id` string, required — The asset id uniquely identifies the asset for an item **Note**: `id` must be unique for the item and must be identical to the filename.
  - `type` string, required — Media type of the asset
  - `title` string — Displayed title
  - `description` string — 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.
  - `href` string, url — Link to the asset object. Details about asset object calls, specifically information about caching behavior can be found [here](#tag/Data/operation/getAssetObject)
  - `file:checksum` string — `sha2-256` checksum of the asset in [multihash](https://multiformats.io/multihash/) format.
  - `roles` string[] — Purposes of the asset
  - `geoadmin:variant` string
  - `geoadmin:lang` 'de' | 'it' | 'fr' | 'rm' | 'en'
  - `proj:epsg` integer — A Coordinate Reference System (CRS) is the data reference system (sometimes called a 'projection') used by the asset data, and can usually be referenced using an EPSG code. If the asset data does not have a CRS, such as in the case of non-rectified imagery with Ground Control Points, proj:epsg should be set to null. It should also be set to null if a CRS exists, but for which there is no valid EPSG code.
  - `gsd` number — GSD is the nominal Ground Sample Distance for the data, as measured in meters on the ground. There are many definitions of GSD. The value of this attribute should be related to the spatial resolution at the sensor, rather than the pixel size of images after ortho-rectification, pansharpening, or scaling. The GSD of a sensor can vary depending on off-nadir and wavelength, so it is at the discretion of the implementer to decide which value most accurately represents the GSD. For example, Landsat8 optical and short-wave IR bands are all 30 meters, but the panchromatic band is 15 meters. The gsd should be 30 meters in this case because that is nominal spatial resolution at the sensor. The Planet PlanetScope Ortho Tile Product has an gsd of 3.7 (or 4 if rounding), even though the pixel size of the images is 3.125. For example, one might choose for WorldView-2 the Multispectral 20° off-nadir value of 2.07 and for WorldView-3 the Multispectral 20° off-nadir value of 1.38.
  - `created` string, date-time, required — RFC 3339 compliant datetime string, time when the object was created
  - `updated` string, date-time, required — RFC 3339 compliant datetime string, time when the object was updated
  - `links` Link[], required
    - `href` string, url, required
    - `rel` string, required — Relationship between the current document and the linked document. NOTE: the following relations are reserved and automatically generated: `self`, `root`, `parent`, `items`, `collection`, `next`, `previous`
    - `title` string
    - `type` string — The media type of the link target
    - `method` 'GET' | 'POST' — Specifies the HTTP method that the link expects
    - `hreflang` string — The language of the link target

## Other responses

- `304` — The cached resource was not modified since last request.
- `404` — The specified resource/URI was not found
- `412` — Some condition specified by the request could not be met in the server
- `500` — The request was syntactically and semantically valid, but an error occurred while trying to act upon it

---

[API](https://skmtc.net/geoadmin/apis/the-spatiotemporal-asset-catalog-api-for-data-geo-admin-ch-4.md) · [All operations](https://skmtc.net/geoadmin/apis/the-spatiotemporal-asset-catalog-api-for-data-geo-admin-ch-4/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/geoadmin/the-spatiotemporal-asset-catalog-api-for-data-geo-admin-ch-4/revisions/11277d3dfca4/schema)