[GRASS-dev] [GRASS GIS] #2788: implement r.export and v.export

GRASS GIS trac at osgeo.org
Wed Jul 19 06:14:11 PDT 2017


#2788: implement r.export and v.export
--------------------------+--------------------------------
  Reporter:  martinl      |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  major        |  Milestone:  7.4.0
 Component:  Default      |    Version:  svn-trunk
Resolution:               |   Keywords:  r.export, v.export
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+--------------------------------

Comment (by mlennert):

 Replying to [ticket:2788 martinl]:
 > It would be nice to implement `r.export` and `v.export` similarly to
 G7:r.import and G7:v.export. These modules would call `r.out.gdal`/
 `v.out.ogr` and then reproject output files to defined crs. I can see
 several scenarious:
 >
 >  1. add to `r.out.gdal` and `v.out.ogr` new parameter `output_crs`,
 reprojection will be done by GDAL
 >  1. create new temporary location in output crs, reproject data
 (`r|v.proj`) and then export
 >  1. export data to temporary output file and then to reproject by GDAL
 >
 > It seems that 2) fits in the best way to the current `r.import` and
 `v.import` approach.

 +1

 I think this option is best as it will allow to use the known v./r.proj
 reprojection options.

 Moritz

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



More information about the grass-dev mailing list