[GRASS-user] sharing GRASS mapsets

[Stefan Blumentrath]

Hi Laura,

There are several options.

One option would be to subdivide “ENVIROMENTAL_COVARIATES” into e.g. topics.
In my organisation (also environmental research) we organized mapsets with prefixes (g_ for mapsets of general interest, gt_ for time series, p_ for projects, u_ for users). Different users can take care of different topics (but everybody has to clean up his/her own mess).
These mapsets can then easily added to the users search_path with g.mapsets (https://grass.osgeo.org/grass74/manuals/g.mapsets.html)…

An advantage of splitting up ENVIROMENTAL_COVARIATES into smaller mapsets is that it is easier to move chunks of data (e.g. from central storage to compute units (laptop/server))…

If your users are allowed to change file ownership, they could in principle take over “ENVIROMENTAL_COVARIATES”. However, an important point of the ownership check implemented in GRASS is to make sure that users do not shoot each others in the foot…
That check can be overwritten with the GRASS_SKIP_MAPSET_OWNER_CHECK environment variable (see: https://grass.osgeo.org/grass74/manuals/variables.html)

See also the related issue: https://trac.osgeo.org/grass/ticket/1829

For both of the latter options there is a significant risk in a multi-user environment…

Hope that helps a bit…

Cheers
Stefan

From: grass-user <grass-user-bounces at lists.osgeo.org> On Behalf Of Laura Poggio
Sent: onsdag 6. februar 2019 12:22
To: GRASS user list <grass-user at lists.osgeo.org>
Subject: [GRASS-user] sharing GRASS mapsets

Dear all,
we need to share a GRASS location and its mapsets across multiple users.
We would like to have a structure similar to this:
LOCATION:
 PERMANENT
 ENVIROMENTAL_COVARIATES
 working_mapset_for_each_user

It is clear in the documentation that a user can only write in a mapset that it owns.
However we would need to have multiple users to be able to add/delete/modify files to the ENVIROMENTAL_COVARIATES mapset. Is this possible at all? any workaround that can be implemented?

Thanks in advance

Laura




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190206/1b6d733c/attachment-0001.html>