Datacube-ows

-------------------

This release introduces changes to both the materialised view definitions and the ``datacube-ows-update``
utility to improve the accuracy and reliability of these extents, as well as bug fixes for
externally-hosted legend images.

This release includes:

* A bug fix to the OWS code which reads from the materialised views, preventing runtime errors
from occurring in scenarios where accurate extent information is not available (825)
* Enhancements to the materialised view definitions to support extracting extent polygons
from various optional metadata locations in both EO and EO3 based products. (826)
* Sanity-check and sanitise bounding box ranges for global datasets. It should now be
possible to use datasets with bounding box ``(-180, -90, 180, 90, crs=EPSG:4326)`` in
OWS. Previously this required hacking the metadata to result in e.g.
``(-179.9999, -89.9999, 179.999, 89.999, crs=EPSG:4326)`` (828)
* Usability improvements for external legends. Clearer reporting of read errors on external
urls, and raise warning instead of failing if external image format is not PNG. (829)
* Update HISTORY.rst and default version number (830)

Upgrade notes:
++++++++++++++

To enjoy all the advantages of these extent handling enhancements you will need to
run the following command, using a database role capable of altering the schema::

datacube-ows-update --schema --role role_to_grant_access_to

After regenerating the schema, the range tables should also be updated::

datacube-ows-update

(Note that there is no need to run ``datacube-ows-update`` with the ``--views`` option in between these
two steps.)

-------------------

Several bugfixes, and documentation updates and we had to change our CI test data because the old USGS Landsat PDS went user-pays.

Cache-control hints can now be configured for the XML requests (GetCapabilities, DescribeCoverage). WMS and WCS GetCapabilities can be configured separately. WCS DescribeCoverage can be configured globally and optionally over-ridden per layer/coverage. Refer to the documentation for details.

-------------------

Optimisation release. Performance improvements to colour-map style rendering algorithm.
For large, complex value_map rule sets the improvement is dramatic (e.g. 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)

-------------------
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)

-------------------

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.

---------------------

Interim administrative release.

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