[GRASS-dev] [GRASS GIS] #3544: i.atcorr does not work for user defined spectral conditions

GRASS GIS trac at osgeo.org
Tue Apr 10 04:29:41 PDT 2018


#3544: i.atcorr does not work for user defined spectral conditions
-------------------------------------+-------------------------
 Reporter:  spartina                 |      Owner:  grass-dev@…
     Type:  defect                   |     Status:  new
 Priority:  normal                   |  Milestone:
Component:  Imagery                  |    Version:  7.4.0
 Keywords:  atmospheric correcction  |        CPU:  x86-64
 Platform:  MSWindows 7              |
-------------------------------------+-------------------------
 I've been trying to get a new satellite sensor working for atmospheric
 correction. It seems like when adding the sensor to the i.atcorr tool it
 will always result in all null values unless it falls in the same exact
 spectral wavelengths as an already defined satellite. Furthermore, when
 trying to define my own spectral conditions (instead of adding a new
 satellite to the tool) by accurately defining my own filter function in
 the 6s parameters the results are always null unless I use values of an
 already defined satellite. The company provides the needed relative
 spectral response of each of the bands for their satallites. I've run the
 create_iwave.py tool and added the necessary code to each file. I've
 triple checked the cpp_template create by the create_iwave tool and found
 no noticeable errors. I've tried this with grass 7.4 and grass 7.5 and on
 a few different windows computers. I'm trying to get this code to work for
 a big project I'm working on

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3544>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list