Releases: opendatacube/eo-datasets
0.28.1
Full Changelog: eodatasets3-0.28.0...eodatasets3-0.28.1
0.28
- Allow products+types to customise validation by @jeremyh in #246
- Fix custom ODC config, while allowing it to be optional by @jeremyh in #247
- Add support for accessory files hosted on s3. by @tebadi in #239
- Expand docs for validator (eg. per-product config) by @jeremyh in #249
- Do subfolder calculation after expanding folders by @jeremyh in #250
New Contributors
Full Changelog: eodatasets3-0.27.5...eodatasets3-0.28.0
0.27.5
0.27.4
0.27.3
0.27.2
0.27.1
Minor release.
- S2 cloudless support in wagl by @uchchwhash in #237
- Run pre-commit updates by @jeremyh in #238
Full Changelog: eodatasets3-0.27.0...eodatasets3-0.27.1
0.27
0.26.1
0.26
Field validation
eo3-validate
can already validate your products and datasets together, but it didn't previously look at the configured metadata fields. Misconfigured fields are a common error in seen in ODC instances.
It now checks fields and warns when they don't match:
❯ eo3-validate eo3_sentinel_ard.odc-type.yaml \
products/ard_s2b*.odc-product.yaml \
products/examples/ga_s2b*.yaml
✓ eo3_sentinel_ard.odc-type.yaml
✓ products/ard_s2b.odc-product.yaml
✓ products/ard_s2b_provisional.odc-product.yaml
✓ products/examples/ga_s2bm_ard_3-2-1_55HFB_2018-12-01_final.odc-metadata.yaml
W missing_field Dataset is missing field 'eo_sun_elevation'
(Hint: Expected at properties->eo:sun_elevationn)
valid: 1 warning
"Thorough" validation now supports embedded URIs
eo3-validate --thorough datasets/
The --thorough
flag on eo3-validate
tells it to read all imagery files and check that they match the metadata (paths, data types etc).
This option now supports embedded locations, so that imagery stored in separate locations (eg. s3://
), or inside packages (eg. tar://
) can be --thorough
-ly validated.
S2 ARD packaging improvements
OA and Contiguity resolution can now be specified separately in eo3-package-wagl
:
--oa-resolution FLOAT Resolution choice for observation attributes
(default: automatic based on sensor)
--contiguity-resolution FLOAT Resolution choice for contiguity (default:
automatic based on sensor)
OA data is now packaged at 20m resolution by default instead of 10m for S2. The previous higher resolution significantly increased package size for data that is rarely used.
This new default matches DEA's packaging.
Contiguity bands will still default to the higher 10m resolution.