Hi Stefan
I see the problem, but have no solution for the organization in GRASS.
Concerning PostgreSQL- our data are in different schemas, to allow for
access of all within our SQL-code. Example: One schema for initial data
and others for processed data or different Versions. Views are used
Hi Stefan
Not sure on your needs, but if not all projects run on GRASS, it might
be an option to run a spatial database as backend to store the data. At
ETH Zürich we have been running PostgreSQL to host our data. Access to
different software is running very well (GRASS, QGIS, R,..) and the
Hi Patrick,
Thanks for your reply!
Yes, PostgreSQL/PostGIS is a nice addition to the GRASS GIS DB (where we
currently run SQLite as backend).
PostgreSQL however, is much less usable for (esp. heavy) raster data: terrain
models and so on.
In addition, the same organizational question arises
