Skip to content

Releases: opendatacube/datacube-ows

OWS Release 1.8.9

03 Jun 06:00
f211246
Compare
Choose a tag to compare

New features:

  • Optional separation of metadata from configuration and internationalisation (#587, #608, #609).
  • Docker containers now run on Python 3.8 (#592, #598, #599, #602, #603, #604, #605, #606, #610, #612, #614).
  • Bulk processing capabilities in Styling API (#595).
  • Ability to load json config from S3 (disabled by default - enable with environment variable). (#591, #601)
  • Misc bug-fixes and documentation updates (#611, #616, #617)

Repository Maintenance and Administrivia:

  • Reduce redundant processing in Github Actions (#594).
  • Add license headers and code-of-conduct. Improve documentation to meet OSGeo project requirements (#593)
  • Make ows_cfg_example.py (more) valid. (#600)
  • Increment version number (#618)

WARNING: Backwards incompatible change:

  • The old datacube-ows-cfg-parse CLI tool has been replaced by the check sub-command of the new, more general purpose datacube-ows-cfg CLI tool.

OWS Release 1.8.8

04 May 00:54
e675148
Compare
Choose a tag to compare

New Features:

  • Multidate ordering (#580)
  • New "day_summary" time_resolution type, for data with summary-style time coordinates (as opposed to local solar-date style time coordinates). (#584)

Bug Fixes and Administrivia:

  • More thorough testing of styling engine (#578)
  • Bug fixes (#579, #583)
  • Upgrade pydevd version for debugging against Pycharm 2021.1.1 (#581)
  • Repository security issue mediation (Codecov security breach) (#585)
  • Increment version number (#586)

Datacube OWS Release 1.8.7

20 Apr 06:02
7ff8843
Compare
Choose a tag to compare

*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

08 Apr 05:26
69779a0
Compare
Choose a tag to compare

OWS Release 1.8.5

25 Mar 23:13
a46939f
Compare
Choose a tag to compare
  • Date delta can now control subtraction direction from config (#535)
  • New helper functions in standalone API (#538)
  • Bug fixes in standalone API. (#542, #543)
  • First draft of new "HOWTO" Styling guide. (#540, #543)
  • Miscellaneous cleanup. (#533, #534, #537, #541)
  • Prep for PyPI (#544)

OWS 1.8.4 release March 2021

19 Mar 02:24
ca984e8
Compare
Choose a tag to compare
  • Standalone API for OWS styling. (#523)
  • Support for enumeration type bands in colour-map styles. (#529)
  • Numerous bugfixes.
  • Updated documentation.

OWS 1.8.3 release March 2021

11 Mar 23:18
fb2cf24
Compare
Choose a tag to compare
  • Generalised handling of WMTS tile matrix sets (#452)
  • Progressive cache control headers (#476)
  • Support for multi-product masking flags. (#499)
  • Greatly improved test coverage (various)
  • Many bug-fixes, documentation updates and minor enhancements (various)

Config enhancement and bug fixes

26 Oct 04:35
4cb7493
Compare
Choose a tag to compare
  • 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

18 Aug 05:16
87de187
Compare
Choose a tag to compare
  1. Bug fixes
  2. Performance enhancements - most notable using materialised views for spatio-temporal DB searches.
  3. Improved testing and documentation.

1.8.0 release

10 Jun 03:45
Compare
Choose a tag to compare
  • 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.