v0.3.10

Major loader refactor

There has been a significant change to the loader code. This change was needed to support hyper-spectral sources in odc-stac and datacube. Xarrays generated by the new loader can have extra dimensions beyond just time,y,x, for example for a visual band one might want to load data into an array with dimensions time,y,x,rgba.

Native zarr support

There is a new loader driver based around xarray.open_zarr(..), driver="zarr". You give it content of .zmetadata file and a url pointing to zarr root for each input dataset and it constructs Dask graph taking care of being properly "lazy". Note that with the use of kerchunk it's possible to construct "zarr spec" around hdf5 data on S3.

What's Changed (auto generated)

• Loading code refactor by @Kirill888 in #142
• Maintenance by @Kirill888 in #143
• populate uris in eo3 ds with stac url by @emmaai in #152
• Major rework or loader logic to support custom hyperspectral sources by @Kirill888 in #156
• fix: upgrade rtd build env by @Kirill888 in #157
• Update DaskReader Protocol by @Kirill888 in #158
• New loader by @Kirill888 in #160
• Release v0.3.10 by @Kirill888 in #161

New Contributors

• @emmaai made their first contribution in #152

Full Changelog: v0.3.9...v0.3.10

v0.3.9

What's Changed

• Use has_extension rather than deprecated validate_has_extension by @jsignell in #134
• Maintenance PR by @Kirill888 in #137
• Fixes for auto computation of output pixel grids by @Kirill888 in #141

New Contributors

• @jsignell made their first contribution in #134

Full Changelog: v0.3.8...v0.3.9

v0.3.8

What's Changed

This is mostly to fix regression in the previous version. Automatic computation of output geobox was broken for certain inputs #131.

• Update stac-load-e84-aws.py by @mehran66 in #129
• maint: S3 upload of notebooks no longer works by @Kirill888 in #130
• Maintenance release v0.3.8 by @Kirill888 in #132

New Contributors

• @mehran66 made their first contribution in #129

Full Changelog: v0.3.7...v0.3.8

v0.3.7

What's Changed

• Add support for "auto" chunks #123
• Implement chunking along "time" dimension #81
• More precise GeoBox for some data sources #125
  • consider pixel alignment of the GeoBox, not just CRS and resolution
  • useful when working tih data sources that align x=0,y=0 to pixel centers rather than pixel edges

Full Changelog: v0.3.6...v0.3.7

v0.3.6

What's Changed

This is mostly about better support for multi-band assets, also fixes some corner cases in STAC item interpretation.

• Fix minor typo. by @tylere in #108
• Routine fixes for CI by @Kirill888 in #109
• fix: multi band asset parsing of band index #107 by @Kirill888 in #111
• Expand raster data detection by @Kirill888 in #116
• fix: band resolution for multi-band assets by @Kirill888 in #118

New Contributors

• @tylere made their first contribution in #108

Full Changelog: v0.3.5...v0.3.6

v0.3.5

What's Changed

• fix: handle missing bands when constructing Dask graph by @Kirill888 in #103

Full Changelog: v0.3.4...v0.3.5

v0.3.4

What's Changed

• Add "continue on error" feature to odc.stac.load by @Kirill888 in #100
• Github actions maintenance
• Minor corrections to docs

Full Changelog: v0.3.3...v0.3.4

v0.3.3

What's Changed

• Fixes for xarray==2020.10.0, see #90 and #91

Full Changelog: v0.3.2...v0.3.3

v0.3.2

What's Changed

STAC Metadata Processing Changes

• Reworking metadata extraction from pystac in #80, #86

Removes various limitations that were present previously

• Can handle multi-band assets (can use asset_name.2 or common name to access those)
• Better handling of clashing common names (aka aliases)
• Handling of collections with irregular assets. No longer assume that first observed STAC item has all the possible assets/bands and instead build up collection description incrementally from observed items
• Handle STAC items that use older raster extension than version supported by currently installed pystac library

Support GCP data sources

Can read data from imagery using GCPs for registration. Starting from odc-geo>=0.3.0there is GCPGeoBox that offers same kind of functionality allowing for re-using the same data loading logic for both "transform" and "GCP" based data sources. On the output side only "transform"-based geoboxes are supported.

Other

• More robust handling of STAC items with geometries that do not project cleanly into epsg:4326 (#85)
• Make botocore an optional dependency by @gadomski in #76
• Fix GDAL/rasterio configuration capture and transfer to processing threads #82

Full Changelog: v0.3.1...v0.3.2

v0.3.1

What's Changed

• Use asset keys as canonical band names by @gadomski in #77

Full Changelog: v0.3.0...v0.3.1