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
Right click on Surfaces in QRiS project tree and choose "Add New Surface"
The QGIS data browser appears.
Exapnd WMS and choose a web mapping service
Back on the QRiS form, provide a name and pick a type etc...
Click OK
Observed
See error screenshot.
Other Considerations
When fixing, please test adding a surface and the user picking from ANY of the many data ttypes in that tree.... Postgres Google Satellite etc.... We don't need to necessarily support all of these.... the software just needs to act gracefully warn the user and not crash.
Maybe we abandon the QGIS data browser and go with a File picker. I don't want to do this straight away and would rather explore whether we can filter the data browser down to the permissible data types etc.
The text was updated successfully, but these errors were encountered:
If the layer is not a 'gdal' compatible layer, then an Invalid Raster message will appear and prevent the user from importing the raster. This should catch any web/wms service rasters. Filtering to gdal rasters (includes most common file types, i.e. tif, gpkg) should prevent a lot of trouble, since we are using GDAL to make the copy anyway. If we come across a new or special type we need, then we will likely require special processing anyway.
This was observed in Logan this week....
Steps to Reproduce
Observed
See error screenshot.
Other Considerations
When fixing, please test adding a surface and the user picking from ANY of the many data ttypes in that tree.... Postgres Google Satellite etc.... We don't need to necessarily support all of these.... the software just needs to act gracefully warn the user and not crash.
Maybe we abandon the QGIS data browser and go with a File picker. I don't want to do this straight away and would rather explore whether we can filter the data browser down to the permissible data types etc.
The text was updated successfully, but these errors were encountered: