[GRASS-user] question on Landsat 8 processing

Carlos Henrique Grohmann de Carvalho carlos.grohmann at gmail.com
Tue Jun 18 05:35:48 PDT 2019


Indeed it needs ALL bands.

I used this module in class a couple of weeks ago. You need to import and
use all bands, including the panchromatic.

Carlos



On Tue, Jun 18, 2019 at 9:32 AM Veronica Andreo <veroandreo at gmail.com>
wrote:

> Seems to me that the module needs all Landsat bands. Try importing all of
> them
>
> Vero
>
> El lun., 17 jun. 2019 a las 15:54, Gabriel Cotlier (<gabiklm01 at gmail.com>)
> escribió:
>
>> Dear Vero, Nikos and Markus,
>>
>> I'm trying to get an NDVI from different preprocessing atmospheric
>> correction methods DOS1, DOS2, DOS 2b, DOS3, DOS4. However, unsuccessfully,
>> I'm not being able to run my supposed workflow on GRASS GIS which is:
>>
>> Step 1. DN to TOA Radiance ( *i.landsat.toar*)
>> Step 2. TOA Radiance to Land Surface Reflectance  (*i.atcorr*)
>>
>> that thought maybe is the correct workflow for Landdsat 8 Level 1
>> products, maybe is not?
>>
>> Since I need it only for Band 4 and Band 5 I proceeded as follows:
>>
>> 1. in a grassdata directory named with the correspondent Landsat 8 scene
>> "LC82270832018074LGN00" I put Band 4 and Band 5 together with the MTL
>> metadata txt file.
>>
>> 2. set a "Location" for this data set using Band 4 data by reading
>> projection and Datum from Band 4.
>>
>> 3.started grass gis and d.rast for displaying the already automatically
>> loaded Band 4
>>
>> 5. import with r.in.gdal Band 5 using Band 5 complete name as was Band 4
>> loaded "LC82270832018074LGN00_B5"
>>
>> [image: image.png]
>> 6. I changed working directory to where the data is:
>>
>> [image: image.png]
>> 7. in command line (the withe one in grass interface) I tried to
>> *i.landsat.toar* for obtaining TOA Radiance as follows :
>>
>> i.landsat.toar -r input=LC82270832018074LGN00_B
>> output=TOAR_LC82270832018074LGN00_B metfile=LC82270832018074LGN00_MTL.txt
>> sensor=oli8 date=2018-03-15 sun_elevation=45.06637424
>> product_date=2018-03-20
>>
>> and the resulting error was:
>>
>> [image: image.png]
>>
>> I do not really understand what could be happening related to the bands
>> names?
>>
>> Thanks a lot I will appreciate a way to solve this problem. May target is
>> to get finally both bands 4 and 5 radiometrically callibrated and further
>> atmospherically corrected with *i.atcorr*  using different DOS methos.
>>
>> Thanks a lot again for the help and guidance.
>>
>> Gabriel
>>
>> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user



-- 
Prof. Carlos Henrique Grohmann
Institute of Energy and Environment - Univ. of São Paulo, Brazil
- Digital Terrain Analysis | GIS | Remote Sensing -

http://carlosgrohmann.com
http://orcid.org/0000-0001-5073-5572
________________
Can’t stop the signal.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190618/79ccafed/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 21501 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190618/79ccafed/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 22349 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190618/79ccafed/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 10708 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190618/79ccafed/attachment-0005.png>


More information about the grass-user mailing list