Hello,
I have a question about l2gen output file. In the L2 netcdf output file I see longitudes slon, clon, and elon. And similar for latitude. I use clon and clat of each pixel as geolocation of that pixel when using in calculations. Is this a correct assumption?
Thanks.
Amita
getanc.py
-
OB.DAACx - SeanBailey
- Posts: 1519
- Joined: Wed Sep 18, 2019 6:15 pm America/New_York
- Been thanked: 9 times
getanc.py
No. There are full lat/lon arrays in the L2 files. The s/c/e variants are a holdover from the original SeaWiFS L2 files, which didn't have full lat/lon arrays. (Rather subsampled arrays). You can ignore the s/c/e arrays.
Sean
Sean
-
OB.DAACx - SeanBailey
- Posts: 1519
- Joined: Wed Sep 18, 2019 6:15 pm America/New_York
- Been thanked: 9 times
getanc.py
It would be a problem if you were....lonlat2pixline works on the unprojected L1/2 files.
There is no consistent method to identify clouds in L1 data. For the three missions you're interested in, there is some hope, though....
OLCI includes a qualityFlags.nc file that has, among others, a flag for "bright" targets.
OLI are TIFF images, but does include a "BQA" image that includes a bit for clouds
MSI are JPEG2000 images, but also include in the directory a subdirectory under "GRANULE" called QI_DATA that includes a set of XML files with flag information....good luck with that...
Sean
There is no consistent method to identify clouds in L1 data. For the three missions you're interested in, there is some hope, though....
OLCI includes a qualityFlags.nc file that has, among others, a flag for "bright" targets.
OLI are TIFF images, but does include a "BQA" image that includes a bit for clouds
MSI are JPEG2000 images, but also include in the directory a subdirectory under "GRANULE" called QI_DATA that includes a set of XML files with flag information....good luck with that...
Sean