#3927: r.external vs r.in.gdal under Windows
-----------------------------------+---------------------------------
Reporter: Nikos Alexandris | Owner: grass-dev@…
Type: defect | Status: new
Priority: major | Milestone:
Component: Raster | Version: svn-releasebranch76
Keywords: r.external, r.in.gdal | CPU: Unspecified
Platform: MSWindows |
-----------------------------------+---------------------------------
This is a case of a (hard to trace) buggy behavior when linking an
external raster map of type Float32. Here an external report:
https://gitlab.com/natcapes/r.estimap.recreation/issues/36.
In short, a raster map of type Float32, linked to an EPSG:3035 Location,
via`r.external`, delivers different descriptive statistics under Windows
than what the identical workflow does under Linux (and what gdalinfo tells
about the data, both under Windows and Linux).
Also, the `--overwrite` flag given to either `r.external` or `r.in.gdal`
does not seem to work under Windows.
Perhaps all these are known issues?
Perhaps this case has to do with the presence of NULL cells too? As is the
case of the example map I use.
The example map `input_water_resources` is available at
https://gitlab.com/natcapes/r.estimap.recreation.data/blob/master/example_data_epsg_3035.tar.gz.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3927>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
