[GRASS-dev] [GRASS GIS] #3374: r.import inconsistent behavior when using r.in.gdal and r.proj

[GRASS GIS]

#3374: r.import inconsistent behavior when using r.in.gdal and r.proj
--------------------------+-----------------------------------------
  Reporter:  annakrat     |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  normal       |  Milestone:  7.4.0
 Component:  Raster       |    Version:  svn-trunk
Resolution:               |   Keywords:  r.import, r.in.gdal, r.proj
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-----------------------------------------

Comment (by mmetz):

 Replying to [ticket:3374 annakrat]:
 > Module r.import has options for output resolution and extent, but they
 are basically ignored when coordinates system matches and r.in.gdal is
 used, they are used only when reprojecting. So when there is no
 reprojection needed:
 >
 > 1. r.in.gdal has new -r flag, so that should be used if extent=region
 > 2. when resolution=value or resolution=region, r.import should resample
 the raster. The default (resolution=estimated) means r.in.gdal uses
 resolution of the raster as it is now.
 >
 > Any objection to this behavior?

 The purpose and intention of [r|v].import is easy import of GIS data with
 optional reprojection. I suggest to have a minimalistic interface for the
 two modules and refer to other modules if more control over the import
 process is needed.

 There are a number of r.resamp.* modules available. The appropriate module
 and method depends on both the kind of input data (categorical, nominal,
 metric) and the kind of resampling (upsampling or downsampling). IMHO it
 would be safer to leave this decision to the user.

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