Opened 9 years ago

Last modified 5 years ago

#2788 new enhancement

implement r.export and v.export

Reported by: martinl Owned by: grass-dev@…
Priority: normal Milestone: 7.8.3
Component: Default Version: svn-trunk
Keywords: r.export, v.export Cc:
CPU: Unspecified Platform: Unspecified

Description

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
  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. Any options?

Change History (15)

comment:1 by neteler, 9 years ago

Milestone: 7.1.0 → 7.2.0

Milestone renamed

comment:2 by neteler, 8 years ago

Milestone: 7.2.0 → 7.2.1

Ticket retargeted after milestone closed

comment:3 by martinl, 8 years ago

Milestone: 7.2.1 → 7.2.2

comment:4 by martinl, 8 years ago

Milestone: 7.2.2 → 7.4.0

in reply to:  description comment:5 by mlennert, 8 years ago

Replying to 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
  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

comment:6 by neteler, 7 years ago

Milestone: 7.4.0 → 7.4.1

Ticket retargeted after milestone closed

comment:7 by neteler, 7 years ago

Milestone: 7.4.1 → 7.4.2

comment:8 by martinl, 6 years ago

Milestone: 7.4.2 → 7.6.0

comment:9 by martinl, 6 years ago

Milestone: 7.6.0 → 7.6.1

Ticket retargeted after milestone closed

comment:10 by martinl, 6 years ago

Milestone: 7.6.1 → 7.6.2

Ticket retargeted after milestone closed

comment:11 by martinl, 6 years ago

Milestone: 7.6.2 → 7.8.0
Priority: major → normal

comment:12 by neteler, 5 years ago

Milestone: 7.8.0 → 7.8.1

Ticket retargeted after milestone closed

comment:13 by neteler, 5 years ago

Milestone: 7.8.1 → 7.8.2

Ticket retargeted after milestone closed

comment:14 by neteler, 5 years ago

Milestone: 7.8.2

Ticket retargeted after milestone closed

comment:15 by neteler, 5 years ago

Milestone: → 7.8.3
Note: See TracTickets for help on using tickets.