modis_L1B output depends on MODIS granule date ?
Posted: Thu Oct 20, 2022 6:31 am America/New_York
Good morning,
I used modis_L1B on two MODIS granules, respectively from 2020 and 2022, but the output is not the same :
modis_L1B A2020168174500.L1A_LAC A2020168174500.GEO outputs only one file : AQUA_MODIS.20200616T174500.L1B.hdf
whereas modis_L1B A2022285162000.L1A_LAC A2022285162000.GEO outputs 3 files :
AQUA_MODIS.20221012T162000.L1B.hdf
AQUA_MODIS_HKM.20221012T162000.L1B.hdf
AQUA_MODIS_QKM.20221012T162000.L1B.hdf
I'm using SeaDAS 8.2.0, tag T2022.15
Info returned by modis_GEO is :
MODIS Aqua L1B version 6.2.1_obpg, built Jun 27 2022 12:15:36
scan: 0 out of 203 Thu Oct 20 10:08:33 2022
...
As I'm using l2gen with resolution=250, the QKM file is needed in input :
-W- /home/dshea/focs/oel_hdf4/libl1/l1_hmodis_hdf.c:239: Cannot open file: ./AQUA_MODIS_QKM.20200616T174500.L1B.hdf
File not found: ./AQUA_MODIS_QKM.20200616T174500.L1B.hdf
Processing at 250m resolution requires a QKM file to be present in the same directory as the 1KM L1B file.
This result seems weird, could the modis_L1B script for SeaDAS 8.2.0, tag T2022.15 have such behaviour ?
Thank you for your help,
Jacques
I used modis_L1B on two MODIS granules, respectively from 2020 and 2022, but the output is not the same :
modis_L1B A2020168174500.L1A_LAC A2020168174500.GEO outputs only one file : AQUA_MODIS.20200616T174500.L1B.hdf
whereas modis_L1B A2022285162000.L1A_LAC A2022285162000.GEO outputs 3 files :
AQUA_MODIS.20221012T162000.L1B.hdf
AQUA_MODIS_HKM.20221012T162000.L1B.hdf
AQUA_MODIS_QKM.20221012T162000.L1B.hdf
I'm using SeaDAS 8.2.0, tag T2022.15
Info returned by modis_GEO is :
MODIS Aqua L1B version 6.2.1_obpg, built Jun 27 2022 12:15:36
scan: 0 out of 203 Thu Oct 20 10:08:33 2022
...
As I'm using l2gen with resolution=250, the QKM file is needed in input :
-W- /home/dshea/focs/oel_hdf4/libl1/l1_hmodis_hdf.c:239: Cannot open file: ./AQUA_MODIS_QKM.20200616T174500.L1B.hdf
File not found: ./AQUA_MODIS_QKM.20200616T174500.L1B.hdf
Processing at 250m resolution requires a QKM file to be present in the same directory as the 1KM L1B file.
This result seems weird, could the modis_L1B script for SeaDAS 8.2.0, tag T2022.15 have such behaviour ?
Thank you for your help,
Jacques