Skip to main content

Download Your Images

To download data, you must have an active order for the respective area. If you did not increase the ApiRequests quota during the ordering process, you can only download the data once.

Composite Availability​

For new live data, it’s advisable to verify its availability before attempting to download it. This can be done with the available endpoint:

POST /api/satelliteimages/process/composite/available

Example Request Body:

{
    "Wkt": "string",
    "GeoJson": {
    "type": "string",
    "coordinates": null,
    "geometries": []
    },
    "Date": "2024-08-24T00:00:00Z",
    "UtmDataSelectionMode": "single_utm_fully_covered",
    "SatelliteConstellations": [
        "Sentinel1",
        "Sentinel2",
        "Landsat89"
    ],
    "Model": "Stratus2",
    "EpsgProjection": 0,
    "Bandnames": "string"
}

Example Request Response:

{
    "Succeeded": true,
    "Error": {
    "Message": "string",
    "Code": 0
    },
    "Data": {
        "IntersectedActiveZones": true,
        "IntersectedActiveZonesUtmEpsg": true,
        "FullyAvailable": true,
        "UncertaintyAvailable": true,
        "PartiallyAvailable": true,
        "PartiallyUncertaintyAvailable": true,
        "PolygonInDataArea": true,
        "DataAvailableForUser": true,
        "DataOnZoneDataFrequencyDate": true,
        "AllImagesPredicted": true,
        "AnyImageWithinStorageMonths": true,
        "OrdersCoverPolygon": true
    }
}
tip

This availability endpoint can be useful when making a fully automatic data acquisition flow, to ensure all data has been produced before attempting to download it.

Download Cloudless Data​

To download data that has been ordered, the composite endpoint can be used to retrieve custom, complex geometries. If you have ordered minitiles or tiles, you can alternatively acquire the data as tiles.

POST /api.clearsky.vision/api/satelliteimages/process/composite

The below example downloads a complex WKT polygon in full resolution as an INT16 GeoTIFF (.tif). This download is performed in a UTM projection and uses parameters specific to UTM data acquisition (i.e. UtmDataSelectionMode and UtmGridForcePixelResolutionSize).

Example Request Payload:

{
    "Wkt": "POLYGON ((9.877893206725581 56.47856668238974, 10.196496722350581 56.47856668238974, 10.196496722350581 56.27782087776097, 9.877893206725581 56.27782087776097, 9.877893206725581 56.47856668238974))",
    "GeoJson": {
        "type": "Polygon",
        "coordinates": []
    },
    "Date": "2024-05-03T00:00:00Z",
    "Resolution": 10,
    "EpsgProjection": 32632,
    "FileType": "tif",
    "PixelSelectionMode": "contained",
    "DataType": "INT16",
    "UtmDataSelectionMode": "combined_utm",
    "SatelliteConstellations": [
        "Sentinel1",
        "Sentinel2",
        "Landsat89"
    ],
    "Model": "Stratus2",
    "UtmGridForcePixelResolutionSize": true,
    "Bandnames": "all"
}

The PixelSelectionMode parameter determines whether we return pixels that are fully contained within the geometry or just pixels that intersects with the geometry. The EpsgProjection parameter specifies the desired EPSG projection. It's adviseable to download in an UTM EPSG (eg. 326XX or 327XX) for maximum data quality. Read more about possible parameters and their definitions at api.clearsky.vision.

tip

You can without additional cost ask for an index to be computed, such as NDVI or NDRE. For now, it only supports (Band1 - Band2) / (Band1 + Band2) formula indices. As an example, writing [B8_B4] in the Bandname parameter will retrieve NDVI.