OWS Release 1.8.20

WCS enhancements, new docker image, bug fixes, and doc updates.

Please read the release notes before upgrading.

WCS changes

As more in the community are starting to actively use WCS, we are slowly polishing away the rough edges. This release has two changes of interest to OWS administrators who use WCS:

1. Firstly, the wcs default_bands has been removed. The default behaviour for WCS requests that do not specify bands is now to return all available bands, as specified in the WCS2 standards.

This means that layer-level "wcs" sections is no longer required. If you have any, you will get warning messages. You can ignore these until you are sure that all your server instances have been upgraded to 1.8.20, when it is safe to remove the layer wcs sections from your config to suppress the warning.

2 .Secondly, more options are available for resource limiting in WCS. Refer to the documentation for details:

https://datacube-ows.readthedocs.io/en/latest/cfg_layers.html#resource-limits-wcs

Docker image base change

The Docker images are now based on osgeo/gdal instead of opendatacube/geobase. You may need to tweak your build environment slightly - check your env files against the latest examples.

New in this release

• Switch docker base image from geobase to osgeo/gdal. (#727)
• Remove support for wcs default_bands entry (# 725)
• Extend resource management capabilities for WCS (#730)
• Fixed several corner-case bugs in the color ramp legend generator (#732)
• Add chapter on legend generation to HOWTO (#733, #735)
• Added Security.md file (#734)
• Other improved documentation (#711)
• Fix bug affecting layers with no extent mask function. (#737, #739)
• Increment default version number to 1.8.20 (#738)