HICO processing problem

Use this Forum to find information on, or ask a question about, NASA Earth Science data.
Post Reply
junzhao
Posts: 28
Joined: Fri Oct 07, 2011 11:21 am America/New_York

HICO processing problem

by junzhao » Mon Aug 26, 2013 6:23 am America/New_York

Hi Sean,
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.

Any solution?

Thanks.

Jun

Tags:

OB.DAAC - SeanBailey
User Services
User Services
Posts: 1313
Joined: Wed Sep 18, 2019 6:15 pm America/New_York
Answers: 1
Been thanked: 1 time

HICO processing problem

by OB.DAAC - SeanBailey » Mon Aug 26, 2013 2:43 pm America/New_York

Jun,

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
values retrieved.

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.

Sean

junzhao
Posts: 28
Joined: Fri Oct 07, 2011 11:21 am America/New_York

HICO processing problem

by junzhao » Tue Aug 27, 2013 2:21 am America/New_York

Hi Sean,
Thanks for you reply.
Regarding the l1mapgen call, the default bands used are 665, 560, and 412. Then which option should be set to use the following bands: 639, 553, and 461 nm ?

Jun

OB SeaDAS - dshea
Subject Matter Expert
Subject Matter Expert
Posts: 240
Joined: Thu Mar 05, 2009 10:25 am America/New_York

HICO processing problem

by OB SeaDAS - dshea » Tue Aug 27, 2013 8:34 am America/New_York

Right now our processing code only reads in the following wavelengths:

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.

don

OB.DAAC - SeanBailey
User Services
User Services
Posts: 1313
Joined: Wed Sep 18, 2019 6:15 pm America/New_York
Answers: 1
Been thanked: 1 time

HICO processing problem

by OB.DAAC - SeanBailey » Tue Aug 27, 2013 8:38 am America/New_York

type l1mapgen at the command prompt to get a usage statement.

Post Reply