[GRASS-dev] [bug #5043] (grass) r.out.gdal does not export "g.region -p"

Hamish hamish_nospam at yahoo.com
Thu Aug 24 23:00:54 EDT 2006


> > >> this bug's URL: http://intevation.de/rt/webrt?serial_num=5043
> > >------------------------------------------------------------------
..
> > >> r.out.gdal does export the region as defined in "g.region -p",
> > >> but the full input raster file.

Paul:
> > This would seem like a good example of why Glynn insisted on
> > retaining  r.resample. r.resample to a temporary file and export
> > that would achieve  the desired effect (i.e. consistent with other
> > raster export modules) I  think? Although would require twice as
> > much disk space. I agree it should  be made consistent (i.e. export
> > based on the current region settings).

Glynn:
> I would suggest that r.out.gdal should behave like other export
> modules and use the current region. If you want "raw" export; you can
> always use "g.region rast=..." first.
> 
> r.in.* modules are a special case, as you can't use "g.region rast="
> before you've imported the raster.


Yes, r.out.gdal should act like other raster modules and work from the
current region. But this goes back to r.out.gdal should be a real module
instead of a wrapper script. Then we could do away with the gdal-plugin
dependancy for generic raster output, which I think is a bit of an
unnecessary burden for regular users to have to worry about for expected
functionality.

Frank's comments from some time ago,  ;)
  http://article.gmane.org/gmane.comp.gis.grass.devel/4657



Hamish




More information about the grass-dev mailing list