Radim Blazek wrote:
> >> Perfect, that is what I need. Why GRASS_SKIP_MAPSET_OWNER_CHECK should
> >> not be set by programs for read only access?
> >
> > If you only need to read a mapset, you shouldn't need to make it the
> > current mapset, nor should you try.
>
> The mapset I need to read
On 29/09/15 21:59, Radim Blazek wrote:
On Sun, Sep 27, 2015 at 9:14 PM, Glynn Clements
wrote:
Radim Blazek wrote:
Perfect, that is what I need. Why GRASS_SKIP_MAPSET_OWNER_CHECK should
not be set by programs for read only access?
If you only need to read a
On Sun, Sep 27, 2015 at 9:14 PM, Glynn Clements
wrote:
>
> Radim Blazek wrote:
>
>> Perfect, that is what I need. Why GRASS_SKIP_MAPSET_OWNER_CHECK should
>> not be set by programs for read only access?
>
> If you only need to read a mapset, you shouldn't need to make it
Radim Blazek wrote:
> Perfect, that is what I need. Why GRASS_SKIP_MAPSET_OWNER_CHECK should
> not be set by programs for read only access?
If you only need to read a mapset, you shouldn't need to make it the
current mapset, nor should you try.
Making a mapset the current mapset means that any
Thanks for the extensive explanation, Glynn.
On Tue, Sep 22, 2015 at 5:18 PM, Glynn Clements
wrote:
>
> Radim Blazek wrote:
>
>> Is it possible to access data through GRASS modules in a location
>> where the user does not own any mapset? Each GRASS module calls first
>>
Radim Blazek wrote:
> Is it possible to access data through GRASS modules in a location
> where the user does not own any mapset? Each GRASS module calls first
> G_gisinit() which checks if current mapset returned by G_mapset() is
> owned by current user. If it is not, it ends with fatal error.
Is it possible to access data through GRASS modules in a location
where the user does not own any mapset? Each GRASS module calls first
G_gisinit() which checks if current mapset returned by G_mapset() is
owned by current user. If it is not, it ends with fatal error. How to
get around this for