Datacube-ows

Latest version: v1.9.0

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

Scan your dependencies

Page 3 of 9

1.8.34

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

This OWS release includes two significant new features:

1. Timeless mosaic layers.

The new `mosaic_date_func` configuration option allows the creation of timeless (i.e. single time-slice)
layers. The user-provided function returns the start/end date to use for dataset date searches, and a
mosaic layer is generated, with the most recent available date for any given pixel returned.

2. Enhanced time resolution handling (subday and overlapping summary periods).

Major refactor of time resolution handling.

There are now only 3 time resolution options:

*solar:* Replaces the old "raw" option. Local-solar-day time model, used for imagery captured in daily swathes
by satellites in heliosynchronous orbits.

*summary:* Replaces the old "day", "month", and "year" options. Only looks at the "start" datetime, and
so neatly supports products with overlapping or non-exclusive dataset date-ranges. Expects the time portion
of the start date to always be "midnight UTC". Used for summary/calculated products.

*subday:* New option. Used for for products with multiple time values per day (e.g. hourly/minutely data). Uses
the "start" datetime of the dataset.

Note that the *solar* and *summary* options explicitly ignore the **time** component of the *time* query parameter
passed by the user. If you need the time component to be significant, you must use subday.

The old "raw", "day", "month", "year" time_resolution options are still supported as aliases for the new
values above. A deprecation warning will be issued advising you to update your configuration to the new
values, but the old values will continue to work. You should not actually move your configuration to
the new values until after all of your deployment environments have been upgraded v1.8.34.

Full list of changes:

* Increment default version number and update version history (937)
* Enhanced time resolution handling (subday and overlapping summary periods) (933, 936)
* Add spellcheck to RST documentation (929, 930)
* Implement timeless mosaic layers (928)
* Refactor integration tests to use new collection DEA data (927)
* Bump datacube-core version (923, 927, 933)
* Miscellaneous cleanup and code-maintenance (922)
* Pre-commit auto-updates (920, 926, 932, 934)

1.8.33

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

Full list of changes:

* Update to examples in documentation (912)
* Bug-fixes to WCS2 (913, 915)
* Pre-commit auto-updates (914, 917)
* Make compatible with numpy 1.24.0+ (918)
* Update default version number and HISTORY.rst (919)

1.8.32

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

Full list of changes:

* Add datacube pypi badge (891)
* Pre-commit auto-updates (894, 899, 906)
* Github action update (896)
* Documentation updates (898, 903, 904)
* WCS grid counts and add checks for sign errors in native resolution (902)
* Match docker image version numbers to github SCM version numbers (907, 908, 909)
* Update default version number and HISTORY.rst (910)

Contributions from pindge and SpacemanPaul (and of course, the pre-commit-ci bot).

1.8.31

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

Full list of changes:

* Added pre_scaled_norm_diff to band_utils.py, allowing calculation of normalised difference calculations on
data that is scaled with an offset. (881)
* Add support for url patching - allowing OWS to serve data from commercial data repositories that use
uri signing for authentication (e.g. Microsoft Planetary Computer) (883)
* Further refinements to Sentry logging. (884)
* Improve interoperability with Jupyter Notebooks. (886)
* Allow band alises for Flag Bands taken from main product(s). (887)
* Add new metadata type to MV definitions, to support DEA Sentinel-2 Collection 3. (888)
* Add support for html info_format for GetFeatureInfo queries in WMS and WMTS - may improve ArcGIS
compatibility. (889)
* Updates to HISTORY.rst, README.rst and default version string for release (890)

Contributions from pindge, rtaib and SpacemanPaul.

1.8.30

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

Minor release, consisting of better Sentry reporting for production deployments, and routine repository
maintenance.

Full list of changes:

* Update code-of-conduct.md to refer to current ODC Steering Council chair (862)
* Fixes to docker-compose files and github workflows (864, 866, )
* Simplify and cleanup scripts and config to create database for integration tests (865, 871)
* Change interpretation of Sentry environment variables to allow Sentry reporting to any hosted Sentry service (868, 877)
* Prevent mysterious Shapely warning message from clogging up Sentry logs (873)
* Minor tweaks to aid trouble-shooting and better support local deployments (878)
* Updates to HISTORY.rst, README.rst and default version string for release (879)

Contributions from pindge and SpacemanPaul.

1.8.29

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

This release includes support for heterogenous multi-product layers (single layers that combine data
from satellite platforms with different bands and native resolutions - e.g. Sentinel-2 plus Landsat),
an upgrade to the docker container (now based on Ubuntu 22.04, with Python 3.10), plus documentation updates
and bug fixes.

Full list of changes:

* Enhancements to support heterogenous multi-product layers (837, 841, 844)
* Refactor data for integration test fixtures (835)
* Docker image migrated to Python3.10/Ubuntu-22.040-based osgeo/gdal base image, and updates to
dependencies (838, 843, 852, 854, 856, 859)
* Isolate ops imports to minimise dependencies for applications only using the styling API (855)
* Documentation updates and improvements (846, 847, 848, 849)
* Bug Fix: Skip cached bounding boxes when layer extent is entirely outside the valid region for the CRS (832)
* Bug Fix: Invalid version parameters in otherwise valid requests were failing with unhandled 500 errors. OWS now
makes a best-effort guess in this case, tending towards the lowest supported version (850)
* Bug Fix: response_crs parameter was not being handled correctly by WCS1 (858)
* Updates to HISTORY.rst and default version string for release (860)

This release includes contributions from SpacemanPaul, and pindge.

Page 3 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.