#2788: implement r.export and v.export --------------------------------+------------------------- Reporter: martinl | Owner: grass-dev@… Type: enhancement | Status: new Priority: major | Milestone: 7.1.0 Component: Default | Version: svn-trunk Keywords: r.export, v.export | CPU: Unspecified Platform: Unspecified | --------------------------------+------------------------- 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. Any options? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2788> GRASS GIS <https://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev