Datacube-ows

Latest version: v1.9.0

Safety actively analyzes 723177 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 9

1.8.19

Not secure
-------------------

Improved test coverage and documentation; bug fixes; repo cleanup.

* Improved test coverage (708, 709, 710)
* Fixed zero-day bug in WMTS GetFeatureInfo (708)
* Improved pylint github action (thanks pindge). (713)
* Cleanup of requirements lists, and removal of old unused files. (714)
* Fix platform-dependent numpy.typing import issue (thanks alexgleith) (718)
* Fix two WCS query interpretation bugs (719)
* Documentation updates, including a cleanup of the README. (720)
* Add support for ows_stats performance diagnostic tool to WMTS and WCS. (721)
* Pin s3fs version in requirements.txt for compatibility with odc_tools (722, 724)
* Increment version number (723)

1.8.18

Not secure
are actively being worked on, see below for details.

Changes:
++++++++

* Cleanup/refactor of styles package: docstrings, type-hints, cleanup and improved test coverage (695)
* Change default behaviour of ``$AWS_NO_SIGN_REQUEST`` to match the standard default behaviour for boto3-based applications (696)
* Fix WCS queries against layers with a flag-band in the main product (699)
* Increment version number (700)

Backward Incompatibilities
++++++++++++++++++++++++++

1. 695 removed support for some legacy legend config formats that have been deprecated (and undocumented)
for over a year.
2. 696 changes the default behaviour if ``$AWS_NO_SIGN_REQUEST`` is not set. Previously the default behaviour
was unsigned requests, it is now signed requests. This was a necessary first-step to supporting dynamic
credentials for S3 access, and brings OWS into line with other software using boto3 for S3 access.

Known Issues
++++++++++++

1. There are still issues with WCS queries against layers with a flag-band in the main product. These will be
addressed in the next release and should not effect queries generated by the Terria Export function.
2. Dynamic credentialling for S3 access is still problematic. We have a PR almost ready to merge (697) but
it needs further testing.

1.8.17

Not secure
-------------------

Urgent bug-fix release to address a WCS bug.

This release also contains a couple of minor backwards compatibility issues, see below for details.

1.8.16

Not secure
-------------------

Mostly about implementing smarter resource limiting to make time-series animation production ready.

* Smarter resource limiting (686, 689, 690)
* docker-compose.yml fixes. (685)
* Fix typo in ``.env_ows_root`` (683)
* Remove "experimental" warning on time-series animations (691)
* Better error reporting of config error cases potentially caused by easy-to-make typos (692)
* Increment version number (693)

Note the following changes to configuration introduced in this release. Old configurations should continue to work,
with the backwards-incompatible exceptions noted below, however you may see warning messages on startup advising
which parts of your config are now deprecated and should be updated.

1. ``native_crs`` and ``native_resolution`` were previously part of the ``wcs`` configuration section of layers,
as they were previously only used for generating WCS metadata. They are now also used by the new
``min_zoom_level`` resource limit for WMS/WMTS, and have therefore moved out of the ``wcs`` section and into
the main layer config section. These entries will continue to be read from the old location with a
deprecation warning. If present in both locations, the values in the new locations take precedence, and
the deprecation warning will still be raised.
2. There is a new ``min_zoom_level`` configuration option, which should be considerably easier to set and
use than ``min_zoom_factor``, as well as being much smarter about how resource requirements for request
are estimated. ``min_zoom_factor`` is still supported, but will be deprecated in a future release.

Backwards Incompatibility Notes

I try to avoid backwards incompatible changes to config format, but some minor ones were unavoidable in this release:

1. Layers with no CRS and/or resolution defined in the ODC product metadata now ALWAYS require a native CRS and resolution to be defined in configuration. This was previously only the case if WCS was enabled for the layer.
2. The default resource_limiting behaviour for WMS/WMTS has changed from "min_zoom_factor = 300.0" to "no resource limits". Maintaining backwards compatibility would have resulted in confusing and inconsistent behaviour.

1.8.15

Not secure
and has increased CI test coverage to over 90%.

If you use docker-compose to orchestrate your configuration, you may need to make some changes to
your ``.env`` file after upgrading to this release. See the updated examples and the documentation for details.

Thanks to all contributors, especially whatnick for the prototype implementation of time-series animation,
and alexgleith for supplying much needed user-feedback on the CLI interfaces.

(* experimental) = produces a warning message when activated. The existing resource limit implementation is
not suitable for production deployment with time-series animations. I hope to address this in the next release.

* Support for time-series animation APNG output for WMS and WMTS. (656, 670, 678)
* User configurable WMS default time (676)
* Code cleanup, starting to systematically add type hints and docstrings. (660, 663, 664, 665, 671)
* CI enhancements (662, 672, 674)
* datacube-ows-update changes to error handling to improve UX for maintainers. (666, 679)
* Enhancements to config management in docker-compose. Note that if you use docker-compose, you may need to make some changes to your ``.env`` file. See the updated examples and the documentation for details. (681)
* Release housekeeping, including incrementing default version number (682)

1.8.14

Not secure
-------------------

* Default band names (as exposed by WCS) are now internationalisable (651)
* Extent polygon rendering now uses rasterio rasterize, removing the dependency on scikit-image (655)
* Calculating GeoTIFF statistics in WCS is now (globally) configurable (654)
* Return an empty response if data for any requested dates is not available (652)
* Bug fix - summary products (time_resolution not raw) were broken in areas close to 0 longitude. (e.g. Africa) (657)
* Increment default version number (658)

Page 6 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.