[GRASS-dev] nc_spm_08_grass8?

Vaclav Petras wenzeslaus at gmail.com
Thu Sep 9 09:19:33 PDT 2021


On Thu, Sep 9, 2021 at 4:46 AM Maris Nartiss <maris.gis at gmail.com> wrote:

> Hello Anna, Veronica.
>
> 2021-09-08 23:09 GMT+03:00, Veronica Andreo <veroandreo at gmail.com>:
>
> > Indeed, we have a problem if all examples using Landsat will stop working
> > in grass 8, so if this is the case, then we might need a new version of
> the
> > sample data which by the way might also include the MODIS LST mapset (~10
> > Mb) to do some time series stuff.
>
> A new version of sample dataset would be good. Still existing version
> also works OK as long as you do an extra step of assigning band
> references at the first time. You'll find usage examples in manual
> pages of i.cluster with following in i.maxlik; and a full example in
> i.smap.
>

In the documentation, we moved from (5 calls):

```
g.region raster=lsat7_2002_10
i.group group=lsat7_2002 subgroup=res_30m input=...
v.to.rast input=training output=training use=cat label_column=label
i.gensigset trainingmap=training group=lsat7_2002 subgroup=...
i.smap group=lsat7_2002 subgroup=res_30m signaturefile=...
```

to (16 calls):

```
g.mapset mapset=PERMANENT
r.support map=lsat7_2002_10 bandref=TM7_1
r.support map=lsat7_2002_20 bandref=TM7_2
r.support map=lsat7_2002_30 bandref=TM7_3
r.support map=lsat7_2002_40 bandref=TM7_4
r.support map=lsat7_2002_50 bandref=TM7_5
r.support map=lsat7_2002_61 bandref=TM7_61
r.support map=lsat7_2002_62 bandref=TM7_62
r.support map=lsat7_2002_70 bandref=TM7_7
r.support map=lsat7_2002_80 bandref=TM7_8
g.mapset mapset=user1
g.region raster=lsat7_2002_10
i.group group=lsat7_2002 subgroup=res_30m input=...
v.to.rast input=training output=training use=cat label_column=label
i.gensigset trainingmap=training group=lsat7_2002 subgroup=...
i.smap group=lsat7_2002 subgroup=res_30m signaturefile=...
```

This seems to be making GRASS more difficult to use instead of making it
easier to use or at least keeping the status quo.

Changing the sample dataset sounds like hiding the issue rather than
solving it. Having an ultra convenient sample dataset doesn't make the
software easier to use.

Additionally, given that the band references seem highly experimental, I
don't think they should be required for any workflow at least from the user
point of view.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20210909/205538fd/attachment.html>


More information about the grass-dev mailing list