Forum

Your help was crucial to find the problem. The issue was the way I was opening the data: using python, I was treating the files as if they were netcdf, opening them with xarray.open_mfdataset However, for HDF files, this should not be done, I came to learn. I adapted a script that I found in another...

also checked there is no report regarding this issue at daily L3 data issues webpage: https://atmosphere-imager.gsfc.nasa.gov/issues/daily

Several things: 1) stored CTT ranging between 14960 and 14840 would yield actual CTT ranging 298.4 to 299.6 K. That is less than 2K variability (in a given day) for the entire globe... The example of page 30 in the document "MODISCloudOpticalPropertyUserGuideFinal_v1.1_1.pdf" shows CTT ran...

I still have an issue: a global snapshot of the stored CTT ranges between 14960 and 14840. scale_factor = 0.009999999776482582 add_offset = -15000.0 I use the conversion equation: CTT_actual = scale_factor * ( CTT_stored - add_offset ) now CTT ranges between 0.4 and 1.6 but with units in K this is c...

I am using daily L3 products (for example MYD08_D3.A2003039.061.2018005124705.hdf) I open the attributes of CTT variable (Cloud_Top_Temperature_Mean.attrs), and what I get is: {'valid_range': array([ 0, 20000], dtype=int16), 'long_name': 'Cloud Top Temperature: Mean', 'units': 'Degrees Kelvin', 'Lev...