Releases: opendatacube/datacube-ows
OWS release 1.8.16
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.
native_crs
andnative_resolution
were previously part of thewcs
configuration section of layers, as they were previously only used for generating WCS metadata. They are now also used by the newmin_zoom_level
resource limit for WMS/WMTS, and have therefore moved out of thewcs
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.- There is a new
min_zoom_level
configuration option, which should be considerably easier to set and use thanmin_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:
- 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.
- 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.
OWS Release 1.8.15
1.8.15 introduces experimental* support for time-series animations from WMS/WMTS, in APNG format, 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)
OWS Release 1.8.14
- 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_resolition not raw) were broken in areas close to 0 longitude. (e.g. Africa) (#657)
- Increment default version number (#658)
OWS Release 1.8.13
Datacube OWS 1.8.12 release
Release 1.8.11
OWS release 1.8.10
Mostly a bugfix release.
- plot_image functions added to styling API (e.g. for use in notebooks). (#619)
- Pass
$AWS_S3_ENDPOINT
through from calling environment to docker. (#622) - Add dive for monitoring container size and contents (#626)
- Suppress confusing error messages when update_ranges is first run (#629)
- Bug fix (#620, #621,#623)
- Documentation corrections and enhancements. (#624,#625,#627,#630)
- Increment default version number to 1.8.10 (#631)
OWS Release 1.8.9
New features:
- Optional separation of metadata from configuration and internationalisation (#587, #608, #609).
- Docker containers now run on Python 3.8 (#592, #598, #599, #602, #603, #604, #605, #606, #610, #612, #614).
- Bulk processing capabilities in Styling API (#595).
- Ability to load json config from S3 (disabled by default - enable with environment variable). (#591, #601)
- Misc bug-fixes and documentation updates (#611, #616, #617)
Repository Maintenance and Administrivia:
- Reduce redundant processing in Github Actions (#594).
- Add license headers and code-of-conduct. Improve documentation to meet OSGeo project requirements (#593)
- Make
ows_cfg_example.py
(more) valid. (#600) - Increment version number (#618)
WARNING: Backwards incompatible change:
- The old
datacube-ows-cfg-parse
CLI tool has been replaced by thecheck
sub-command of the new, more general purposedatacube-ows-cfg
CLI tool.
OWS Release 1.8.8
Datacube OWS Release 1.8.7
*Includes support for user-defined band math (for colour ramp styles with matplotlib colour ramps). This is an experimental non-standard WMS extension that extends the WMS GetCapabilities document in the standard manner. The output validates against an XSD which is a valid extension of the WMS GetCapabilities schema. Backwards compatible extensions to GetMap allow the feature to be called by client software (#562, #563).
- If all goes to plan this will be the first OWS release automatically pushed to PyPI (#560, #568, #369, #570, #571, #572, #573, #574, #575, #576).
- Multi-product masking bug fix (#567). This was a serious bug affecting most multi-product masking use cases.
- Documentation updates (#561, #564)
- Version number increment to 1.8.7 (#577)