Hi Stefan,
I'm happy to inform you that ASTER support has been added to i.atcorr
in grass6.5.svn as well as grass7. As always, if you could test it out
and let us know if you encounter any issues it would be greatly
appreciated.
Cheers,
Mike
Markus Neteler wrote:
On Wed, Jun 10, 20
Michael,
On Wed, Jul 29, 2009 at 6:49 PM, Michael Perdue wrote:
> In the mean time
> I'll try to figure out GeomCond.cpp so I can simply submit a patch.
maybe I did it wrong but I simply added the last sensor:
http://trac.osgeo.org/grass/changeset/35851#file1
Markus
_
If you can interpolate and organize the data as follows, I can
incorporate it fairly painlessly;
/* not real data */
sensor= Spot 2
band= 3 hvr2
Lower edge wavelength = 0.715
Upper edge wavelength = 0.9175
Spectral Response =
., .0001, .0001, .0002, .0004, .0005, .0007, .0009
.0012, .0014,
Hi Mike
thanks for this supporting information. I will start the interpolation. Is
there any prefered method for this? Can I use a bilinear approach.
I think this is as far as I can take it though - as I have no understanding
of lwave.cpp and the file construct. Will it be ok to post a txt file on
Hi Andy,
Yes, it looks like the right info for the SPOT sensor platforms.
Iwave.cpp expects the data to be in 2.5nm increments so you will have
to interpolate the data to the correct interval. It's a bit tedious,
but is straight forward. I might be able to dedicate some time to it,
but won
Hi All,
Im just adding to this discusssion. I would be interested in using i.atcorr
with SPOT 2, 3, 4 and 5. I have found a file on the
http://www.spotimage.com/web/en/555-spot-images.php website that contains
the spectral sensitivity data. Is this the same as the spectral profile? It
looks like t
Hi Markus,
Here is a text file with everything organized as I think it should be.
I didn't add the this Iwave.cpp to submit a patch as I wasn't really
sure how to modify GeomCond.cpp.
Cheers,
Mike
On 26-Jul-09, at 1:34 PM, Markus Neteler wrote:
Great - the header of Iwave.cpp contains in
On Mon, Jul 27, 2009 at 6:25 AM, Michael Perdue wrote:
> I'm guessing that the values in these two assignments represent the left and
> right edges of the Spectral response curves. Is that correct?
> static const float wli[7] =
> { 0.4350, 0.5000, 0.6150, 0.7400, 1.5050, 2.0150, 0.5025 };
> static
I'm guessing that the values in these two assignments represent the
left and right edges of the Spectral response curves. Is that correct?
static const float wli[7] = { 0.4350, 0.5000, 0.6150, 0.7400, 1.5050,
2.0150, 0.5025 };
static const float wls[7] = { 0.5200, 0.6225, 0.7025, 0.9125, 1.79
On Sun, Jul 26, 2009 at 9:31 PM, Michael Perdue wrote:
> Organized like this?
> /* 1st spectral band of enhanced thematic mapper plus */
> static const float sr1[35] = {
> .0160, .0710, .2870, .6665, .7920, .8570, .8390, .8060,
> .7790, .8460, .9010, .8995, .8900, .8510, .8750, .8930,
Organized like this?
/* 1st spectral band of enhanced thematic mapper plus */
static const float sr1[35] = {
.0160, .0710, .2870, .6665, .7920, .8570, .8390, .8060,
.7790, .8460, .9010, .8995, .8900, .8510, .8750, .8930,
.8840, .9300, .9580, .9540, .9800, .9750, .9650, .9
On Sun, Jul 26, 2009 at 9:03 PM, Michael Perdue wrote:
> I believe these are what you're looking for.
> http://www.science.aster.ersdac.or.jp/en/about_aster/sensor/excel/SPEC_ROFILES.LZH
Good:
I managed to uncompress it with "lha e SPEC_ROFILES.LZH" and
the spreadsheet table seems to contain the r
I believe these are what you're looking for.
http://www.science.aster.ersdac.or.jp/en/about_aster/sensor/excel/SPEC_ROFILES.LZH
Cheers,
Mike
On 26-Jul-09, at 10:56 AM, Markus Neteler wrote:
Hi Stefan,
On Sun, Jul 26, 2009 at 1:27 PM, Stefan Sylla
wrote:
Hi Markus,
can you explain what
Hi Stefan,
On Sun, Jul 26, 2009 at 1:27 PM, Stefan Sylla wrote:
>
> Hi Markus,
>
> can you explain what the filter functions should contain? I guess it is
> something about the sensor calibration parameters. I could give you that,
> but I need to know the details.
it is a table of values describi
Hi Markus,
can you explain what the filter functions should contain? I guess it is
something about the sensor calibration parameters. I could give you that,
but I need to know the details.
Best regards
Stefan
Markus Neteler wrote:
>
> On Wed, Jun 10, 2009 at 3:27 PM, sela wrote:
>>
>> Hi,
>
On Wed, Jun 10, 2009 at 3:27 PM, sela wrote:
>
> Hi,
>
> has anyone ever performed atmospheric correction with i.atcorr on ASTER L1B
> images? I am wondering because there are no templates for geometrical
> conditions or sensor bands (like there are for Landsat, Modis, AVHRR etc.).
If you can find
Well, I finally found out that the 6S algorithm of i.atcorr is not to be
performed only with the header-file information of the Aster-L1B Images. So
I switched to an easier image-based operation (the landsat standard-equation
for the CosT-approach) which was very easy to perform with r.mapcalc.
G
Hi,
has anyone ever performed atmospheric correction with i.atcorr on ASTER L1B
images? I am wondering because there are no templates for geometrical
conditions or sensor bands (like there are for Landsat, Modis, AVHRR etc.).
I am not sure if all the information required for the i.atcorr 6S algor
18 matches
Mail list logo
