<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="NO-BOK" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I was wondering if someone knows some well-working solutions for collaborating on locations and mapsets in teams (“best practice”)?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Background: In my organization we have some 70 users working in different projects (n~120) (not all use GRASS though), where new data is generated or acquired which might be of wider interest throughout the organisation.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">My aim is that data of common interest is shared in a common GRASS database on NFS. Yet the problem is that things might get messy with all project-mapsets, user-mapsets and “PERMANENT”-like mapsets in one location (in
the light of the amount of available GIS data, one PERMANENT mapset appears to be no longer sufficient I guess, esp. when also space time datasets are hosted in the GRASS DB).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The solution described here: <a href="https://grasswiki.osgeo.org/wiki/Location_and_Mapsets">
https://grasswiki.osgeo.org/wiki/Location_and_Mapsets</a> with common GRASS DB on NFS linked into users home directory is somewhat sexy in order to keep the “user mapsets” out of the common GRASS GIS DB. The drawback however is, that users explicitly have to
switch between the two GRASS DBs if they want to share data on NFS, if I understood the consequences correctly. Is someone aware of some nice “one-click- tools” which might be used to sync between home and NFS GRASS DB. Would one need to write a wrapper script
around r./v.pack and r./v.unpack for such a job (if not entire (and tidy!) mapsets can be copied) to simplify synchronization for basic users?
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In addition, if users generate one mapset for every dataset they might be willing to share, this may lead to way to many mapsets. Furthermore, such mapsets do not end up in the search path automatically as data in PERMANENT
would... I was considering to group data as far as possible into INSPIRE themes / ISO topics (meaning one mapset per topic plus extra mapsets for time series data). But then different users would need to be able to add data in those mapsets meaning modify
them (as it would be the case for PERMANENT cause there is not one person handling all data anyway)… Does someone work with a “data janitor user” others may “su” to in order to do general data maintenance?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">How do you deal with mapsets for projects where different users collaborate? Do you use project name as a prefix followed by user name or something like this, so that mapsets for a project are grouped? Do you use project
user accounts?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I am grateful for any recommendations or info on how others organize locations and mapsets in a collaborative environment…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Cheers<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Stefan<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>