Dataset Preparation Scripts

Sometimes data to load into an Open Data Cube will come packaged with compatible Dataset Documents and be ready to index immediately.

In other cases you will need to generate these Dataset Documents yourself. This is done using a Dataset Preparation Script, which reads whatever format metadata has been supplied with the data, and either writes out ODC compatible files, or adds records directly to an ODC database.

For common distribution formats there is likely to be a script already, but other formats will require one to be modified.

Examples of prepare scripts are found in the datacube-dataset-config repository on Github.

The two examples below show preparing USGS Landsat data for indexing into an Open Data Cube:

1. Preparing USGS Landsat Collection 1 - LEVEL1

Download the USGS Collection 1 landsat scenes from any of the links below:

The prepare script for collection 1 - level 1 data is available in

$ wget
$ python --help

    Prepare USGS Landsat Collection 1 data for ingestion into the Data Cube.
    This prepare script supports only for MTL.txt metadata file
    To Set the Path for referring the datasets -
    Download the  Landsat scene data from Earth Explorer or GloVis into
    'some_space_available_folder' and unpack the file.
    For example: --output [Yaml- which writes datasets into this file for indexing]
    [Path for dataset as : /home/some_space_available_folder/]

    --output PATH  Write datasets into this file
    --help         Show this message and exit.

$ python --output ls8_usgs_lv1 ~/earth_explorer/Collection1/LANDSAT8

ls8_usgs_lv1 is the output for required dataset for landsat 8 scene.

To add the product definitions:

For Landsat collection 1 level 1 product:

$ datacube product add docs/config_samples/dataset_types/ls_usgs.yaml
Added "ls8_level1_usgs"
Added "ls7_level1_usgs"
Added "ls5_level1_usgs"
Added "ls8_l1_pc_usgs"

2. Preparing USGS Landsat Surface Reflectance - LEDAPS

To prepare downloaded USGS LEDAPS Landsat scenes for use with the Data Cube, use the script provided in

The following example generates the required Dataset Metadata files, named agdc-metadata.yaml for three landsat scenes.

$ wget
$ python USGS_precollection_oldscripts/ --help

  Prepare USGS LS dataset for ingestion into the Data Cube.

  --help  Show this message and exit.

$ python ~/USGS_LandsatLEDAPS/*/
2016-06-09 15:32:51,641 INFO Processing ~/USGS_LandsatLEDAPS/LC80960852015365-SC20160211222236
2016-06-09 15:32:52,096 INFO Writing ~/USGS_LandsatLEDAPS/LC80960852015365-SC20160211222236/agdc-metadata.yaml
2016-06-09 15:32:52,119 INFO Processing ~/USGS_LandsatLEDAPS/LE70960852016024-SC20160211221824
2016-06-09 15:32:52,137 INFO Writing ~/USGS_LandsatLEDAPS/LE70960852016024-SC20160211221824/agdc-metadata.yaml
2016-06-09 15:32:52,151 INFO Processing ~/USGS_LandsatLEDAPS/LT50960852011290-SC20160211221617
2016-06-09 15:32:52,157 INFO Writing ~/USGS_LandsatLEDAPS/LT50960852011290-SC20160211221617/agdc-metadata.yaml

The scenes are now ready to be indexed and accessed using the Data Cube.

For Landsat Surface reflectance LEDAPS add:

$ datacube product add docs/config_samples/dataset_types/*
Added "ls5_ledaps_scene"
Added "ls7_ledaps_scene"
Added "ls8_ledaps_scene"

Then index the data.

3. Prepare script and indexing Landsat data on AWS

Landsat 8 data is available to use directly from Amazon S3 without needing to download any scenes in advance.

Landsat on AWS stores each band of each Landsat scene in separate GeoTIFF files and the scenes metadata in a side-care text file.

About the data:




GIS, Sensor Data, Satellite Imagery, Natural Resource


GeoTIFF, txt, jpg

Storage Service

Amazon S3


s3://landsat-pds in US West (Oregon) Region

Update Frequency

New Landsat 8 scenes are added regularly as soon as they are available

Each scene’s directory includes:

  • a .TIF GeoTIFF for each of the scene’s up to 12 bands (note that the GeoTIFFs include 512x512 internal tiling)

  • .TIF.ovr overview file for each .TIF (useful in GDAL based applications)

  • a _MTL.txt metadata file

  • a small rgb preview jpeg, 3 percent of the original size

  • a larger rgb preview jpeg, 15 percent of the original size

  • an index.html file that can be viewed in a browser to see the RGB preview and links to the GeoTIFFs and metadata files

Accessing data on AWS

The data are organized using a directory structure based on each scene’s path and row. For instance, the files for Landsat scene LC08_L1TP_139045_20170304_20170316_01_T1 are available in the following location:


> The c1 refers to Collection 1, the L8 refers to Landsat 8, 139 refers to the scene’s path, 045 refers to the scene’s row, and the final directory matches the product’s identifier, which uses the following naming convention: LXSS_LLLL_PPPRRR_YYYYMMDD_yyymmdd_CC_TX, in which:

L = Landsat
X = Sensor
SS = Satellite
PPP = WRS path
RRR = WRS row
YYYYMMDD = Acquisition date
yyyymmdd = Processing date
CC = Collection number
TX = Collection category
In this case, the scene corresponds to WRS path 139, WRS row 045, and was taken on March 4th, 2017.The full scene list is available here.

Instead of downloading scenes, use the to scrape and record metadata into an ODC Database.

Usage of the script:

$ wget
$ python --help

   Enter Bucket name. Optional to enter configuration file to access a
   different database

   -c, --config PATH  Pass the configuration file to access the database
   -p TEXT            Pass the prefix of the object to the bucket
   --help             Show this message and exit.

$ python landsat-pds -p c1/139/045/`

where landsat-pds is the amazon public bucket name, c1 refers to collection 1 and the numbers after represents the WRS path and row.

Index any path and row by changing the prefix in the above command

Before indexing:

  1. You will need an AWS account and configure AWS credentials to access the data on S3 bucket

    For more detailed information refer to the Working with AWS Credentials Documentation.

Listing 1 Example ~/.aws/credentials file
     aws_access_key_id = <Access key ID>
     aws_secret_access_key = <Secret access key>
  1. Add the product definition to datacube

    Sample product definition for LANDSAT_8 Colletcion 1 Level1 data is available at docs/config_samples/dataset_types/ls_sample_product.yaml

    $ datacube product add ls_sample_product.yaml
      Added "ls8_level1_scene"

Custom Prepare Scripts

We expect that many new Data Cube instances will require custom prepare scripts to be written. It is generally a straightforward task of mapping metadata from one form to another and writing out a YAML document. The code need not even be written in Python, although starting with one of our examples is generally the easiest way.