[GRASS-dev] lib/vask [i.points replacement]

[Michael Barton]

Glynn and Hamish,

One more thought. Because the GRASS database is a set of geospatial
information for a particular projection (location) and set of maps/images
(mapset), storing GCP's for the geospatial data with that projection in the
GRASS database is a reasonable thing to do.

However, we do need to keep track of the target location for a particular
GCP POINTS file--either in the GCP file itself, or in a separate ascii file
like we have now. This is one argument for keeping at least the
$GISBASE/group/ structure. However, it might make more sense if each
directory under $GISBASE/group/ represents a target location (it could have
multiple GCP files) rather than the way it is now with a single target,
single POINTS file, and list  of maps.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Glynn Clements <glynn at gclements.plus.com>
> Date: Mon, 26 Jun 2006 13:41:32 +0100
> To: Hamish <hamish_nospam at yahoo.com>
> Cc: <michael.barton at asu.edu>, <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] lib/vask  [i.points replacement]
> 
> The GRASS database directory is supposed to be a database of
> geospatial information, not a place for individual applications to
> store their session files.