[GRASS-dev] Re: [GRASS GIS] #37: r.in.xyz increase region based on input data

[GRASS GIS]

#37: r.in.xyz increase region based on input data
--------------------------+-------------------------------------------------
  Reporter:  marisn       |       Owner:  hamish     
      Type:  enhancement  |      Status:  reopened   
  Priority:  minor        |   Milestone:  6.4.0      
 Component:  default      |     Version:  unspecified
Resolution:               |    Keywords:             
--------------------------+-------------------------------------------------
Comment (by glynn):

 Replying to [comment:7 hamish]:

 >  It would be possible to automatically set the bounds for the new map
 after
 >  scanning the data, but as there is no associated resolution in the data
 >  you have to use whatever the current region settings are, and then code
 in
 >  a 'g.region -a' approach or not.

 That just means aligning the bounds to the existing grid (resolution
 and offset).

 >  At which point before running the module
 >  for the final product you have to scan the data and run 'g.region res=
 -a'
 >  and spend a little time thinking about the region size anyway. Or if
 you
 >  don't want to code in -a (it's problematic enough in g.region already),

 The only things that are problematic about g.region -a are:

 1. The existing behaviour is counterintuitive. That mostly derives
 from the fact that you *might* be changing the resolution at the same
 time, in which case you have to choose the offset arbitrarily.

 2. Any change to the eixting behaviour creates an incompatibility with
 previous versions.

 An enhancement to r.in.xyz wouldn't have either of these problems.
 There is no reason to change the resolution, and there is no existing
 behaviour to remain compatible with.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/37#comment:8>
GRASS GIS <http://grass.osgeo.org>
GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/