* Ken Mankoff <mankoff@gmail.com> [2016-06-23 14:38:21 -0400]:
Is there a way to only process 1 band with i.landsat.toar? It would
save some time.
I don't think so. But it would be nice to have it.
Related to this, the documentation for the "-n" flag in i.landsat.toar
is: "Input raster maps use as extension the number of the band instead
the code". I'm not sure what that means, and can't find clarification
in the manual page.
Take for example the landsat scene LE71840332009140ASN00. Its bands
"codes" are 1, 2, 3, 4, 5, 61, 62, 7 and 8. In total, 9 bands.
Assuming a common prefix, for these codes, inside a GRASS Mapset, would
be the letter "B" (so we have B1, B2, B3, B4, B5, B61, B62, B7, B8),
then the `input=` parameter for i.landsat.toar would be exactly "B".
Given an `output=` string "R" (say as a short for reflectance), the
derived raster maps would be named R1, R2, R3, R4, R5, R61, R62, R7, R8.
Now, using -n and keeping the same `input=` and `output=`, the expected
list of names (of the input bands), would be simply B1, B2, B3, B4, B5,
B6, B7, B8, B9. The names of the derived maps would, though, still be
the same... R1, ..., R61, R62, R7 up to R8.
I guess it has to do with how you import, and name, the bands in GRASS'
db in first place.
Nikos