search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

implement r.export and v.export #181

Open landam opened 5 years ago

landam commented 5 years ago

Reported by @landam on 29 Oct 2015 16:07 UTC It would be nice to implement r.export and v.export similarly to https://grass.osgeo.org/grass77/manuals/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: .html1. 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
  2. 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?

GRASS GIS version and provenance

svn-trunk

Migrated-From: https://trac.osgeo.org/grass/ticket/2788

landam commented 5 years ago

Comment by neteler on 5 May 2016 14:08 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 28 Dec 2016 15:04 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by @landam on 5 May 2017 20:40 UTC

landam commented 5 years ago

Modified by @landam on 18 Jul 2017 13:28 UTC

landam commented 5 years ago

Comment by mlennert on 19 Jul 2017 13:14 UTC Replying to [ticket:2788 martinl]:

It would be nice to implement r.export and v.export similarly to https://grass.osgeo.org/grass77/manuals/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: .html>

  1. add to r.out.gdal and v.out.ogr new parameter output_crs, reprojection will be done by GDAL
  2. create new temporary location in output crs, reproject data (r|v.proj) and then export
  3. 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

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Modified by @landam on 25 Aug 2018 16:02 UTC

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed