Changes to materialised view definition to prevent errors on databases with WKT CRSs #1037
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in #1002, creation of OWS materialised views fails on indexes that contain datasets with WKT-format CRSs, even if the datasets in question belong to products not included in the OWS config.
This PR explicitly excludes non-EPSG CRS datasets from the materialised view. This means that such datasets can NEVER be returned by OWS, but it will at least be able to possible to use OWS for other products in the same index.
Viewing non-EPSG CRS datasets will be possible in 1.9.0, with the new postgis ODC driver.
This (and other CRS-related) limitations of 1.8/postgres OWS are now documented in the README.
📚 Documentation preview 📚: https://datacube-ows--1037.org.readthedocs.build/en/1037/