Hi again, Two related things: I just started collecting GRASS data which has been floating around in different GRASS DBs in my institute into one, central DB. In that context I am implementing a kind of naming convention (like the one sketched below) in order to make the data order systematically.
My two questions are now: 1) Would it be much work to implement a filter in the Location and Mapset selection window, which would reduce the list to "mapsets owned by me" (e.g. in a tickbox), as these are the only ones I technically can use for working anyway? 2) Is it possible in the WX GUI to allow the user to change the distribution of horizontal space used for the "mapset box" and the "locations box", meaning, that I can make the mapset box wider myself if I have longer mapset names? Would you consider it relevant enough for an enhancement ticket? Kind regards, Stefan -----Original Message----- From: grass-user-boun...@lists.osgeo.org [mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of Blumentrath, Stefan Sent: 4. oktober 2015 15:23 To: Markus Neteler <nete...@osgeo.org> Cc: grass-user grass-user (grass-user@lists.osgeo.org) <grass-user@lists.osgeo.org> Subject: Re: [GRASS-user] Organizing locations and mapsets on NFS for teams Hi Markus, Thanks for your reply. Yes, I was referring to the "Using GRASS GIS locations in a network"/"Student machine(s)" section. I overlooked the "NFS read-only reason" for this solution... Do you (or anyone else) have a smart solution for keeping your locations on NFS tidy? Are you and your colleagues only very disciplined or do you have a kind of data care taker who cleans up the GRASS DB regularly and maybe archives expired projects? Do you use specific naming conventions (esp. for mapsets but maybe also maps)? We copied the convention used on the wiki-page to name locations by CRS, but I am less sure what to do when it comes to mapsets... Here, I was considering using prefixes like "G_" for all mapsets of general interest (probably "GT_" for TGIS-mapsets) followed by a thematic name / keyword, "P_" followed by project name for project mapsets, and "U_" followed by user name for user mapsets... So at least these conceptually different mapset types group / order logicaly... And how do you maintain the PERMANENT mapset(s) on NFS. Does only the creator of the location use / modify it? Are there any solutions for doing that in a collaborative approach (which might be used for other mapsets too)? I mean in terms of access rights... Do you use a metadata repository to make it transparent for everybody what data is in what mapset? Sorry for the bunch of questions. Using GRASS already helps a lot to have and keep the (growing amounts of) data well structured, but a description of recommended practices or field-proven solution might help users to get even more out of it... Kind regards Stefan -----Original Message----- From: neteler.os...@gmail.com [mailto:neteler.os...@gmail.com] On Behalf Of Markus Neteler Sent: 4. oktober 2015 09:01 To: Blumentrath, Stefan <stefan.blumentr...@nina.no> Cc: grass-user grass-user (grass-user@lists.osgeo.org) <grass-user@lists.osgeo.org> Subject: Re: [GRASS-user] Organizing locations and mapsets on NFS for teams On Thu, Oct 1, 2015 at 12:19 PM, Blumentrath, Stefan <stefan.blumentr...@nina.no> wrote: ... > The solution described here: > https://grasswiki.osgeo.org/wiki/Location_and_Mapsets 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. Are you sure about this? Do you refer to the section "Student machine(s)"? In my group, we simply have all in /grassdata/ which is on NFS (actually with a big BeeGFS device behind). Works nicely. Markus _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
