Skip to main content

ARD Order Output Files

The output of an ARD order is a time-series stack of tiles and their accompanying metadata. The files are:

  • A single-band panchromatic GeoTIFF.
  • A 4 or 8-band multispectral GeoTIFF.
  • A 3-band RGB GeoTIFF. We refer to this file as a "visual" tile.
  • A set of data masks delivered individually in both raster GeoTIFF and vector GeoPackage formats. Individual masks can be excluded from the delivery as part of the order requests.
  • A set of STAC-compliant metadata files that describe the contents of the order delivery.

Delivery file directory structure

ARD orders are delivered in the following directory structure:

📁 {bucket or container}
└── 📁 {prefix (optional)}
└── 📁 acquisition_collections
└─╴📄 {acquisitionID}_collection.json
└── 📁 order_collections
└─╴📄 {orderID}_root_collection.json
└── 📁 {UTM-zone}
└── 📁 {quadkey}
└── 📁 {acquisition-date}
└─╴📄 (files)
└── 📄 {orderID}-request.json
  • There can be multiple prefixes in the path.
  • The UTM zone and quadkey indicate where the tile is located on the grid.
  • The acquisition date is the month, day, and year the image was acquired by the satellite. In a list view, the acquisition-date folders are arranged from oldest to most recent. The image files and accompanying data are stored in the acquisition date folder.

Non-intersecting tiles report

Most orders will not include a non-intersecting tiles report file.

The imagery selection and order validation steps use an estimated image footprint, based on metadata. The estimated footprint and the actual footprint can be slightly different. Most of the time, the difference doesn't impact the ordering process.

Occasionally, when only the edge of the estimated footprint intersects with the AOI, the shift is enough that the actual footprint does not intersect. In this scenario, the imagery would pass select and order validation, but the non-intersecting tile or tiles cannot be ordered. When this occurs, the intersecting image tiles in the order are delivered, and a report is generated that lists the non-intersecting tiles that could not be delivered.

The report is named {orderID}_non_intersecting_tiles_report.json .

It is located in the order_collections subdirectory.

📁 {bucket or container}
└── 📁 {prefix}
└── 📁 acquisition_collections
└─╴📄 {acquisition ID}_collection.json
└─╴ 📁 order_collections
└─╴📄 {orderID}_root_collection.json
└─╴📄 {orderID}_non_intersecting_tiles_report.json

Image files

There are three raster image files for each tile in a delivery. These are Cloud-Optimized GeoTIFFs, or "COGs".

Image fileDescriptionFilename
multispectral imageA 4 or 8-band multispectral image in GeoTIFF format.{acquisitionID}-ms.tif
panchromatic imageA single-band panchromatic image in GeoTIFF format.{acquisitionID}-pan.tif
visual (RGB) imageA 3-band RGB image in GeoTIFF format.{acquisitionID}-visual.tif

See ARD Technical Overview for more information about ARD image tiles and additional pre-processing steps.

Data Masks

ARD order deliveries include a set of data masks for each tile. A raster GeoTIFF (.tif) and a vector GeoPackage (.gpkg) file are delivered for most masks. There are two exceptions:

  • Clouds and cloud shadows are both captured in a single raster mask called the "cloud/cloud shadow coverage raster". Cloud and cloud shadows have individual vector files, named "cloud polygons" and "cloud shadow polygons".
  • The "data mask" is derived from the raster image and is delivered only as a vectorized GeoPackage.
MaskDescriptionFile typeFilename
Cloud/Cloud Shadow Coverage RasterIdentifies clouds and cloud shadow pixels.raster{acquisitionID}-clouds.tif
Cloud PolygonsTraces the boundaries of identified cloud polygons.vector{acquisitionID}-cloud-mask.gpkg
Cloud Shadow PolygonsTraces the boundaries of identified cloud shadows.vector{acquisitionID}-cloud-shadow-mask.gpkg
Data MaskIdentifies all pixels classified as "data" in the raster image and vectorizes those pixels as a GeoPackage. Pixels are either classified as "data" or "no data".vector{acquisitionID}-data-mask.gpkg
Healthy Vegetation MaskBinary raster indicating green, healthy vegetation pixels.raster{acquisitionID}-healthy-vegetation.tif
Healthy Vegetation PolygonsPolygons that indicate the detected boundaries of green, healthy vegetation.vector{acquisitionID}-healthy-vegetation-mask.gpkg
MS Pixel Saturation MaskIdentifies saturated pixels in a 4 or 8-band multispectral image.raster{acquisitionID}-ms-saturation.tif
MS Pixel Saturation PolygonsTraces the boundaries of identified saturated pixels in a multispectral image.vector{acquisitionID}-ms-saturation-mask.gpkg
Pan Flare MaskDetected flared pixels from a panchromatic image.raster{acquisitionID}-pan-flare.tif
Pan Flare PolygonsTraces the boundaries of detected flare pixels from a panchromatic image.vector{acquisitionID}-pan-flare-mask.gpkg
Terrain shadows maskIdentifies terrain shadow pixels.raster{acquisitionID}-terrain-shadows.tif
Terrain Shadows PolygonTraces the boundaries of detected terrain shadows.vector{acquisitionID}-terrain-shadow-mask.gpkg
Water MaskDetects pixels for bodies of water and swimming pools.raster{acquisitionID}-water.tif
Water PolygonsTraces the boundaries of bodies of water and swimming pools.vector{acquisitionID}-water-mask.gpkg

Metadata files

An ARD order delivery includes additional files with information about the order and its contents. The metadata files adhere to the Spatio-temporal Asset Catalog (STAC) specifications.

FileDescriptionFile typeFilename
STAC Item Metadata FileThe STAC item file that describes the ARD assets.JSON{acquisitionID}.json
Order STAC Collection fileDescribes the contents of the order delivery.JSON/order_collections/{orderID}_root_collection.json
Acquisition STAC collection fileDescribes the acquisitions in the order delivery.JSON/acquisition_collections/{acquisitionID}_collection.json
Order request fileShows the JSON body of the order request.JSON/{orderID}-request.json