[GRASS-dev] terminology issues in grass7

[Markus Metz]

According to the Open Geospatial Consortium, there are some ISO 
standards [1]. Of particular interest may be

- ISO/IEC 13249-3:2003, Information technology — Database languages — 
SQL multimedia and application packages — Part 3: Spatial
- ISO 19107:2003, Geographic information ― Spatial schema
- ISO 19125-1:2004, Geographic information — Simple feature access — 
Part 1: Common architecture
- ISO 19125-2:2005, Geographic information — Simple feature access — 
Part 2: SQL Option

[1] http://www.opengeospatial.org/standards

Markus M


Helena Mitasova wrote:
> I am wondering whether this should be discussed at osgeo level to make 
> sure
> that we have at least some consistency in terminology used in OSGeo 
> software stack.
>
> I checked some on-line GIS terminology and category is mostly used in 
> a different
> context so I am curious what are the current vector data layers as 
> they are called in GRASS6
> (with "category set" suggested as a better term) called in other 
> packages such as QGIS (if they are supported)?
> For GRASS7 release there is a unique opportunity to align the terminology
> within OSGeo if there is an interest to do that although most efforts 
> on terminology
> and dictionary tend to die pretty quickly, but maybe we can least find 
> some
> common ground for vector data model,
>
> Helena
>
> http://www.lib.unc.edu/reference/gis/datafinder/glossary.html
> http://www.opengeospatial.org/ogc/glossary/
> http://support.esri.com/index.cfm?fa=knowledgebase.gisDictionary.gateway
>
> On Apr 26, 2009, at 7:01 PM, Martin Landa wrote:
>
>> Hi,
>>
>> 2008/8/11 Maciej Sieczka <tutey at o2.pl>:
>>
>> [...]
>>
>>> (A "table" is an object in the database that stores the given "layer"'s
>>> attributes, and the "table" and "layer"'s geometrical features are
>>> linked using "key column" in which the "categories" are stored inside
>>> the "table".)
>>>
>>> Regarding Moritz's remark I indeed missed the fact that the vector map
>>> having 0 or more "layers" does not directly imply it has the same 
>>> number
>>> of data "tables". Given that, "table link" to replace "layer" as I
>>> suggested is bad. If we are to change the term, we should do it right.
>>> How do you like "category set" then, "catset" in short? Together with
>>> with replacing term vector "map" with vector "layer" it would yield:
>>>
>>> Each vector "feature" (line, point etc.) can have 0 or more 
>>> "categories"
>>> in a vector "layer". Each "category" belongs to only 1 "category set".
>>> Each "category set" of a vector "layer" can be connected or not with a
>>> single database "table". The "key column" in that "table" stores the
>>> "categories" of "features" present in the given "category set".
>>
>> after some time I am going to re-open this topic... I have summarized
>> the proposals on the wiki
>>
>> http://grass.osgeo.org/wiki/GRASS_7_Terminology#Vector_layer
>>
>>> From my point of view, I would suggest to use "category set" (catset)
>> as replacement for 'layer'.
>>
>> Please feel free to put here your suggestions. It would be good to
>> close this topic soon. Then I can start changing terminology in GRASS
>> 7.
>>
>> Best regards, Martin
>>
>> -- 
>> Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>