<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Juan,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Can you please give the download link for your images,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Could you also check the output of i.landsat.toar for them and tell if reflectance ranges are valid/logic.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thank you,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yann<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Juan Benavides Duque [mailto:jbenavid@siu.edu] <br><b>Sent:</b> Thursday, May 26, 2011 11:38 PM<br><b>To:</b> Chemin, Yann (IWMI)<br><b>Cc:</b> Markus Metz; Elena Mezzini<br><b>Subject:</b> Re: [GRASS-user] Re: i.atcorr returns all NULL values<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><br>I tried Yann's code for the i.atcorr on some Landsat TM5 images<br><br>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 <br><br>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... <br><br>sorry I can provide a way to fix it but I hope somebody will<br><br>juan c <br><br><br><br><br><o:p></o:p></p><div><p class=MsoNormal>On Tue, May 24, 2011 at 3:49 AM, Chemin, Yann (IWMI) <<a href="mailto:Y.Chemin@cgiar.org">Y.Chemin@cgiar.org</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'>>Each created visibility map holds only one value r.mapcalc<br>expression="visibility=${vis_list[$i]}" --overwrite so why not just use<br>this visibility value as input in the >parameter file instead of<br>creating a map where all cells have the same value?<o:p></o:p></p></div><p class=MsoNormal>Yes, this is a valid point, the script is designed to (hopefully soon)<br>encompass raster maps of visibility data (maybe interpolated...), so<br>this is a placeholder for the next steps.<o:p></o:p></p><div><p class=MsoNormal><br>-----Original Message-----<br>From: Markus Metz [mailto:<a href="mailto:markus.metz.giswork@googlemail.com">markus.metz.giswork@googlemail.com</a>]<br>Sent: Tuesday, May 24, 2011 12:52 PM<br>To: Chemin, Yann (IWMI)<br>Cc: <a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>; Elena Mezzini; Markus Neteler<o:p></o:p></p></div><div><div><p class=MsoNormal>Subject: Re: [GRASS-user] Re: i.atcorr returns all NULL values<br><br>On Mon, May 23, 2011 at 9:36 PM, Markus Neteler <<a href="mailto:neteler@osgeo.org">neteler@osgeo.org</a>><br>wrote:<br>> Hi Yann,<br>><br>> On Mon, May 23, 2011 at 5:07 AM, Chemin, Yann (IWMI)<br><<a href="mailto:Y.Chemin@cgiar.org">Y.Chemin@cgiar.org</a>> wrote:<br>>> p192 r030 image of July 2003 of Italy (L5TM) successfully corrected<br>>> for band 1 and 2.<br>>> The following script works well in GRASS GIS Trunk SVN.<br>><br>> (better send as attachment since a series of line breaks got broken)<br>><br>> ...<br>>> # For i.atcorr scripting<br>>> #-----------------------------------------------------<br>>> 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<br>>> 6 15) vis_len=${#vis_list[*]} echo $vis_len<br>><br>> ... this is not clear to me: why so many values and where do they<br>> originate from? Since we have only 6 channels to work with...<br>><br>Moreover, how can it be possible that visibility is different for<br>different channels of the same scene? >From the documentation it seems<br>that visibility is related to aerosol concentration at 550nm which can<br>not possibility be different for different bands of the same scene.<br>Each created visibility map holds only one value r.mapcalc<br>expression="visibility=${vis_list[$i]}" --overwrite so why not just use<br>this visibility value as input in the parameter file instead of creating<br>a map where all cells have the same value?<br><br>Markus M<br>_______________________________________________<br>grass-user mailing list<br><a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></body></html>