Ocean Color Forum - Not logged in
I downloaded meris RR level 2 products from the ESA website (merci), format N1.
The product contains chlorophyll data (called algal_1 and algal_2), suspended sediment (total_susp)
and yellow substance (yellow_subs).
I displayed the above 4 constituents using SeaDAS.
Values for algal_1, algal_2 and total_susp were in the expected range.
However, a rather large number of pixels had negative yellow substance values.
ESA documentation indicates that the logarithm of the 4 constituents is stored.
In the SeaDAS code (src/c4idl/libmerisread/epr_dddb.c) I could find reference to this
logarithm transform for algal_1, algal_2 and total_susp, but not for yellow_subs.
Can someone confirm that one should apply 10^yellow_subs to get the proper value for yellow_subs in SeaDAS
or am I mistaking?
The example N1 file I have shows that yellow_substance is NOT store as the log10 of the value.
However, this file predates the latest MERIS product spec document I found, which as you point
out, indicates that yellow_substance IS stored as the log10 of the value. Seems a change was
made. So, I suppose the answer to your question is sometimes...
It seems I have to perform the 10^ operation myself whenever needed.
The MERIS L2 data include product confidence descriptors.
For yellow substance it is PCD_16 (see epr_dddb.c).
Is PCD_16 somehow included in the l2_flags provided by SeaDAS?
SeaDAS will display the MERIS L2 flags via:
Utilities->Data Visualization->L2 Flags Display
And, yes, the PCD_16 flag is available.
Glad that PCD flags are available.
On the Level 2 Flags Display I can switch between
"l2gen L2 Flags", "MODIS SST Flags" and "MERIS L2 Flags".
The first item for "l2gen L2 Flags" is ATMFAIL,
whereas the first item for "MERIS L2 Flags" is CLOUD.
Does this mean that whenever I load the variable l2_flags of MERIS L2 data into memory, using the IDL routine get_meris_data,
the first bit is the CLOUD flag.
whereas in case of SeaDAS or MODIS data, using the appropriate reading routine, the first bit of l2_flags corresponds to the ATMFAIL flag?
Yes. The load routine does nothing to the l2 flag array when it is read in,
the L2 flags display function simply interprets a MERIS l2 flags array
differently from a SeaWiFS l2 flags array - because they're different
I applied MERIS L2 flags (in Level 2 Flags Display) on a MERIS L2 images in GUI (e.g. cloud, land, etc). However, is there the function in command line? I searched but couldn't find it. Thanks.
Thanks for your answer.
Actually, I already tried 'load_graph' command.
But it doesn't work well unlike GUI.
For example, after loading ['chlor_a','l2_flags] from MERIS L-2 files..
I successfully displayed land (or cloud) over the chl-a image. But when I tried it in command..
>load_graph, 2, fbuf=1, ftype='BAND', bit=, color=
it doesn't work. (I'm using seadas 6.1 on mac os-x).
am I wrong?
bit 1 is ATMFAIL. bit 10 is CLDICE.
yes, bit 1 is ATMFAIL for 'l2gen L2 flags'.
but for 'MERIS L2 Flags', it looks different. is that right?
Correct. I was lost in a fog, saw l2_flags and assumed you were using OBPG processed L2 files.
The MERIS l2_flags are indeed different. After fiddling with the GUI and load_graph a bit, I'm
not convinced the GUI is entirely correct.
I was able to confirm that load_graph can produce flag overlays for the MERIS products, however.
I don't have time to dig too deeply into it (the MERIS flag scheme is a little more complicated than
the simple 32 bitwise values used by OBPG), but here are a few key flags and their corresponding
bit value (replace the bit value with BIT in the following: load_graph, 2, fbuf=1, ftype='BAND', bit=[BIT], color=)
Land bit 24
Ocean bit 22
Coastline bit 14
High Glint bit 3
Suspect bit 21 (I think)
Cloud bit 1
It looks now working. Thanks a lot.