1.8.0 release

• now bases off odc 1.8.x
• supports for wcs2.0
• update_ranges changes (see below)

Update_ranges.py now uses the spatio-temporal materialised views proposed for odc 2.0.

You will need to run update_ranges.py --schema --role myrole once after upgrading to create the materialised views.

Thereafter the materialised views can be periodically refreshed with update_ranges.py --views.

The --product, --all and --multiproduct options are now deprecated - you simply need to list the OWS layers that you wish to update. (ODC product names can also be used).

The default refresh mode is a non-blocking/concurrent refresh. - i.e. the refresh is calculated in the background and takes effect when complete, with the pre-refresh data readable in the mean time. Therefore to update the OWS ranges for layer "mylayer" with a guarantee to have the latest available data it would be necessary to run:

update_ranges.py --views --blocking
update_ranges.py mylayer

Running --views without the --blocking flag would mean that the update of mylayer could use old data as the refresh could still be running in the background.