[GRASS-dev] [GRASS GIS] #2055: r.in.gdal lacks flag "-r Limit import to the current region"

[GRASS GIS]

#2055: r.in.gdal lacks flag "-r Limit import to the current region"
--------------------------+---------------------------------
  Reporter:  neteler      |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:  7.2.0
 Component:  Raster       |    Version:  svn-trunk
Resolution:               |   Keywords:  r.in.gdal, r.import
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+---------------------------------

Comment (by neteler):

 Replying to [comment:1 mmetz]:
 > Replying to [ticket:2055 neteler]:
 > > While v.in.ogr offers "-r   Limit import to the current region"
 > > the module r.in.gdal does not.
 > >
 > v.in.ogr -r imports all features that overlap with the current region.
 The result might thus have extents extending beyond the current region,
 which makes sense.
 >
 > Translated to raster import, I see a disadvantage when limiting the
 import to the current region: for a given project, raw data are commonly
 coming from different sources with different extents and resolution. You
 would then need to use one of the r.resamp.* modules to resampling raw
 data to the current region, and r.resamp.* modules typically extend the
 current region by the margin required for resampling (if not nn). Limiting
 the import to the current region followed by resampling would thus eat
 away rows and columns at the region's borders.

 The solution would be "lazy cutting", that is not cutting sharp to the
 boundary but allow for a small "extra". Essentially, like v.in.ogr
 behaves. Resampling is definitely undesired since we usually import as-is
 in r.in.gdal.

 Lines to look at:
 https://trac.osgeo.org/grass/browser/grass/trunk/raster/r.in.gdal/main.c#L359

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