Brent-Edwards
Brent-Edwards
Any chance that you could add support for this format - xmswiki.com/wiki/SMS:2D_Mesh_Files_*.2dm? Thanks!
GDAL/OGR currently does not provide an option for specifying the the tablespace for Postgresql/PostGIS outputs. The user is thus forced to move the table/index to the desired, non default tablespace...
It would be really useful to provide the option to specify nodata values, data type and bit depth for the output rasters. The tool currently seems to default to -32768...
The existing documentation doesn't contain information regarding calculation methods (ex. all touching versus pixels centers). Existing documentation - [https://docs.qgis.org/3.28/en/docs/user_manual/processing_algs/qgis/rasteranalysis.html#qgiszonalstatisticsfb](https://docs.qgis.org/3.28/en/docs/user_manual/processing_algs/qgis/rasteranalysis.html#qgiszonalstatisticsfb) Examples of the need for better documentation and content suggestions- [https://gis.stackexchange.com/questions/276794/how-does-qgis-zonal-statistics-handle-partially-overlapping-pixels](https://gis.stackexchange.com/questions/276794/how-does-qgis-zonal-statistics-handle-partially-overlapping-pixels)