[GRASS-dev] Landsat MTL files

[Markus Metz]

On Tue, Nov 14, 2017 at 9:22 AM, Stefan Blumentrath <
Stefan.Blumentrath at nina.no> wrote:
>
> Hi,
>
> Sorry if I confuse something here or cause confusion...
>
> I do understand that it can be handy to handle Landsat scenes in
different mapsets. And creating new mapsets at import can be a smart
workflow indeed.
>
> I just thought GRASS modules were supposed not to write data to other
mapsets than the ones they are called from (which I understood was e.g. why
Sören changed modules of the temporal framework that always wrote to TGIS
DB in PERMANENT)?

GRASS modules should not try to write to existing mapsets because they
might not have permission to do so. Creating a new mapset and then writing
to the new mapset is fine.

Markus M
>
>
>
> Cheers
>
> Stefan
>
>
>
> From: grass-dev [mailto:grass-dev-bounces at lists.osgeo.org] On Behalf Of
Markus Neteler
> Sent: tirsdag 14. november 2017 08.36
> To: Nikos Alexandris <nik at nikosalexandris.net>
> Cc: GRASS developers list <grass-dev at lists.osgeo.org>
> Subject: Re: [GRASS-dev] Landsat MTL files
>
>
>
> On Nov 14, 2017 1:24 AM, "Nikos Alexandris" <nik at nikosalexandris.net>
wrote:
> >
> > * Nikos Alexandris <nik at nikosalexandris.net> [2017-10-15 17:57:30
+0200]:
> >
> >> ...in improving https://github.com/NikosAlexandris/i.landsat.import
> >
> >
> > The script will import scenes in independent Mapsets. This is contra to
> > the "convention" to import data (first) in the PERMANENT Mapset.
>
> IMHO there is no such convention.
> To use different mapsets is perfectly fine.
> The PERMANENT mapset is ideal for base cartography shared with all other
mapsets.
>
> Markus
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20171114/92944536/attachment.html>