0.20.0

Assembler Improvments

Custom product names
You can now set your own product_name to bypass the automatic name generation.

    with DatasetAssembler(out) as p:
        p.datetime = datetime(2019, 7, 4, 13, 7, 5)
        p.product_name = "loch_ness_sightings"
        ...

Multiple-platforms
Multiple platforms are now allowed to be stored as a list of comma-separated values.

(and a p.platforms convenience property exists for accessing it as a sequence.)

>>> # Set multiple platforms
>>> p.platforms == ["landsat-5", "landsat-7"]
>>> # Or (identically):
>>> p.platform = 'landsat-5,landsat-7'


>>> # Access them using either method:
>>> p.platforms
{"landsat-5", "landsat-7"}
>>> p.platform
'landsat-5,landsat-7'

They are normalised individually using our existing platform normalisation (lowercase etc), and maintained sorted automatically (so that comparison and matching between values is always stable).

Validator improvements

You can now run eo3-validate on directories and it will validate all ODC files inside.

Examples:

# Validate a folder of products:
eo3-validate /path/to/my-products

# Validate all datasets against a product
eo3-validate /some/product.yaml /tmp/all-my-datasets

# Validate everything found inside the current folder(s)
eo3-validate .

# Validate a dataset *thoroughly* (opening its image files to check they match)
eo3-validate --thorough /some/product.odc-product.yaml /some/dataset.odc-metadata.yaml

Other improvements to eo3-validate.

• Added warning for missing product license field (required for Stac and strongly encouraged now for ODC)
• Added warning for non-standard file suffixes (*.odc-product.yaml etc)
• Catch schema violations that will make the product fail to index into ODC.
• Fixed false warnings in product->dataset nodata comparison (when "thorough" is enabled).
• It now supports all ODC file types (datasets, products, metadata-types)

Product preparation

• Further improvements to S2 preparation in eo3-prepare