[GRASS-dev] [GRASS GIS] #2305: i.atcorr landsat8 support

#2305: i.atcorr landsat8 support
-------------------------+--------------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
     Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: unspecified
Keywords: Landsat | Platform: Unspecified
      Cpu: Unspecified |
-------------------------+--------------------------------------------------
*) Added support for Landsat 8
*) Corrected docs: Second WV entry was QuickBird in reallity about
according to IWave.h/cpp

I just added support for Landsat 8 bands in i.atcorr; It needs some
testning now

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305&gt;
GRASS GIS <http://grass.osgeo.org>

#2305: i.atcorr landsat8 support
-------------------------------+--------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
     Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: unspecified
Keywords: Landsat, i.atcorr | Platform: Unspecified
      Cpu: Unspecified |
-------------------------------+--------------------------------------------
Changes (by neteler):

  * keywords: Landsat => Landsat, i.atcorr

Comment:

Unfortunately the patch cannot be applied as is due to tab/space
confusion. You need to use

svn diff imagery/i.atcorr > i.atcorr_ls8.patch

and then upload to preserve the formatting. Thanks!

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>

#2305: i.atcorr landsat8 support
-------------------------------+--------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
     Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: unspecified
Keywords: Landsat, i.atcorr | Platform: Unspecified
      Cpu: Unspecified |
-------------------------------+--------------------------------------------

Comment(by neteler):

Uploaded to trunk in r60610 (please test this new Landsat8 support)

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305#comment:2&gt;
GRASS GIS <http://grass.osgeo.org>

#2305: i.atcorr landsat8 support
-------------------------------+--------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
     Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: unspecified
Keywords: Landsat, i.atcorr | Platform: Linux
      Cpu: x86-64 |
-------------------------------+--------------------------------------------
Changes (by ychemin):

* cc: ychemin (added)
  * platform: Unspecified => Linux
  * cpu: Unspecified => x86-64

Comment:

Replying to [comment:2 neteler]:
> Uploaded to trunk in r60610 (please test this new Landsat8 support)

iwave 115 gets through but 116 and more give Unsupported Warning, and
still process.
Band 1 processed without warning gives 10^-9 values, bands with warning
give null data.

LC81270512014115LGN00.toar.1 LC81270512014115LGN00.surf.1
iwave no: 115
Atmospheric correction...
  100%
Atmospheric correction complete.
LC81270512014115LGN00.toar.2 LC81270512014115LGN00.surf.2
iwave no: 116
WARNING: Unsupported iwave value: 116
Atmospheric correction...
  100%
Atmospheric correction complete.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305#comment:3&gt;
GRASS GIS <http://grass.osgeo.org>

#2305: i.atcorr landsat8 support
-------------------------------+--------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
     Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Keywords: Landsat, i.atcorr | Platform: Linux
      Cpu: x86-64 |
-------------------------------+--------------------------------------------
Changes (by neteler):

  * version: unspecified => svn-trunk

Comment:

Try r60761.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305#comment:4&gt;
GRASS GIS <http://grass.osgeo.org>

#2305: i.atcorr landsat8 support
-------------------------------+--------------------------------------------
Reporter: vesnikos | Owner: grass-dev@…
     Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Keywords: Landsat, i.atcorr | Platform: Linux
      Cpu: x86-64 |
-------------------------------+--------------------------------------------

Comment(by ychemin):

Fixed indeed ! Thanks.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305#comment:5&gt;
GRASS GIS <http://grass.osgeo.org>

#2305: i.atcorr landsat8 support
--------------------------+-------------------------------------------------
  Reporter: vesnikos | Owner: grass-dev@…
      Type: enhancement | Status: closed
  Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Resolution: fixed | Keywords: Landsat, i.atcorr
  Platform: Linux | Cpu: x86-64
--------------------------+-------------------------------------------------
Changes (by neteler):

  * status: new => closed
  * resolution: => fixed

Comment:

Backported to relbr7 in r61314.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305#comment:6&gt;
GRASS GIS <http://grass.osgeo.org>

#2305: i.atcorr landsat8 support
--------------------------+-------------------------------------------------
  Reporter: vesnikos | Owner: grass-dev@…
      Type: enhancement | Status: closed
  Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Resolution: fixed | Keywords: Landsat, i.atcorr
  Platform: Linux | Cpu: x86-64
--------------------------+-------------------------------------------------

Comment(by nikosa):

While scripting an i.landsat.atcorr module, wouldn't it be "ok" to keep
the official order of Landsat's 8 band_designation? Currently, in i.atcorr
the order is:

1: 115, 2: 116, 3: 117, 4: 118, 8: 119, 5: 120, 9: 121, 6: 122, 7: 123

Why not:

1: 115, 2: 116, 3: 117, 4: 118, 5: 119, 6: 120, 7: 121, 8: 122, 9: 123

?

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305#comment:7&gt;
GRASS GIS <http://grass.osgeo.org>

#2305: i.atcorr landsat8 support
--------------------------+-------------------------------------------------
  Reporter: vesnikos | Owner: grass-dev@…
      Type: enhancement | Status: closed
  Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Resolution: fixed | Keywords: Landsat, i.atcorr
  Platform: Linux | Cpu: x86-64
--------------------------+-------------------------------------------------

Comment(by neteler):

Replying to [comment:7 nikosa]:
> While scripting an i.landsat.atcorr module, wouldn't it be "ok" to keep
the official order of Landsat's 8 band_designation?

Yes, would make more sense.

> Currently, in i.atcorr the order is:
>
> 1: 115, 2: 116, 3: 117, 4: 118, 8: 119, 5: 120, 9: 121, 6: 122, 7: 123
>
> Why not:
>
> 1: 115, 2: 116, 3: 117, 4: 118, 5: 119, 6: 120, 7: 121, 8: 122, 9: 123
>
> ?

I guess that's how the original patch was provided. Can you manage to
prepare a patch for the modification?

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305#comment:8&gt;
GRASS GIS <http://grass.osgeo.org>

The band follow that order (if i remember correcty) because they are
ordered by ascending wavelength since its the same scema the other
sensors follow.

No reason not to change the order if its needed

On Tue, Nov 25, 2014 at 7:10 PM, GRASS GIS <trac@osgeo.org> wrote:

#2305: i.atcorr landsat8 support
--------------------------+-------------------------------------------------
  Reporter: vesnikos | Owner: grass-dev@…
      Type: enhancement | Status: closed
  Priority: normal | Milestone: 7.0.0
Component: Imagery | Version: svn-trunk
Resolution: fixed | Keywords: Landsat, i.atcorr
  Platform: Linux | Cpu: x86-64
--------------------------+-------------------------------------------------

Comment(by neteler):

Replying to [comment:7 nikosa]:
> While scripting an i.landsat.atcorr module, wouldn't it be "ok" to keep
the official order of Landsat's 8 band_designation?

Yes, would make more sense.

> Currently, in i.atcorr the order is:
>
> 1: 115, 2: 116, 3: 117, 4: 118, 8: 119, 5: 120, 9: 121, 6: 122, 7: 123
>
> Why not:
>
> 1: 115, 2: 116, 3: 117, 4: 118, 5: 119, 6: 120, 7: 121, 8: 122, 9: 123
>
> ?

I guess that's how the original patch was provided. Can you manage to
prepare a patch for the modification?

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2305#comment:8&gt;
GRASS GIS <http://grass.osgeo.org>