You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Latest merge to OWS master moves the "native_crs" and "native_resolution" elements out of WCS and into the main layer config. (As they will be needed for WMS as well under the new OWS resource management framework.) This may produce warning messages in dev.
Note that both elements are only required if the native CRS and resolution cannot be determined from the product metadata. If you do have layers that need them in config, you can specify them in BOTH positions (i.e. in wcs section AND main layer section) and then it will work with both current master and 1.8.15. (It will throw a warning in master is all). (edited)
The text was updated successfully, but these errors were encountered:
Has this been resolved with the #250 merge? We are currently having to manually export then assign CRSs while using the WCS in QGIS, to circumvent errors.
From @SpacemanPaul
Latest merge to OWS master moves the "native_crs" and "native_resolution" elements out of WCS and into the main layer config. (As they will be needed for WMS as well under the new OWS resource management framework.) This may produce warning messages in dev.
Note that both elements are only required if the native CRS and resolution cannot be determined from the product metadata. If you do have layers that need them in config, you can specify them in BOTH positions (i.e. in wcs section AND main layer section) and then it will work with both current master and 1.8.15. (It will throw a warning in master is all). (edited)
The text was updated successfully, but these errors were encountered: