OWS Release 1.8.26

Optimisation release.

Includes significant performance improvements to the colour-map style rendering algorithm. For large, complex value_map rule sets the improvement is dramatic (e.g. for DEA LCCS level4 style, which contains over 100 rules, rendering speed is increased by 70-80%).

• Minor improvements to unit and docker testing (#792, #793)
• Optimisation of colour-map style rendering algorithm (#795)
• Increment default version number and update HISTORY.rst (#797)

OWS Release 1.8.25

Bug fix release.

The legend internationalisation code in 1.8.24 caused errors in manual legends for deployments that do not have internationalisation enabled. This release fixes that issue.

• Legend internationalisation bug fix (#789, #790)
• Update default version number and HISTORY.rst (#791)

OWS Release 1.8.24

Introduces support for internationalisation (translation) of style legends - see the documentation for details:

https://datacube-ows.readthedocs.io/en/latest/configuration.html#metadata-separation-and-internationalisation
https://datacube-ows.readthedocs.io/en/latest/cfg_styling.html#url

This is the first formal release since the 9th December, although there were several interim releases in mid-December when we were testing the Prometheus metric changes (see below).

Due to an oversight in deprecation warnings several releases ago, some configurations that worked in 1.8.23 will now raise errors. Affected configurations have legacy "legend" hints embedded inside the colour ramp definitions. Such hints have not been read by OWS for quite some time, having been replaced by the "tick_labels" entry in the "legend" section. Digital Earth Australia and Digital Earth Africa configurations have already been updated.

Changes since 1.8.23:

• Prometheus metric enhancements and release notes for interim releases (#777, #778, #779, #780, #781, #782)
• Github integration tests against a large real world OWS configuration (DEA) (#784)
• Internationalisation of style legends. (#783, #786)
• Fix WCS1 DescribeCoverage regression (missing SRS/CRS) (#787)
• Update History.RST and increment default version number (#788)

OWS 1.8.23.3 Interim Release

Interim administrative release.

• Upgraded Prometheus metrics to histogram type, and updated HISTORY.rst (#781)

OWS 1.8.23.2 Interim Release

Interim administrative release.

• Improved Prometheus metrics for monitoring (#779)
• Update HISTORY.rst (#780)

OWS 1.8.23.1 Iterim Release

Interim administrative release.

• Improved Prometheus metrics for monitoring (#777)
• Update HISTORY.rst (#778)

OWS Release 1.8.23

In addition to the standard animated handlers previously supported by all style types, this release introduces two additional approaches to produce an non-animated image from a multi-date request for colour-map (aka value_map) type styles:

1. Using a variant of the value_map_ entry used for the single-date case. This is a much simpler way of achieving most use cases.
2. Using an aggregator function, which allows for fully customisable behaviour but requires writing Python code.

The new behaviour is fully documented here: https://datacube-ows.readthedocs.io/en/latest/cfg_colourmap_styles.html#multi-date-requests

This means that OWS now supports rich comparison visualisation techniques for both contiguous and discrete data products.

Also, the masking rule parser for pq_masks sections now uses the same code as the parser for value_map rules in colour map styles.

This means that:

1. pq_mask rules now supports and/or operators, consistent with value_map rules.
2. value_map rules now support the invert operator, consistent with pq_mask rules.
3. The old "enum" keyword in pq_masks is now deprecated - please now use the values keyword, as in value_maps.

Full details are in the documentation. Old style syntax will continue to work as before - except the enum keyword in pq_masks now produces a deprecated warning message.

Changes in this release:

New Feature:

• Support for non-animated multi-date handlers for "colour-map" type styles. (#770)
• Consistent syntax for masking rules in pq_masks and value_map rules (#774)

Bug fixes

• Fix to bug affecting resource-limiting for WCS (#769)
• Fix bug in handling of missing data when applying cross-product masking (#772)

Dependency management and release process

• Remove constraint requiring very recent versions of numpy (#766)
• Upgrade to Postgis 3.1 (#767)
• Add automated spell check of documentation to github actions (#775)
• Increment default version number. (#776)

This release includes contributions from @Kirill888, @NikitaGandhi, @pindge and @SpacemanPaul

OWS Release 1.8.22

OWS Release 1.8.22 includes a change to the config manifest json format used by datacube-ows-cfg. System maintainers who use the datacube-ows-cfg -i/-o flags to validate config integrity will need to regenerate their reference manifests.

• Raise error on duplicate layer names. (#759)
• Add layer name to config manifest file format (#759)
• Apply configured http headers to WCS2 GetCoverage responses (#761)
• Remove and replace tests based on S3FS, removing test dependency on aiobotocore (#762)
• Prevent non-S3 urls from being followed by config inclusion (#762)
• Documentation updates (#758)
• Increment default version number and revive HISTORY.rst (#763)

OWS Releases 1.8.21

• Allow layers with no extent_mask_function (#739)
• Eliminate redundant connection pool - use datacube-core connection pool directly (#740)
• Remove requirements.txt Use setup.py exclusively for dependency management. (#741, #744)
• Improve docker image efficiency (#743, #745, #746)
• Fix WCS1 bug affecting requests with no explicit measurements or style (#749)
• Add $AWS_S3_ENDPOINT to environment variable documentation (#751)
• Improve Prometheus metrics (#752)
• Fix function config internal over-writing issue - was causing issues for odc-stats (#754)
• Increment default version number and switch setuptools_scm to post-release version numbering (#753)

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)