The improvements of the vector architecture cover the new 3D
multiattribute, multilayer vector library, a modified NVIZ and a few
database management tools. DBMS is now integral part of the system.
New Vector Engine (geometry):
Support for 2D/3D vectors (see screenshot)
(CAD drawings, TINs), visualization supported in NVIZ
multiformat - also virtual map supported from external data
sources (SHAPE-file, PostGIS) without the need of data conversion
(through OGR library with 'v.external');
Export/Import to PostGIS;
spatial index build on the fly - 'v.build' (was: v.support)
significantly accelerated;
category index to accelerate attribute queries;
Database Management Interface (attributes):
Attribute storage in DBMS for compatibility with industry standards
(SQL based interface for PostgreSQL, mySQL, ODBC, dBase)
multiattribute - attributes saved in dBase files (default) or
saved in external DBMS
multilayer - features in one vector may represent one or several
layers and may be linked to one or many external tables
forms library implemented for user friendly query dialogs
Linear reference systems supported (LRS, yet to integrate)
Applications/Misc:
SQL queries/selects/extractions supported by vector modules
interactive attributes updating is supported through the forms library
(d.what.vect lets you modify directly the attached attributes)
Vector network analysis:
Shortest path, Traveling salesman (round trip), Allocation of sources
(subnetworks), Minimum Steiner trees (starlike connections),
and isodistances (from centers)
(e.g. shortest path, see
screenshot) - based on
DGLIB (Directed Graph Library), costs may be assigned
both to nodes and arcs (and also different in both directions of a vector
line)
GUI generated on runtime and display
manager (screenshots)
i18n: support for multiple languages (messages partially indicated and
translated)
multiple GRASS sessions: a user can start more than one session
at the time
Interoperability
Raster and vector data interoperability is granted through the GDAL/OGR
libraries which implement interfaces to OGC standards and common GIS data formats
GRASS 6.0 experimentally supports reading and writing large files (> 2GB, LFS support)
if it is possible in your operating system. If you compile with
-D_FILE_OFFSET_BITS=64, you should be able to have raster maps
which are larger than 2Gb. Note that the support currently only applies
to the core raster I/O code. Individual programs may or may not work
with large files - please report.
Compiling own GRASS 6.0 modules or changed modules:
simply run "make" in the appropriate directory
and "make install" in the top source directory (or read INSTALL for a simpler method).
Further delopment tasks:
Code cleanup, clones removal, etc.
GRASS as Web server application (client/server architectures)
