Hi,
I have a question about g.access.
When I try to change permissions for mapset PERMANENT, it does not work:
-> access to PERMANENT must be open, nothing changed
when I try to change permissions for another mapset test, it works:
-> Everyone now has access to mapset test
Does this mean, that I cannot use mapset PERMANENT together with other users?
Or how can I resolve/change this?
regards,
Otto
Otto Dassau wrote:
I have a question about g.access.
When I try to change permissions for mapset PERMANENT, it does not work:
-> access to PERMANENT must be open, nothing changedwhen I try to change permissions for another mapset test, it works:
-> Everyone now has access to mapset testDoes this mean, that I cannot use mapset PERMANENT together with other users?
Or how can I resolve/change this?
A few notes:
1. You cannot select a mapset as the current mapset (where any new
maps will be created) unless you own the mapset directory; having
write permission isn't sufficient.
2. To change the permissions for a mapset, you have to own the mapset
directory.
3. No-one should ever have the PERMANENT mapset as their current
mapset. GRASS doesn't actually enforce this, although it probably
should.
--
Glynn Clements <glynn@gclements.plus.com>
Dear Glynn
Otto Dassau wrote:
I have a question about g.access.
When I try to change permissions for mapset PERMANENT, it does not work:
-> access to PERMANENT must be open, nothing changedwhen I try to change permissions for another mapset test, it works:
-> Everyone now has access to mapset testDoes this mean, that I cannot use mapset PERMANENT together with other users?
Or how can I resolve/change this?A few notes:
1. You cannot select a mapset as the current mapset (where any new
maps will be created) unless you own the mapset directory; having
write permission isn't sufficient.
does this mean, only one user (the owner of a mapset) can create new maps in 'his/her' mapset? So if I want another user to have write permissions I would have to change the owner of the mapset directory.
for example:
I work in a project (mapset) and during my holliday another user shall keep on working for me. If I don't want to create an extra mapset, because I will be back in a couple of weeks and don't want to have all data and results split in 2 mapsets, I could change the owner of the mapset. Is this correct?
2. To change the permissions for a mapset, you have to own the mapset
directory.
ok - I understand, and g.access is only to restrict read and execute access (as written in the manual).
3. No-one should ever have the PERMANENT mapset as their current
mapset. GRASS doesn't actually enforce this, although it probably
should.
yes, that would be fine - I think.
thanks a lot for your notes!
Otto
--
Glynn Clements <glynn@gclements.plus.com>
Otto Dassau wrote:
> 1. You cannot select a mapset as the current mapset (where any new
> maps will be created) unless you own the mapset directory; having
> write permission isn't sufficient.does this mean, only one user (the owner of a mapset) can create
new maps in 'his/her' mapset?
Yes.
So if I want another user to have write permissions I would have to
change the owner of the mapset directory.
Yes.
for example:
I work in a project (mapset) and during my holliday another user shall
keep on working for me. If I don't want to create an extra mapset, because
I will be back in a couple of weeks and don't want to have all data and
results split in 2 mapsets, I could change the owner of the mapset. Is
this correct?
Yes.
--
Glynn Clements <glynn@gclements.plus.com>
Glynn Clements wrote:
3. No-one should ever have the PERMANENT mapset as their current
mapset. GRASS doesn't actually enforce this, although it probably
should.
It is useful to occasionally drop into the PERMANENT to use
"g.copy perm_map,map@other_mapset", so that a base map will be available
to all mapsets without qualification or risk of accidental damage.
Maybe add a "are you sure you want to do this?" dialogue window to the
GUI startup menu if the PERMANENT mapset is selected.
Hamish
Otto Dassau wrote:
I work in a project (mapset) and during my holliday another user shall
keep on working for me. If I don't want to create an extra mapset,
because I will be back in a couple of weeks and don't want to have
all data and results split in 2 mapsets, I could change the owner of
the mapset. Is this correct?
you could do that. But fetching maps from other mapsets in the same
location is very easy:
# select "map1" from the "otto" mapset: (if g.access permission is granted)
r.univar map1@otto
# copy a map from another mapset back to your mapset for modification:
g.copy map2@other,map2
Hamish