1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
/*!
\mainpage GRASS 6.0 Vector Architecture
by GRASS Development Team
http://grass.itc.it
\section intro Introduction
This description covers the new GRASS 5.7/6.0 vector library
architecture. This new architecture overcomes the vector limitations
of GRASS 4.x-5.4.x by extending the vector support with attributes
stored in external relational databases and by new 3D
capabilities. Besides internal file based storage the geometry may
alternatively be stored in PostGIS database. This enables users to
maintain large data sets with simultaneous write access. External GIS
formats such as SHAPE-files may be used directly without necessity of
format conversion.
\section background Background
generally, the vector data model is used to describe geographic
phenomena which may be represented by geometric entities (primitives)
like points, lines, and areas. The GRASS vector data model includes
the description of topology, where besides the coordinates -
describing the location of the points, lines, boundaries and centroids
- also their spatial relations are stored. In general, topological GIS
require a data structure where common boundary between two adjacent
areas is stored as a single line, simplifying the map maintenance.
\section libraries Libraries
Besides internal library functions there are two main libraries:
\subsection vlib Vlib (Vector library)
For details please read Blazek et al. 2002 (see below) as well as the
references in this document.
\subsubsection vlibspidx Vector library categories and layers
<P>
<i>Note: "layer" was called "field" in earlier version.</i>
<P>
In GRASS a "category" is a feature ID used to link geometry
with attributes stored in one or many (external) database table(s).
Each vector feature inside a vector map has zero, one or more
<layer,category> tuple(s). A user can (but not must) create attribute
tables which are referenced by the layer, and rows which are essentially
referenced by the <layer,category> pair.
\subsubsection vlibspidx Vector library spatial index management
Spatial index (based on R-tree) is calculated on the fly.
\subsubsection vlibtopo Vector library topology management
Topology is generated for all kinds of vector types. Memory is not
released by default. The programmer can force the library to release
the memory by using Vect_set_release_support(). But: The programmer
cannot run Vect_set_release_support() in mid process because all
vectors are needed in the spatial index is needed to build topology.
Topology is also necessary for points in case of vector network
because the graph is built using topology informations about lines
and points.
The topology structure does not only store the topology but also
'line' bounding box and line offset in coor file (index).
The existing spatial index is using line ID in 'topology' structure
to identify lines in 'coor' file. Currently it is not possile to build
spatial index without topology.
\subsubsubsection vlibtopo_coor coor file
<ol>
<li> In the coor file the following is stored: 'line' (element) type,
number of attributes and layer number for each category.
<li> Coordinates in binary file are stored as double (8 bytes).
</ol>
\subsubsection vlibtin Vector TINs
TINs are created as 2D/3D vector polygons consisting of 3 vertices.
\subsubsection vlibfunc List of vector library functions
The Vect_*() functions are the programmer's API for GRASS vector
programming. See details here:
<a class="qindex" href="modules.html">Structured Vect_*() functions list</a>
\subsection dglib DGLib (Directed Graph Library)
The Directed Graph Library or DGLib (Micarelli 2002,
http://grass.itc.it/dglib/) provides functionality for vector network
analysis. This library released under GPL is hosted by the GRASS project (in
the CVS server within the GRASS source code). As stand-alone library it
may also be used by other software project.
The Directed Graph Library library provides functionality to assign costs to
lines and/or nodes. That means that costs can be accumulated while traveling
along polylines. The user can assign individual costs to all lines and/or
nodes of a vector map and later calculate shortest path connections based on
the accumulated costs. Applications are transport analysis, connectivity and
more.
For details please read Blazek et al. 2002 (see below).
\section contacts Contacts
Radim Blazek (vector architecture) <blazek@itc.it>
Roberto Micarelli (DGLib) <mi.ro@iol.it>
\section references References
Text based on: R. Blazek, M. Neteler, and R. Micarelli. The new GRASS 5.1
vector architecture. In Open source GIS - GRASS users conference 2002,
Trento, Italy, 11-13 September 2002. University of Trento, Italy, 2002.
<a href="http://www.ing.unitn.it/~grass/conferences/GRASS2002/proceedings/proceedings/pdfs/Blazek_Radim.pdf">http://www.ing.unitn.it/~grass/conferences/GRASS2002/proceedings/proceedings/pdfs/Blazek_Radim.pdf</a>
\section seealso See Also
<a href="../../db/html/index.html">DBMI - Database Management Interface</a>
Last change: $Date: 2005/08/08 09:06:29 $
*/
|
