Opened 7 years ago
Last modified 5 years ago
#3544 new defect
i.atcorr does not work for user defined spectral conditions
Reported by: | spartina | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.8.3 |
Component: | Imagery | Version: | 7.4.0 |
Keywords: | atmospheric correcction | Cc: | |
CPU: | x86-64 | Platform: | MSWindows 7 |
Description
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
Attachments (2)
Change History (3)
by , 7 years ago
Attachment: | relative_spectral_response_median_per_ps_sat_group.xlsx added |
---|
by , 7 years ago
Attachment: | planet_cpp_template.txt added |
---|
create_iwave file for satallite of interest
comment:1 by , 5 years ago
Milestone: | → 7.8.3 |
---|
RelativeSpectralResponse