[GRASS-dev] [GRASS GIS] #3927: r.external vs r.in.gdal under Windows

[GRASS GIS]

#3927: r.external vs r.in.gdal under Windows
-------------------------------+-----------------------------------
  Reporter:  Nikos Alexandris  |      Owner:  grass-dev@…
      Type:  defect            |     Status:  new
  Priority:  critical          |  Milestone:
 Component:  Raster            |    Version:  svn-releasebranch76
Resolution:                    |   Keywords:  r.external, r.in.gdal
       CPU:  Unspecified       |   Platform:  MSWindows
-------------------------------+-----------------------------------

Comment (by Nikos Alexandris):

 Replying to [comment:2 hellik]:
 >
 > >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.
 >
 >
 > {{{
 > r.univar -e map=input_water_resources_ringdal at data
 > total null and non-null cells: 6231077
 > total null cells: 2626801
 > }}}
 >
 > vs
 >
 > {{{
 > r.univar -e map=input_water_resources_rexternal at data
 > total null and non-null cells: 6231077
 > total null cells: 5157779
 > }}}
 >
 > null cells number seems to differ: r.in.gdal: 2626801 vs. r.external:
 total null cells: 5157779

 This confirms my findings. I should have went for the `-e` flag too,
 totally forgot it.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3927#comment:4>
GRASS GIS <https://grass.osgeo.org>