Hi Juan,
Can you please give the download link for your images, Could you also check the output of i.landsat.toar for them and tell if reflectance ranges are valid/logic. Thank you, Yann From: Juan Benavides Duque [mailto:[email protected]] Sent: Thursday, May 26, 2011 11:38 PM To: Chemin, Yann (IWMI) Cc: Markus Metz; Elena Mezzini Subject: Re: [GRASS-user] Re: i.atcorr returns all NULL values I tried Yann's code for the i.atcorr on some Landsat TM5 images It worked very nice for images taken after 1995 but before that still returns null values when running i.atcorr for bands 1 and 2 I used TM5 scenes from the same location for 1986, 1989, and 1996 and the first two (1986 and 1989) had the same problem with the null values... sorry I can provide a way to fix it but I hope somebody will juan c On Tue, May 24, 2011 at 3:49 AM, Chemin, Yann (IWMI) <[email protected]> wrote: >Each created visibility map holds only one value r.mapcalc expression="visibility=${vis_list[$i]}" --overwrite so why not just use this visibility value as input in the >parameter file instead of creating a map where all cells have the same value? Yes, this is a valid point, the script is designed to (hopefully soon) encompass raster maps of visibility data (maybe interpolated...), so this is a placeholder for the next steps. -----Original Message----- From: Markus Metz [mailto:[email protected]] Sent: Tuesday, May 24, 2011 12:52 PM To: Chemin, Yann (IWMI) Cc: [email protected]; Elena Mezzini; Markus Neteler Subject: Re: [GRASS-user] Re: i.atcorr returns all NULL values On Mon, May 23, 2011 at 9:36 PM, Markus Neteler <[email protected]> wrote: > Hi Yann, > > On Mon, May 23, 2011 at 5:07 AM, Chemin, Yann (IWMI) <[email protected]> wrote: >> p192 r030 image of July 2003 of Italy (L5TM) successfully corrected >> for band 1 and 2. >> The following script works well in GRASS GIS Trunk SVN. > > (better send as attachment since a series of line breaks got broken) > > ... >> # For i.atcorr scripting >> #----------------------------------------------------- >> vis_list=(10 10 8 9.7 15 8 7 10 10 9.7 12 9.7 7 12 12 12 3 15 12 9.7 >> 6 15) vis_len=${#vis_list[*]} echo $vis_len > > ... this is not clear to me: why so many values and where do they > originate from? Since we have only 6 channels to work with... > Moreover, how can it be possible that visibility is different for different channels of the same scene? From the documentation it seems that visibility is related to aerosol concentration at 550nm which can not possibility be different for different bands of the same scene. Each created visibility map holds only one value r.mapcalc expression="visibility=${vis_list[$i]}" --overwrite so why not just use this visibility value as input in the parameter file instead of creating a map where all cells have the same value? Markus M _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
