Releases: opendatacube/datacube-ows
OWS Release 1.8.8
Datacube OWS Release 1.8.7
*Includes support for user-defined band math (for colour ramp styles with matplotlib colour ramps). This is an experimental non-standard WMS extension that extends the WMS GetCapabilities document in the standard manner. The output validates against an XSD which is a valid extension of the WMS GetCapabilities schema. Backwards compatible extensions to GetMap allow the feature to be called by client software (#562, #563).
- If all goes to plan this will be the first OWS release automatically pushed to PyPI (#560, #568, #369, #570, #571, #572, #573, #574, #575, #576).
- Multi-product masking bug fix (#567). This was a serious bug affecting most multi-product masking use cases.
- Documentation updates (#561, #564)
- Version number increment to 1.8.7 (#577)
OWS Release 1.8.6
OWS Release 1.8.5
OWS 1.8.4 release March 2021
OWS 1.8.3 release March 2021
Config enhancement and bug fixes
- Config inheritance for layers and styles.
- CRS aliases
- Enhanced band util functions.
- Query stats parameter.
- Stand-alone config parsing/validating tool.
- Cleaner internal APIs, improved test coverage, and bug fixes.
Bug fixes and performance enhancements
- Bug fixes
- Performance enhancements - most notable using materialised views for spatio-temporal DB searches.
- Improved testing and documentation.
1.8.0 release
- now bases off
odc 1.8.x
- supports for
wcs2.0
- update_ranges changes (see below)
Update_ranges.py now uses the spatio-temporal materialised views proposed for odc 2.0.
You will need to run update_ranges.py --schema --role myrole
once after upgrading to create the materialised views.
Thereafter the materialised views can be periodically refreshed with update_ranges.py --views
.
The --product, --all and --multiproduct options are now deprecated - you simply need to list the OWS layers that you wish to update. (ODC product names can also be used).
The default refresh mode is a non-blocking/concurrent refresh. - i.e. the refresh is calculated in the background and takes effect when complete, with the pre-refresh data readable in the mean time. Therefore to update the OWS ranges for layer "mylayer" with a guarantee to have the latest available data it would be necessary to run:
update_ranges.py --views --blocking
update_ranges.py mylayer
Running --views without the --blocking flag would mean that the update of mylayer could use old data as the refresh could still be running in the background.
Fix for https://github.com/opendatacube/datacube-ows/issues/258
Merge pull request #259 from opendatacube/release-action Try github.event_name