[GRASS-dev] [GRASS GIS] #3374: r.import inconsistent behavior when using r.in.gdal and r.proj
GRASS GIS
trac at osgeo.org
Tue Jul 18 12:25:55 PDT 2017
#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
Keywords: r.import, r.in.gdal, r.proj | CPU: Unspecified
Platform: Unspecified |
-----------------------------------------+-------------------------
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?
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3374>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list