On Aug 8, 2008, at 9:00 AM, <grass-dev-request@lists.osgeo.org> wrote:
Date: Fri, 08 Aug 2008 10:27:33 +0300
From: Wolf Bergenheim <wolf+grass@bergenheim.net>
Subject: Re: [GRASS-dev] terminology issues in grass7
To: Martin Landa <landa.martin@gmail.com>
Cc: GRASS developers list <grass-dev@lists.osgeo.org>
Message-ID: <489BF565.70002@bergenheim.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 07.08.2008 20:22, Martin Landa wrote:
GRASS is basically layer-based GIS, in grass6 we call layers as maps,
e.g. raster map. I would suggest to use in grass7 'layer' instead
* raster layer
* 3d raster layer
* vector layer
'Map' could be used for composition of layers. And to rename all the
arguments ('map' -> 'layer').
'Layer' is currently used for vectors. Original term 'field number'
seems to me as a better choice. It would mean at the end to rename
also all 'layer' parameters to 'field'.
I agree with changing map to layers and using map to refer to the composited group of layers.
However, I disagree with using "field number" for the features that are now called "layers" in vectors. These are "key fields" or "keys" in standard DBMS terminology for linking the vector table with the attribute table. I propose using "key" or "keyfield".
Michael
Yes, that would conform more with the terminology of most other GIS:es
out there. Especially the vector layer is very confusing for people who
switch to GRASS. The renaming the layer parameters might need a lot of
manual work, or maybe we can device a script to do it.
Hi,
2008/8/8 Michael Barton <michael.barton@asu.edu>:
However, I disagree with using "field number" for the features that are now
called "layers" in vectors. These are "key fields" or "keys" in standard
DBMS terminology for linking the vector table with the attribute table. I
propose using "key" or "keyfield".
it sounds reasonable to me...
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *
Michael Barton pisze:
I agree with changing map to layers and using map to refer to the composited group of layers.
Sounds alright to me as well.
However, I disagree with using "field number" for the features that are now called "layers" in vectors. These are "key fields" or "keys" in standard DBMS terminology for linking the vector table with the attribute table. I propose using "key" or "keyfield".
In GRASS there is already a term "key column" (the column that links the
category number with the table row). Since terms "field" and "column"
are sometimes used interchangeably, and term "key column" is already a
part of GRASS terminology, using "keyfield" for something different will
lead to confussion.
May I suggest "table link" in place of the current "layer" then? So each
vector map can have multilpe "table links", and each "table" can have
it's own "key column".
As to "voxel" and aliases (i.e. "3D raster", "G3D", "volume", "GRID3D",
"3d cell") - could we just stick to "3d raster layer"? A little longish,
but plain obvious and conforms to "(2d) raster layer", "(2d/3d) vector
layer".
Maciek
--
Maciej Sieczka
www.sieczka.org
Hi,
2008/8/9 Maciej Sieczka <tutey@o2.pl>:
In GRASS there is already a term "key column" (the column that links the
category number with the table row). Since terms "field" and "column"
are sometimes used interchangeably, and term "key column" is already a
part of GRASS terminology, using "keyfield" for something different will
lead to confussion.
May I suggest "table link" in place of the current "layer" then? So each
vector map can have multilpe "table links", and each "table" can have
it's own "key column".
nice idea, "table link" or "dblink" make sense to me.
As to "voxel" and aliases (i.e. "3D raster", "G3D", "volume", "GRID3D",
"3d cell") - could we just stick to "3d raster layer"? A little longish,
but plain obvious and conforms to "(2d) raster layer", "(2d/3d) vector
layer".
+1 for 3d raster layer
BTW which elements we can discard in GRASS7?
rast OK
rast3d OK
vect - OK
oldvect - ?
asciivect - ?
icon - ?
labels - ?
sites - remove?
region
region3d - should be removed
group - OK
3dview - remove?, no support for TCL/TK Nviz ?
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *
Martin Landa pisze:
2008/8/9 Maciej Sieczka <tutey@o2.pl>:
In GRASS there is already a term "key column" (the column that links the
category number with the table row). Since terms "field" and "column"
are sometimes used interchangeably, and term "key column" is already a
part of GRASS terminology, using "keyfield" for something different will
lead to confussion.
May I suggest "table link" in place of the current "layer" then? So each
vector map can have multilpe "table links", and each "table" can have
it's own "key column".
nice idea, "table link" or "dblink" make sense to me.
Hmm, "dblink"... "db" seems a shortname for "database" rather than
"table", and the two are different things. Maybe "tbllink" for a
shortname would do better?
As to "voxel" and aliases (i.e. "3D raster", "G3D", "volume", "GRID3D",
"3d cell") - could we just stick to "3d raster layer"? A little longish,
but plain obvious and conforms to "(2d) raster layer", "(2d/3d) vector
layer".
+1 for 3d raster layer
BTW which elements we can discard in GRASS7?
rast OK
rast3d OK
vect - OK
All are fine.
oldvect - ?
Remove?
asciivect - ?
I'd keep it as "GRASS ASCII vector" format is still there.
icon - ?
labels - ?
These seem still valid and in use I guess.
sites - remove?
+1
region
region is OK.
region3d - should be removed
+1
group - OK
Yup.
3dview - remove?, no support for TCL/TK Nviz ?
?
Maciek
--
Maciej Sieczka
www.sieczka.org