[GRASS5] g|r.region

[Brad Douglas]

On Tue, 2006-02-07 at 22:36 +0100, Markus Neteler wrote:
> On Tue, Feb 07, 2006 at 09:28:33PM +0000, Glynn Clements wrote:
> > Brad Douglas wrote:
> > 
> > > Is there a specific reason to keep r.region around?  Is there a case
> > > where you want to have a specific raster in a different metric than the
> > > global?
> > 
> > r.region exists for a specific purpose: to "fix" the region
> > information for rasters which were imported without georeferencing
> > information.
> > 
> > > If so, why is there no v.region?
> > 
> > Ungeoreferenced vector maps are uncommon,
> 
> Most CAD drawings are not georeferenced - so in this
> "niche" it's very common (unfortunately).

Unless there are no reference data/points (or in XY "projection"), I
tend to manipulate my data with GDAL before importing into GRASS.  I'm
not a heavy end-user, though.

> > and there is already v.transform.

Would it make sense to move this functionality to g.region to keep all
region related work in a single module?  A flag '-s' could be added in
order to set the region of a particular map (be it vector or raster).

I can see strong cases made for both modular and unified functionality.


-- 
Brad Douglas <rez at touchofmadness.com>                      KB8UYR
Address: 37.49,-121.92 / WGS84      National Map Corps #TNMC-3785
GRASS GIS Developer