[GRASS5] features needed for 6.2
michael.barton at asu.edu
Tue Mar 28 18:57:18 EST 2006
OK. That makes sense. It got put off in the transition to 6 and I just
wanted to make sure that people didn't forget about it.
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402
voice: 480-965-6262; fax: 480-965-7671
> From: Glynn Clements <glynn at gclements.plus.com>
> Date: Wed, 29 Mar 2006 00:55:00 +0100
> To: Michael Barton <michael.barton at asu.edu>
> Cc: Radim Blazek <radim.blazek at gmail.com>, <grass5 at grass.itc.it>
> Subject: Re: [GRASS5] features needed for 6.2
> Michael Barton wrote:
>> There has been discussion periodically about changing how raster files are
>> stored within mapsets. What I understood (perhaps incorrectly I suppose) was
>> that the idea was to store each map in a separate folder, like vectors,
>> rather than combine all raster cat files in one folder, header files in
>> another folder, and so on. This would make GRASS raster files much more
>> portable and easier to manipulate. However, there would need to be some way
>> to convert formats as between old and new vector formats.
> OK, that makes sense.
> It's also completely orthogonal to any changes which I was considering
> regarding the actual raster format.
> But, I think that it's the kind of thing which needs to be done at the
> start of a revision cycle, i.e. not in 6.2.0 but at the beginning of
> 6.3cvs. If you try to do it for 6.2.0, it's going to either push 6.2.0
> back to next year or make 6.2.0 too buggy for actual use.
> Glynn Clements <glynn at gclements.plus.com>
More information about the grass-dev