Skip to content

OWS release 1.8.16
Compare
Choose a tag to compare
@SpacemanPaul SpacemanPaul released this 15 Aug 23:31
1.8.16
aeee428
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

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.
Assets 2
Loading