When HICO L1B data were processed in command line using l2gen (SeaDAS v7.0), there are no valid data in the output hdf file.
The command I run was
l2gen ifile=H2013206053504.L1B_ISS ofile=test.hdf
When l1mapgen command was run, there was no output. I just used
l1mapgen ifile=H2013206053504.L1B_ISS ofile=test.png
The error read "Number of output pixels (2 of a possible 180000) < threshold (0.10%). Output image not generated".
I am using Ubuntu 13.04.
- User Services
- Posts: 1428
- Joined: Wed Sep 18, 2019 6:15 pm America/New_York
- Been thanked: 1 time
We have not started any work on HICO L2 processing. While the code functions, there has been no attempt to vicariously calibrate the data.
For the scene you have, the cloud albedo values have a minimum around 0.05 - the default cloud albedo threshold (used for cloud flagging)
is 0.027, so the entire scene is flagged as cloudy. Setting the albedo value to 0.055 allowed the scene to be processed - but I wouldn't trust the
As for l1mapgen, seems the code wasn't able to identify reasonable lon/lat limits for the scene and processed the entire globe. A HICO scene is
rather small when compared to the globe :wink: If you set the north, south, west, east extents in the call to l1mapgen the scene maps nicely.
- Subject Matter Expert
- Posts: 256
- Joined: Thu Mar 05, 2009 10:25 am America/New_York
- Been thanked: 2 times
Lambda(1) = 413
Lambda(2) = 443
Lambda(3) = 490
Lambda(4) = 510
Lambda(5) = 560
Lambda(6) = 620
Lambda(7) = 665
Lambda(8) = 681
Lambda(9) = 709
Lambda(10) = 754
Lambda(11) = 762
Lambda(12) = 779
Lambda(13) = 865
Lambda(14) = 885
Lambda(15) = 900
Until we add better handling of hyper spectral sensors, you are limited to these wavelengths for HICO.