<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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="NO-BOK" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">I would like to second Markus on that one.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">We considered using AERONET for atmospheric correction in i.atcorr, but ended up using arbitrary / averaged values, cause AERONET data for our locations was very, very sparse and showed
very high variation.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">So, in a module, that compiles a 6s-parameter file, I would be happy if there was an option for providing manual values, ideally accompanied by fetching AOT values from other sources
(e.g. AEORNET, MODIS).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Could be like in v.to.rast, where you have a “use” option (here e.g. with “value”, “aeronet”, “modis” choice), accompanied by “aot_value” to provide values manually, “aot_aeronet” option
to provide input file or “aot_modis” which could be a raster map option the module extracts values from (producing that map(s) would be a user task).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Just a suggestion.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Stefan<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> grass-dev <grass-dev-bounces@lists.osgeo.org>
<b>On Behalf Of </b>Markus Metz<br>
<b>Sent:</b> onsdag 27. juni 2018 14:24<br>
<b>To:</b> Roberta Fagandini <robifagandini@gmail.com><br>
<b>Cc:</b> GRASS developers list <grass-dev@lists.osgeo.org><br>
<b>Subject:</b> Re: [GRASS-dev] compile 6S library in GRASS<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
On Wed, Jun 27, 2018 at 2:16 PM, Roberta Fagandini <<a href="mailto:robifagandini@gmail.com">robifagandini@gmail.com</a>> wrote:<br>
><br>
> I'm trying to create an automatic procedure to retrieve all the input parameters for the control file of i.atcorr.<o:p></o:p></p>
<div>
<p class="MsoNormal">> I need py6S because I want to automatically read and compute AOT at 550nm from an AERONET file.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">With AOT you mean aerosol optical thickness right? This is user input to i.atcorr. There are various sources for AOT at 550nm, e.g. MODIS.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Anyway, it is probably much easier to to write your own routine to read the AERONET file and get the corresponding formula for AOT than to fight with 51821 lines of Fortran source code that is numerically unstable. Maybe I can help with
getting AOT at 550nm from an AERONET file avoiding the Fortran version of 6S.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Markus M<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">><br>
> 2018-06-27 14:01 GMT+02:00 Moritz Lennert <<a href="mailto:mlennert@club.worldonline.be">mlennert@club.worldonline.be</a>>:<br>
>><br>
>> On 27/06/18 13:54, Roberto Marzocchi wrote:<br>
>>><br>
>>><br>
>>> Il giorno mer 27 giu 2018 alle ore 13:47 Markus Metz <<a href="mailto:markus.metz.giswork@gmail.com">markus.metz.giswork@gmail.com</a> <mailto:<a href="mailto:markus.metz.giswork@gmail.com">markus.metz.giswork@gmail.com</a>>> ha scritto:<br>
>>><br>
>>> Hi Roberta,<br>
>>><br>
>>> On Wed, Jun 27, 2018 at 1:20 PM, Roberta Fagandini<br>
>>> <<a href="mailto:robifagandini@gmail.com">robifagandini@gmail.com</a> <mailto:<a href="mailto:robifagandini@gmail.com">robifagandini@gmail.com</a>>> wrote:<br>
>>> ><br>
>>> > Hi all!<br>
>>> > I need to compile the 6S library in GRASS in order to install the<br>
>>> python library Py6S [0].<br>
>>><br>
>>> do you really need Py6S? Can't you use i.atcorr instead?<br>
>>><br>
>>><br>
>>> She use Py6S to calculate imput for i.atcorr<br>
>><br>
>><br>
>> That seems a bit overkill: why use Py6S to then use i.atcorr ? What are you trying to get from Py6S ?<br>
>><br>
>> Moritz<br>
>><br>
><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>