opendatacube / odc-tools

ODC features that DEA is experimenting with or prototyping with the intention of being integrated into odc-core in the future

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

s3-to-dc fails due to lineage

GeoFelpave opened this issue · comments

When using:

s3-to-dc --stac 's3://bucket-name/folder-name/**/*.json ' 'produc_name'

The indexing process gives the error below

odc.apps.dc_tools.utils.IndexingException: Failed to create dataset with error Error loading lineage dataset: Dataset metadata did not match product signature.
Dataset definition:
 {}
Product signature:
 {
    "product": {
        "name": "rainfall_chirps_daily"
    }
}, 

The --help is showing that Default is not to skip lineage, so is expected to be empty, so no lineage to match. The expected behaviour is not taken place.

The work around is to use the flag --skip-lineage.

Thanks

Hi @GeoFelpave,
This error message is perhaps a little misleading. Dataset definition: {} does not mean that the dataset lineage is empty, only that there was no overlap between its contents and the product signature. Are you able to double check and see if the files in your s3 bucket indeed have lineage: {}?

This has now been solved under the latest version. As per @Ariana-B the lineage was checked and the dataset did not have lineage, the default behaviour of dc should be not to check per lineage as per documentation, which has been corrected