Docstoc

NASA HDFEOS_ver6.0-lizzie

Document Sample
NASA HDFEOS_ver6.0-lizzie Powered By Docstoc
					     When analyzing NASA HDF4 and HDF-EOS2 files distributed by NASA data cen
     users may need to make extra efforts to retrieve the physically meaningful inform
     metadata information is stored inside some files. Case 2: for some other files, a
     in a physically meaningful manner. Case 3: attributes in some files do not compl
     Case 4: some files use techniques that end users may not be familiar with, altho
     provides comprehensive and detailed descriptions of the listed phenomena base
     from the URL(http:// .....)(URL added later) . The primary purpose of this docum
     archiving. We understand that some descriptions may not be accurate. Users s
     document carefully. We list the issues in four categories to help data centers to
     Category One : Wrong information
     Category Two : Need to obtain information
     outside the HDF files
     Category Three: Non-standard

     Category Four: Special files


     Descriptions of each column of the work sheet
     Each worksheet is named after different NASA Data Centers. Eight data centers
A.
     NSIDC, worksheet, GHRC, LAADS, LaRC, PO DAAC and listed inrespectively.
     In each LP DAAC, the name of the NASA Data Center is OBPG the upper left
B.   also given.
     As mentioned above, all special issues are organized into four categories. The k
C.
     the Data Center Name. Because column names are ordered as project or missio
     Next to the 'Data Center Name', thethere might be more than one 'Projects/Missions
     'notes'. Specifically, column 'issue' provides a brief summary for the special features.
     the same issues are grouped under the column 'product name', a typical example file
D.   readers download the example file . The detailed description for the issues can be fou
     products was downloaded and reviewed to see if the issue is resolved. This informat
     issues, in order to make the table more concise, the full list of these products is put u
     Within the fourth category 'Special Files', some issues are highlighted by either red o
E.   by rows that are highlighted in the red color may require extra efforts to retrieve info
     that are highlighted in green color may actually help the end users to retrieve the co
DF-EOS2 files distributed by NASA data centers, we found that there are a small amount of special files that end
 s to retrieve the physically meaningful information out of these files. Here illustrates a few cases. Case 1: wrong
e some files. Case 2: for some other files, additional information outside the files are required to retrieve the data
Case 3: attributes in some files do not comply with CF conventions, which gain its popularity among end users.
hat end users may not be familiar with, although the techniques may greatly help the data storage. This work sheet
 d descriptions of the listed phenomena based on sample special files obtained from the NASA data collections
d later) . The primary purpose of this document is to provide references for NASA data centers to do data
e descriptions may not be accurate. Users should evaluate the descriptions of these special files listed in this
 es in four categories to help data centers to identify them easily.
             The information provided by NASA HDF4 and HDF-EOS2 files may be wrong.
             To retrieve some key information(lat,lon etc coordinate infomration) from NASA HDF4 and HDF-EOS2
             files users may rely on additional information outside the HDF files.
             The Information provided by NASA HDF4 and HDF-EOS2 files may not be presented in a standard way
             such as following the common usage of the HDF-EOS2 library or following some widely used
             NASA HDF4 and HDF-EOS2 files arrange data and metadata in a way that users may need to be
             aware in order to retrieve the correct information.




rent NASA Data Centers. Eight data centers are included in this Excel speadsheet file. They are GES DISC,
NASA Data Center is OBPG the upper left
LaRC, PO DAAC and listed inrespectively. corner. The URL of the corresponding website of each data center is

 es are organized into four categories. The key words that describes each category are given in 'column A' beneath
 lumn names are ordered as project or mission in one data center, all the issues are further organized by different
ere might be more than one 'Projects/Missions'(if applicable), 'product name', 'Issue', 'File', 'URL', 'Description' and
 vides a brief summary for the special features. Products may share commons issues. Accordingly, the products that have
e column 'product name', a typical example file is given under the column 'file' and the column 'URL' in order to help
he detailed description for the issues can be found under the column 'Description'. The latest version of some typical
ed to see if the issue is resolved. This information falls into the column 'notes'. Since many products share the common
e concise, the full list of these products is put under the column 'notes' as well.
 es', some issues are highlighted by either red or green background. According to our best knowledge, the files described
  color may require extra efforts to retrieve information from these files. On the other hand, the files described by rows
 y actually help the end users to retrieve the corresponding informtion easily. For other 'Special Files', we simply leave
GESDISC                             Projects/Missions     Product names




Wrong Information            AIRS



                                                        AIRS L3.CO2Std031,
                                                        AIRS L3 RetQuant
                                                        AIRS L2.CC*.v4,AIRS
                             AIRS                       L2.RetStd*.v4, AIRS
                                                        L2.RetSup*.v4

                                                        3A46, 2A25, CSH
Need to obtain information
outside the HDF files
                             TRMM
                                                        3B43, 3B42


                                                        3A46


                                                        AIRS L3.CO2Std031,
Non-Standard                 AIRS                       AIRS L3 RetQuant




                                                        AIRS L2G.Precip




                                                        AIRS L2.CC




                             AIRS                       AIRS L2.RetStd, AIRS
                                                        L2.RetSup

                                                        AIRS L3.RetStd
Special Files
                                                        AIRS_L3.CO2Std AIRS
                                                        L1B.AIRS, AIRS_Rad
Special Files




                        AIRS L3.RetQuant

                        AIRS_L1B files

                        All MERRA file
                MERRA

                        All MERRA file

                TRMM
                        1B21, 1C21, 2B31
                                     Issue




Wrong parameters in StructMetadata

Data fields contain 'Fill Values', but there is neither a 'Fill_Value' attribute
nor a 'missing value' attribute.
Data fields contain 'Fill Values', but there is neither a 'Fill_Value' attribute
nor a 'missing value' attribute.


The users are not able to find latitude and longitude information from the
file.




Non-Standard Dimension name




There are two or more pairs of data fields that look like latitude and
longitude




The variable names include characters that are not underscore '_' or
alphanumeric. CF conventions require the usage of only underscore of
alphanumeric for variable and attribute names.




One latitude and longitude field pair for the whole file


Latitude and longitude contains 'Fill Value'
Latitude and longitude values retrieved directly from the latitude and
longitude fields are different from those retrieved from the
structMetadata
The latitude and longitude are stored as 1D array each and the number of
the elments for each array is the same.

Duplicated Latitude and longitude information

StructMetadata has parameter 'GridOrigin=HDFE_GD_LL' rather than
default value 'GridOrigin=HE5_HDFE_GD_UL'


Unclear Latitude and Longitude information
                               File




AIRS.2005.01.01.L3.CO2Std031.v5.4.12.67.X09261141415.hdf


AIRS.2002.12.31.001.L2.CC_H.v4.0. 21.0.G06100185050.hdf

3A46.080101.2.HDF



3B43.070901.6A.HDF


3A46.080101.2.HDF




AIRS.2005.01.01.L3.CO2Std031.v5.4.12.67.X09261141415.hdf




AIRS.2005.12.31.L2G.Precip_Est.v1.0.1.0. G08009215125.hdf




AIRS.2002.12.31.001.L2.CC_H.v4.0. 21.0.G06100185050.hdf




AIRS.2003.02.05.001.L2.RetStd_H.v4.0.21.0.G06066135630.hdf

AIRS.2002.08.24.L3.RetStd_H008.v4.0.21.0.G06104133343.hdf


AIRS.2005.01.01.L3.CO2Std031.v5.4.12.67.X09261141415.hdf
AIRS.2009.12.01.L3.RetQuant_IR031.v5.0.14.0.G10006163547.hdf

AIRS.2005.12.31.L1B.Cal_Subset.v5.0.16.0.G08008000255.hdf

MERRA300.prod.assim.inst3_3d_chm_Ne.20021201.hdf


MERRA300.prod.assim.inst3_3d_chm_Ne.20021201.hdf


1B21_CSI.990906.10217.KORA.6.HDF
                                Description                                                      notes
Parameter 'UpperLeftPoint/LowerRight Mtrs' should be packed in
degrees, minutes, seconds format (DDDMMMSSS.SS). In this file, this
parameter doesn't follow the DDDMMMSSS.SS format. In
DDDMMMSSS.SS format, the value of UpperLeftPoint should be (-
180000000.000000,90000000.000000). But in this file, the
UpperLeftPointMtrs is (-180.000000,89.500000)', which only shows the
degrees. This will generate the wrong latitude and longitude values if
one uses the HDF-EOS2 library to retrieve the latitude and longitude
values.                                                                        no change in latest version

                                                                                AIRS_v5.0 does not have the same
The fillvalue of the datafield 'CCfinal_Resid' is -9999.0                      issue.

The fillvalue of the datafield 'ssmiData' is -9999.0                       no change in latest version
The information of latitude and longitude can only be found from:
http://disc.sci.gsfc.nasa.gov/additional/faq/precipitation_faq.shtml#lat_l
on                                                                         no change in latest version
The information of latitude and longitude can only be found from:
http://disc.sci.gsfc.nasa.gov/precipitation/documentation/TRMM_READ
ME/TRMM_3A46_readme.shtml                                                  no change in latest version
The default dimension name of latitude and longitude for HDF-EOS2
grids should be 'XDim' and 'YDim'. But the dimension names of latiude
and longitude in this file are ‘LatDim’ and ‘LonDim’ .
                                                                               no change in latest version
There are two pairs of latitude and longitude fields in this file. The first
pair "Latitude, Longitude", has fill values. The second pair
"GridCenterLatitude, GridCenterLongitude", doesn't have fill value,
which is more likely to represent the real latiude and longitude Fields.
The users may still need to guess what the real latitude and longitude
are.                                                                           didn't find the latest files
The group name, L2_Standard_cloud-cleared_radiance_product,
contains a special character (hyphen ‘-‘) and therefore requires a
modification (L2_Standard_cloud_cleared_radiance_product) for some
software tools to access the fields under this group.                          no change in latest version
The group name, L2_Standard_atmospheric&surface_product, contains a
special character (ampersand ‘&‘) and therefore requires a modification
(L2_Standard_atmospheric_surface_product) for some software tools to
access the fields under this group.
                                                                               no change in latest version
There are 5 groups in this file. All of them share the latitude and            The latest file we found is just from
longitude which are stored under the group 'location'                          Year 2002


The latitude and longitude fields contain fill value -9999.0                   no change in latest version
This grid's latiude and longitude values can be retrieved from the
StructMetadata. It also has two fields called 'LatCenter' and 'LonCenter'.
The latitude and longitude fields retrieved from the StructMetadata are
different than 'LatCenter' and 'LonCenter'. Users may get confused about
which one to choose.                                                       no change in latest version
1-D latitude and longitude may be difficult for tools to visualize the data.
                                                                               no change in latest version
Variables 'XDim' and 'Ydim' are duplications of latitude and longitude
variables.                                                                     no change in latest version
The end users should be aware to retrieve the GridOrigin correctly
instead of assuming the default value of "HE5_HDFE_GD_UL".
                                                                               no change in latest version
Both latitude and longitude are stored in one 3-D variable ’geolocation’.
Users need to make extra efforts to retrieve individual latitude and
longitude values.                                                         no change in latest version
NSIDC                        Projects/Missions      Product names



Need to obtain information
                             AMSR
outside the HDF files
                                                 Many AMSR L2 or L3
                                                 products




                             MODIS

                                                 All MODIS

                                                 MOD10A1, MOD10A2
                                                 MOD29E1D,MOD29P1
                                                 D, MOD29P1N

                                                 AE_L3_DailyLand
                                                 AE_L3_SeaIce12km,
                                                 AE_L3_SeaIce25km,
                                                 AE_L3_SeaIce6km




                                                 AE_L3_DailyLand
                             AMSR

Special files




                                                 AE_L3_RainGrid
                                                 AE_L3_5DaySnow,
                                                 AE_5DSno,
                                                 AE_L3_DailySnow,
                                                 AE_L3_MonthlySnow
       All NISE

       All NISE


NISE


       All NISE




       All NISE
Issue                                             File




Data fields contain 'Fill Values', but there is
neither a 'Fill_Value' attribute nor a 'missing
value' attribute.                                 AMSR_E_L3_DailyOcean_V03_20020619.hdf




The data for all data fields only contain
discrete value rather than continuous value.      MOD29P1D.A2005018.h03v08.005.2007348222738.hdf

Sinusodial projection                             MOD10A1.A2000065.h00v08.005.2008237034422.hdf

LAMAZ projection                                  MOD29E1D.A2000055.005.2006268025009.hdf

CEA projection                                    AMSR_E_L3_DailyLand_V06_20050118.hdf


PS projection                                     AMSR_E_L3_SeaIce12km_V11_20050118.hdf
The variable names include characters that
are not underscore '_' or alphanumeric. CF
conventions require the usage of only
underscore of alphanumeric for variable and
attribute names.                                  AMSR_E_L3_DailyLand_V06_20050118.hdf




longitude may need additional processing
because it starts from 0 and ends at 360.         AMSR_E_L3_RainGrid_V06_200206.hdf




LAMAZ projection                                  AMSR_E_L3_5DaySnow_V09_20050126.hdf
The data for all data fields only contain
discrete value rather than continuous value.   NISE_SSMIF13_20050424.hdf

LAMAZ projection                               NISE_SSMIF13_20050424.hdf




The metadata information regarding the data
fields is stored as the file attribute.     NISE_SSMIF13_20050424.hdf




The same field name is shared across different
vgroups.                                       NISE_SSMIF13_20050424.hdf
Description




The fillvalue of the data field 'Very_low_res_sst' is -
9999.0, etc.

For data field 'Sea_Ice_by_Reflectance', the value of data
field is given by attribute 'Key': 0=missing data, 1=no
decision, 11=night, 25=land, 37=inland water, 39=ocean,
50=cloud, 200=sea ice, 253=land mask, 254=ocean mask,
255=fill; the application should be aware of this. The
application should be very careful when visualizing the
data since the data values should not be interpolated as
normal fields.
Extra efforts should be made for some tools to retrieve the
latitude and longitude.
The HDF-EOS2 library can retrieve the latitude and
longitude correctly.
Extra efforts should be made for some tools to retrieve the
latitude and longitude.

Extra efforts should be made for some tools to retrieve the
latitude and longitude.


Some data fields contain special characters (period ‘.‘ and
Parentheses '()') and therefore require modification (e.g
A_TB36_5H__Res_1) for some tools to read these fields.

Parameter
'UpperLeftPointMtrs=(0.000000 ,70000000.000000) and
LowerRightMtrs=(360000000 .000000,-
70000000.000000)'. That means longitude ranges from 0
degree to 360 degree. However, many tools expect that
the range of longitude is from -180 degree to 180 degree.


The HDF-EOS2 library cannot retrieve the latitude and
longitude correctly
For data field 'Age', the value of data field is given by
attribute 'age_grid_key': 0-254        age in days since date
of file; 255      filler value for corners and undetermined
data pixels
The HDF-EOS2 library is not able to retrieve latitude and
longitude correctly

Because some data fields share common attributes, these
attributes are stored as the global attributes rather than as
the attributes of individual SDS objects. For example, the
global attribute 'age_grid_key' describes two data fields,
both named 'Age' under two different vgroups.

Tools have to figure out the full path of a data field
because the data field name may be shared by another
field under a different vgroup. Under most cases, the data
field can be uniquely identified by its full path.
notes
Other AE_L3_DailyOcean,
AE_L2A_BrightnessTemperatures,
AE_L3_MonthlyOcean, AE_L2_Ocean,
AE_L2_Rain,AE_L3_RainGrid, AE_L3_SeaIce12km,
AE_L3_SeaIce25km, AE_L3_SeaIce6km,
AE_L3_WeeklyOcean;                           no
change in latest version




no change in latest version

no change in latest version

no change in latest version

no change in latest version


no change in latest version




no change in latest version




no change in latest version




no change in latest version
no change in latest version

no change in latest version




no change in latest version




no change in latest version
LP DAAC                   Projects/Missions       Product names




                          MCD




                                              MCD43C3




                                              MOD13C2
Wrong Information

                                              MOD13C2
                          MOD




                                              MOD43C3, MOD43C1




                                              MOD14


                          MYD
                                              MYD14




                                              MOD11_L2
                          MOD
Need to obtain
information outside the
HDF files
                          MOD
Need to obtain
information outside the
HDF files
                                MOD13C2


                          MYD
                                MYD11_L2
                          MCD
                                MCD43A*,MCD43B*




                                Most MOD products
                          MOD
                                MOD09GA, MOD09GHK,
                                MODMGGAD
Special files

                                MOD12Q1, MOD14,
                                MOD15A2




                          MYD
                                Most MYD products
                                MYD09GA, MYD09GHK,
                                MYD09GQK, MYD09GST,
                                MYDMGGAD
                Issue                                       File




Wrong parameters in StructMetadata    MCD43C1.A2006353.004.2007012185705.hdf




                                      MOD13C2.A2007001.005.2007108072029.hdf
Wrong parameters in StructMetadata
                                      MOD13C2.A2007001.005.2007108072029.hdf




                                      MOD43C1.A2006353.004.2007008092801.hdf
FP_latitude and FP_longitude, which
are equvalient to latitude and
longitude, has zero length in one
dimension.                            MOD14.A2007101.0345.005.2007101114133.hdf
FP_latitude and FP_longitude, which
are equvalient to latitude and
longitude, has zero length in one
dimension                             MYD14.A2007273.0255.005.2007275112449.hdf

This swath uses the dimension map
technique
                                      MOD11_L2.A2007278.0350.005.2007280073443.hdf
The value of parameter 'Projection' is
missing. Users have to check 'MODIS
Products Table' to find the type of
projection.                              MOD13C2.A2007001.005.2007108072029.hdf




This swath uses the dimension map        MYD11_L2.A2007093.0735.005.2007101061952.hdf

Sinusodial projection                    MCD43A1.A2007257.h00v08.005.2007281122810.hdf




Sinusodial projection                    MOD09A1.A2006361.h00v08.004.2007006103308.hdf




Hybrid file                               MOD09GA.A2007268.h10v08.005.2007272184810.hdf
The data for all data fields only contain
discrete value rather than continuous
value.                                    MOD12Q1.A2004001.h01v08.004.2006117172443.hdf




Sinusodial projection                    MYD09A1.A2007273.h03v07.005.2007285103507.hdf


Hybrid file                              MYD09GA.A2007069.h00v10.005.2007072094611.hdf
                            Description

Parameter 'UpperLeftPoint/LowerRight Mtrs' should be packed in
degrees, minutes, seconds format (DDDMMMSSS.SS). In this file,
this parameter doesn't follow the DDDMMMSSS.SS format. In
DDDMMMSSS.SS format, the value of UpperLeftPoint should be (-
180000000.000000,90000000.000000). But in this file, the
UpperLeftPointMtrs is (-180.000000,89.500000)', which only shows
the degrees. This will generate the wrong latitude and longitude
values if the application uses the HDF-EOS2 library to retrieve the
latitude and longitude values.

Parameter 'UpperLeftPoint/LowerRight Mtrs' should be packed in
degrees, minutes, seconds format (DDDMMMSSS.SS). In this file,
this parameter doesn't follow the DDDMMMSSS.SS format. In
DDDMMMSSS.SS format, the value of UpperLeftPoint should be (-
180000000.000000,90000000.000000). But in this file, the
UpperLeftPointMtrs is (-1,1)', which seems using the default values
provided by the HDF-EOS2 library. This will generate the wrong
latitude and longitude values if one uses the HDF-EOS2 library to
retrieve the latitude and longitude values.

The value of parameter 'projection' is blank

Parameter 'UpperLeftPoint/LowerRight Mtrs' should be packed in
degrees, minutes, seconds format (DDDMMMSSS.SS). In this file,
this parameter doesn't follow the DDDMMMSSS.SS format. In
DDDMMMSSS.SS format, the value of UpperLeftPoint should be (-
180000000.000000,90000000.000000). But in this file, the
UpperLeftPointMtrs is (-180.000000,89.500000)', which only shows
the degrees. This will generate the wrong latitude and longitude
values if one uses the HDF-EOS2 library to retrieve the latitude and
longitude values.




There are no data values inside these fields.




There are no data values inside these fields.
Users need either to find the corresponding HDF-EOS2 files that
provide the latiude and longitude values for the data fields or to
calculate the latitude/longitude based on the dimension map
parameters.
Users need either to find the corresponding HDF-EOS2 files that
provide the latiude and longitude values for the data fields or to
calculate the latitude/longitude based on the dimension map
parameters.
Extra efforts should be made for some tools to retrieve the latitude
and longitude.




Extra efforts should be made for some tools to retrieve the latitude
and longitude.
HDF4 APIs are used to add information in the HDF-EOS2 file.
Accordingly, some SDS and vdata objects do not belong to any grid
and cannot be retrieved by the HDF-EOS2 library.
For data field 'Land_Cover_Type_1', each specific value is provided
by one attribute, such as 'water' is 0; 'evergreen needleleaf forest' is
1; '_FillValue' is 255 and so forth.




Extra efforts should be made for some tools to retrieve the latitude
and longitude.
HDF4 APIs are used to add information in the HDF-EOS2 file.
Accordingly, some SDS and vdata objects do not belong to any grid
and cannot be retrieved by the HDF-EOS2 library.
                        notes




no change in the latest version




Corrected in the latest version
(MOD13C2.A2010213.005.2010263091009.hdf)
Corrected in the latest version
(MOD13C2.A2010213.005.2010263091009.hdf)




no change in the latest version




no change in the latest version




no change in the latest version




no change in the latest version
Corrected in latest version
(MOD13C2.A2010213.005.2010263091009.hdf)




no change in latest version

no change in latest version

MYD09GA, MYD09GHK, MYD09GQ, MYD09GQK,
MYD09GST, MYD09Q1, MYD11A*, MYD11B1,
MYD13A*, MYD13Q1, MYD14A*, MYD15A2,
MYD17A2, MYDMGGAD; no change in latest version




no change in the latest version


The latest file I found is just from Year 2004

MYD09A1, MYD09GHK, MYD09GQ, MYD09GQK,
MYD09GST, MYD09Q1, MYD11A1, MYD11A2,
MYD11B1, MYD13*, MYD14*, MYD15A2, MDY17A2,
MYDMGGAD; no change in the latest version


no change in the latest version
GHRC
                           Projects/Missions    product names                     Issue

                                                                Data fields contain 'Fill Values', but
                          NAMMA
                                                                there is neither a 'Fill_Value' attribute
Need to obtain                                 NAMMA_APR-2      nor a 'missing value' attribute.
information outside the
HDF files                                                       The latitude and longitude provided by
                          LIS SCF                               the file is (-0.25, 0.25, 0.75, …, 359.25)
                                                                and (-0.25, 0.25, 0.75, …, 179.25),
                                               All LISOTD       which is not accurate.




                          CAMEX-4
                                                                There are two pairs of latitude and
                                                                longitude and both of them have non-
                                                                Standard Latitude and Longitude Field
Special files                                  MASL1B           name
                       File



namma_apr2_20060819_151913_41.hdf




LISOTD_HRAC_V2.2.hdf




MASL1B_05921_01_20050618_1421_1433_V01.hdf
                             Description



The fill value of data field 'zhh14' is -9999, etc.

The correct end points of latitude and longitude are: N: 90.0; S: -
90.0; E: 180.0; W: -180.0. Users have to refer to website:
'ftp://ghrc.nsstc.nasa.gov/pub/doc/lis_climatology/' for correct
latitude and longitude




The file contains two pairs of latitude and longitude. The latitude
and longitude names are either preceded by ‘Aircraft’ or by
‘Pixel’. Moreover, users need to know which pair of latitude and
longitude to use.
                                  notes



The latest file we found is just from Year 2006




no change in the latest version

1. The AircraftLatitude and AircraftLongitude are 1-D arrays (length
4436) containing the position of the aircraft (along with
AircraftAltitude, AircraftHeading, AircraftPitch and AircraftRollCount).
Meanwhile, the PixelLatitude and PixelLongitude are 2-D arrays
(length 4436 x width 716) with positions of pixels in the “swath” of
data obtained during the flight – in CalibratedData array (et al.) (4436
x 716 x 50 channels). (this was the answer from a NASA scientist) 2.
The latest file I found from data center data pool is only year 2001)
  personal notes (need to be deleted later)




ftp://ghrc.nsstc.nasa.gov/pub/doc/camex4/c4emas/c4emas_dataset.html
LAADS                        Projects/Missions   Product Names

                                                 MOD021KM,
                                                 MOD05_L2,
                                                 MOD06_L2,
                                                 MOD35_L2




                                                 MOD02HKM,
                                                 MOD02QKM
                                                 MOD01,
                                                 MOD02OBC,
                             MOD
                                                 MODCSR


                                                 MOD021KM,
                                                 MOD02HKM,
                                                 MOD02QKM,
                                                 MOD02SSH
                                                 MOD07_L2,
                                                 MODARNSS.Abrac
                                                 os_Hill,
                                                 MODATML2,
Need to obtain information                       MOD08
outside the HDF files
                                                 MDY021KM,
                                                 MYD05_L2,
                                                 MYD06_L2,
                                                 MYD35_L2




                                                 MYD02HKM,
                                                 MYD02QKM
                                                 MYD01,
                                                 MYD02OBC,
                             MYD
                                                 MYDCSR




                                                 MYD021KM,
                                                 MYD02SSH
                      MYD07_L2,
                      MYD021KM,
                      MYD02HKM,
                      MYD02QKM,
                      MYDARNS




                      MODARNSS
                MOD
                      MODARNSS,
                      MOD021KM,
                      MOD02HKM,
                      MOD02QKM,
Non-Standard          MOD02SSH




                MYD   MYDARNSS




                      MYD swath files




                      MOD04_l2,
                      MOD05_L2
                MOD
                      MODASRVN


                      MODATML2




                      MYD04_L2,
Special files
                      MYD05_L2


                      MDY02HKM
                MYD

                      MYDATML2
MYD




      MYDATML2
                Issue                                            File




                                    MOD021KM.A2000055.0000.005.2010041143816.hdf
This swath uses the dimension map




                                    MOD02HKM.A2000055.0005.005.2010029230803.hdf

No latitude and longitude
information                         MOD01.A2000055.0155.005.2010030164343.hdf




There are several 'scales' and
'offsets' attributes for some
variables.                          MOD021KM.A2000055.0000.005.2010041143816.hdf




the usage of scale and offset
attributes                          MOD021KM.A2000055.0000.005.2010041143816.hdf




                                    MYD021KM.A2002226.0000.005.2009193222735.hdf
This swath uses the dimension map




                                    MYD02HKM.A2002193.0000.005.2009192212603.hdf

No latitude and longitude
information                         MYD01.A2002233.2055.005.2010057104302.hdf




There are several 'scales' and
'offsets' attributes for some
variables.                          MYD02HKM.A2002193.0000.005.2009192212603.hdf
the usage of scale and offset
attributes                            MYD021KM.A2002226.0000.005.2009193222735.hdf




Non-standard hybrid file              MODARNSS.Abracos_Hill.A2000080.1515.005.2007164153544.hdf


units' attribute for latitude and
longitude does not follow CF
conventions                           MODARNSS.Abracos_Hill.A2000080.1515.005.2007164153544.hdf




Non-standard hybrid file              MYDARNSS.Barrow.A2002184.2200.005.2007051063709.hdf

units' attribute for latitude and
longitude does not follow CF
conventions                           MYDARNSS.Barrow.A2002184.2200.005.2007051063709.hdf




special usage of scale and offset
attributes                            MOD04_L2.A2000055.0010.005.2006253050115.hdf

Sinusodial projection                 MODASRVN.Arica.A2000055.1525.005.2008161234032.hdf
need to apply 'scale_factor' and
'add_offset' attributes on latitude
and longitude                         MODATML2.A2000055.0000.005.2006253045900.hdf




special usage of scale and offset
attributes                            MYD04_L2.A2002184.2200.005.2007068182321.hdf

Latitude and longitude contains 'Fill
Value'                                MYD02HKM.A2002193.0000.005.2009192212603.hdf
need to apply 'scale_factor' and
'add_offset' attributes on latitude
and longitude                         MYDATML2.A2002184.2200.005.2007068182350.hdf
Swath file contains corresponding
geolocation information under group
'Data Fields'                       MYDATML2.A2002184.2200.005.2007068182350.hdf
                    Description                                        notes
Users need either to find the corresponding HDF-
EOS2 files that provide the latiude and longitude
values for the data fields or to calculate the
latitude/longitude based on the dimension map
parameters.                                            no change in the latest version

There are no corresponding HDF-EOS2 files that
provide the latiude and longitude values for the
data fields. Users need to calculate tha latitude and
longitude based on the dimension map parameters. no change in the latest version

There are no latiude and longitude fields and
related information in this file                     no change in the latest version
For data field 'EV_Band26'. One can find the
following 'scales' and 'offsets' attributes.
"radiance_scales", "radiance_offsets",
"reflectance_scales" and "reflectance_offsets", etc.
Users or tools have to figure out which one they
should use.                                          no change in the latest version
The common usage of scale and offset attributes is:
float value = scale*value+offset . However, in this
file, the scale and offset equation is 'float
value=scale*(value-offset) .
                                                      no change in the latest version
There are no corresponding HDF-EOS2 files that
provide the latiude and longitude values for the
data fields. Users need to calculate tha latitude and
longitude based on the dimension map parameters.
.                                                     no change in the latest version

There are no corresponding HDF-EOS2 files that
provide the latiude and longitude values for the
data fields. Users need to calculate tha latitude and
longitude based on the dimension map parameters. no change in the latest version


There are no latitude and longitude fields in this file no change in the latest version
For data field 'EV_500_RefSB'. One can find the
following 'scales' and 'offsets' attributes.
"radiance_scales", "radiance_offsets",
"reflectance_scales" and "reflectance_offsets", etc.
Users or tools have to figure out which one they
should use.                                             no change in the latest version
The common usage of scale and offset attributes is:
float value = scale*value+offset . However, in this
file, the scale and offset equation is 'float
value=scale*(value-offset) .
                                                           no change in the latest version
This is a hybrid file, which means people use the
HDF4 APIs to add information on the HDF-EOS2 file.
Moreover, this swath file does not contain any
group. That's why it falls into 'Non-Standard'
category.                                          no change in the latest version

units' attribute for latitude and longitude is 'degree'.
In CF conventions, the 'unit' of latitude is
"degrees_north" and the 'unit' of longitude is
'degrees_east".                                            no change in the latest version
This is a hybrid file, which means people use the
HDF4 APIs to add information on the HDF-EOS2 file.
Moreover, this swath file does not contain any
group. That's why it falls into 'Non-Standard'
category.                                                  no change in the latest version
units' attribute for latitude and longitude is 'degree'.
In CF conventions, the 'unit' of latitude is               MYD021KM, MYD02HKM,
"degrees_north" and the 'unit' of longitude is             MYD02QKM, MYD02SSH, MYD03;
'degrees_east".                                            no change in the latest version

 File level attribute: 'Slope_and_Offset_Usage'
stores the equation to calculate the data value
based on scale and offset.The equation is: float
value = scale_factor*(stored integer - add_offset)         no change in the latest version
Extra efforts should be made for some tools to
retrieve the latitude and longitude.                       no change in the latest version


                                                           no change in the latest version

 File level attribute: 'Slope_and_Offset_Usage'
stores the equation to calculate the data value
based on scale and offset.The equation is: float
value = scale_factor*(stored integer - add_offset)         no change in the latest version
                                                           Corrected in the latest version
                                                           (MYD02HKM.A2010274.0000.005.2
The geolocation fields contain fill value -9999.0          010274225018.hdf)


                                                           no change in the latest version
Besides latitude and longitude under Geolocation
Fields, there are 'Latitude_10km' and
'Longitude_10km' fields under the vgroup 'Data
Fields' that stored the latitude and longitude values
for data fields . Users do not need to obtain
corresponding geolocation files.                      no change in the latest version
LaRC                       Projects/Missions            Product Names


                          CERES
                                               CER_ES4_TRMM




Wrong Information

                          MOPITT




                                               MOP03
                                               CERES_EBAF_TOA, CER_BDS_Aqua-FM4,
                                               CER_BDS_Terra-FM1, CER_ES4_TRMM-
                                               PFM


                          CERES                CER_ISCCP-D2like-Day,
Need to obtain
                                               CER_SRBAVG3_Aqua, CER_ZAVG_Aqua
information outside the
HDF files


                                               CER_ZAVG_Aqua, CER_AVG_Aqua

                          MOPITT
                                               MOP02, MOP03


                          MISR
                                               MISR_AM1_CGAL


                                               CER_FSW_Aqua, CER_SFC_Aqua
                          CERES
Non-Standard


                                               Many CERES
Non-Standard




               MOPITT


                        MOP03


                        MISR_AM1_CGAL,
                        MISR_AM1_AS_AEROSOL

                        MISR_AM1_AGP




               MISR



                        Many MISR




                        MISR_AM1_CGCL
                        CER-NEWS_CCCM, CER_CRS_Aqua,
                        CER_ES8_Aqua, CER_ES9_Aqua




                        Many CERES




                        Many CERES
                        Many CERES
Special files




                        Many CERES




                CERES




                        Many CERES




                        Many CERES




                        Many CERES




                        Many CERES




                        Many CERES
         CER_ISCCP-D2like-GEO, CER_ES4_Aqua-
         FM3

MOPITT   MOD02
                       Issue



Wrong information in StructMetadata




Wrong information in StructMetadata
Data fields contain 'Fill Values', but there is
neither a 'Fill_Value' attribute nor a 'missing
value' attribute.




The users are not able to find latitude and
longitude information from the file.




Data fields contain 'Fill Values', but there is
neither a 'Fill_Value' attribute nor a 'missing
value' attribute.


Files do not provide latitude and longitude
information for some data fields


The incomplete group name




units' attribute for latitude and longitude does
not follow CF conventions
Non-Standard Dimension name




Hybrid file

Non-standard latitude and longitude name




SOM projection


The variable names include characters that are
not underscore '_' or alphanumeric. CF
conventions require the usage of only underscore
of alphanumeric for variable and attribute names.
The dimension size of latitude and longitude are
same and stored as 1D array




The variable names include characters that are
not underscore '_' or alphanumeric. CF
conventions require the usage of only underscore
of alphanumeric for variable and attribute names.




Non-standard latitude and longitude name
One latitude and longitude field pair for the
whole file




Latitude or longitude needs additional processing




The vgroup names include characters that are not
underscore '_' or alphanumeric. CF conventions
require the usage of only underscore of
alphanumeric for variable and attribute names.




The name of some fields are like latitude and
longitude




The same field name is shared across different
vgroups.




The same sub-vgroup name is shared across
different parent vgroups.




Latitude and longitude contain 'Fill Value'
Latitude and longitude can be condensed from 2-
D array to 1-D array
The latitude and longitude of swath are stored as
1-D arrays rather than 2-D arrays.
                                  File



CER_ES4_TRMM-PFM_Edition1_009001.199808.hdf




MOP03-20000303-L3V1.0.1.hdf


CER_BDS_Aqua-FM4_Edition2_030032.20050329.hdf




CER_ISCCP-D2like-Day_Aqua-FM3-MODIS_Beta1_023030.200612.hdf




CER_ZAVG_Aqua-FM4-MODIS_Edition2B_007005.200503.hdf


MOP02-20000303-L2V5.7.1.val.hdf




MISR_AM1_CGAL_2005_F06_0012.hdf


CER_FSW_Aqua-FM3-MODIS_Edition2C_020026.200712Z60.hdf




CER-NEWS_CCCM_Aqua-FM3-MODIS-CAL-CS_RelA2_903903.20070430.hdf
MOP03-20000303-L3V1.0.1.hdf

MOP03-20090727-L3V1.0.1.hdf




MISR_AM1_AS_AEROSOL_FIRSTLOOK_P106_O043086_F12_0022.hdf

MISR_AM1_AGP_P001_F01_24.hdf




MISR_AEROSOL_P017_O036105_F10_0020_GOM_b64-72.hdf




MISR_AM1_CGAL_2005_F06_0012.hdf

CER-NEWS_CCCM_Aqua-FM3-MODIS-CAL-CS_RelA2_903903.20070430.hdf




CER-NEWS_CCCM_Aqua-FM3-MODIS-CAL-CS_RelA2_903903.20070430.hdf




CER-NEWS_CCCM_Aqua-FM3-MODIS-CAL-CS_RelA2_903903.20070430.hdf
CER-NEWS_CCCM_Aqua-FM3-MODIS-CAL-CS_RelA2_903903.20070430.hdf




CER_AVG_Aqua-FM3-MODIS_Edition2B_007005.200510.hdf




CER_AVG_Aqua-FM3-MODIS_Edition2B_007005.200510.hdf




CER-NEWS_CCCM_Aqua-FM3-MODIS-CAL-CS_RelA2_903903.20070430.hdf




CER_AVG_Aqua-FM3-MODIS_Edition2B_007005.200510.hdf




CER_ISCCP-D2like-Day_Aqua-FM3-MODIS_Beta1_023030.200612.hdf




CER_BDS_Aqua-FM3_Edition1-CV_034038.20091101.hdf
CER_ES4_Aqua-FM3_Edition1-CV_024032.200908.hdf

MOP02-20000303-L2V5.7.1.val.hdf
                        Description                                            notes
The values of parameter 'UpperLeftPointMtrs' and
'LowerRightMtrs' are set to be 'default'. The latitude and
longitude values are incorrect if using the HDF-EOS2 library   The latest file we found is from Year
to retrieve them.                                              1998

Parameter 'UpperLeftPoint/LowerRight Mtrs' should be
packed in degrees, minutes, seconds format
(DDDMMMSSS.SS). In this file, this parameter doesn't follow
the DDDMMMSSS.SS format. In DDDMMMSSS.SS format, the
value of UpperLeftPoint should be (-
180000000.000000,90000000.000000). But in this file, the
UpperLeftPointMtrs is (-180.000000,89.500000)', which only
shows the degrees. The latitude and longitude values are
wrong if using the HDF-EOS2 library to retrieve the latitude
and longitude values.                                        no change in the latest version

The fillvalue of data field 'CERES Viewing Zenith at TOA -
Geocentric' is 3.4028235E38
The informaiton of latitude and longitude can only be found
from:
http://eosweb.larc.nasa.gov/PRODOCS/ceres/SRBAVG/Quali
ty_Summaries/srbavg_ed2d/nestedgrid.html                    no change in the latest version
The informaiton of latitude and longitude can only be found
from Data Products Catalog:
http://eosweb.larc.nasa.gov/PRODOCS/ceres/DPC/DPC_ZAV
G_R5V1.pdf                                                  no change in the latest version

The fillvalue of data field 'Retrieval Bottom Pressure' is -
9999.0                                                       no change in the latest version
This is a derived product, which creates a new group of data
fields that are not belong to any grid. However, it does not
provide latitude and longitude information for these data
fields.                                                      no change in the latest version
HDFVIEW may have not been able to read group name
completely. For example: “TOA Fluxes              (mean std
num_ob” .                                                    no change in the latest version

                                                               CER-NEWS_CCCM, CER_AVG_Aqua,
units' attribute for latitude and longitude is 'degree'. In CF CER_BDS_Aqua, CER_ES9_Aqua,
conventions, the 'unit' of latitude is "degrees_north" and the CER_ISCCP-D2like-GEO; no change in
'unit' of longitude is 'degrees_east".                         the latest version
The default dimension name of latitude and longitude for
HDF-EOS2 grids should be 'XDim' and 'YDim'. But the
dimension names of latiude and longitude in this file are
‘nlat’ and ‘nlon’ .
Dimension names are ‘nlat’ and ‘nlon’ rather than the           The latest file we found is from Year
standard XDim and YDim.                                         2009
People use the HDF4 APIs to add informaiton in the HDF-
EOS2 file. Accordingly, some SDS and vdata objects do not
belong to any grid and cannot be retrieved by the HDF-EOS2
library.                                                        no change in the latest version
The name for latitude and longitude fields are 'GeoLatitude'
and 'GeoLongitude'                                              no change in the latest version

There are two ways to retrieve latitude and longitude for the   MISR_AM1_TC_ALBEDO,
MISR SOM projection files. One way is to caculate the           MISR_AEROSOL, MISR_AM1_AS,
latitude and longitude through HDF-EOS2 library. The other      MISR_AM1_GP_GMP,
way is to obtain the latitude and longitude from the            MISR_AM1_GRP_ELLIPSOI,
corresponding MISR AGP file. Be aware that not all MISR         MISR_AM1_GRP_RCCM; no change
SOM projection files have the corresponding MISR AGP file,      in the latest version
such as MISR_AM1_TC_ALBEDO.

The data field name 'Restrictive albedo first moment - 5
deg', contains a special character (hyphen ‘-‘) and therefore
requires a modification (Restrictive albedo first moment__ 5
deg) for some software tools to access the data field. We
also find the similar problem occur in several other fields.  no change in the latest version
1-D latitude and longitude may be difficult for tools to
visualize the data.                                           no change in the latest version

                                                             CER-NEWS_CCCM, CER_AVG_Aqua,
                                                             CER_CRS_Aqua, CER_ES4_TRMM,
                                                             CER_ES9_Aqua, CER_FSW_Aqua,
The data field name 'CERES TOT filtered radiance - upwards', CER_ISCCP-D2like-Day, CER_ISCCP-
contains a special character (hyphen ‘-‘) and therefore      D2like-GEO, CER_SFC_Aqua,
requires a modification (CERES TOT filtered radiance __      CER_SSF_Aqua, CER_SYN_Aqua,
upwards) for some software tools to access the data field.   CER_ZAVG_Aqua; no change in the
We also find the similar problem occur in some other fields. latest version

                                                            CER-NEWS_CCCM,
                                                            CERES_EBAF_TOA, CER_AVG_Aqua,
                                                            CER_BDS_Aqua, CER_BDS_TRMM,
                                                            CER_BDS_Terra, CER_CRS_Aqua,
                                                            CER_ES4_Aqua, CER_ES8_Aqua,
Latitude and longitude are under the vgroup 'Time and       CER_ES9_Aqua, CER_FSW_Aqua,
Position'. The latitude name is 'Colatitude of CERES FOV at CER_SFC_Aqua, CER_ISCCP-D2like-
surface' and the longitude name is 'Longitude of CERES FOV GEO, CER_SSF_Aqua; no change in
at surface'.                                                the latest version
                                                              CER-NEWS_CCCM, CER_CRS_Aqua,
                                                              CER_ES9_Aqua, CER_FSW_Aqua,
There are 38 vgroups in this file. All data fields of these   CER_SFC_Aqua, CER_SSF_Aqua,
vgroups share the same latitude and longitude which are       CER_SYN_Aqua; no change in the
stored under the vgroup 'Time and Position' .                 latest version
                                                              CER_AVG_Aqua, CER_ES4_Aqua,
Latitude and longitude need following processing: Latitude = CER_ISCCP-D2like-GEO,
90 – Colatitude(original dataset); Longitude ranges from 0 to CER_SSF_Aqua, CER-NEWS_CCCM,
360. Normally users expect the longitude ranging from -180 CER_SYN_Aqua; no change in the
to 180 .                                                      latest version
                                                           CER_AVG_Aqua, CER_BDS_Aqua,
                                                           CER_BDS_TRMM, CER_BDS_Terra,
                                                           CER_CRS_Aqua, CER_ES4_Aqua,
                                                           CER_ES4_TRMM, CER_ES9_Aqua,
                                                           CER_FSW_Aqua, CER_ISCCP-D2like-
The vgroup name 'Cloud Layer - UpperMid' contains a        Day, CER_ISCCP-D2like-GEO,
special character (hyphen ‘-‘) and therefore requires a    CER_SFC_Aqua,
modification (Cloud Layer __UpperMid) for some tools to    CER_SRBAVG3_Aqua,
access information about the vgroup.                       CER_SYN_Aqua, CER_ZAVG_Aqua


                                                               CER-NEWS_CCCM, CER_BDS_Aqua,
The name of some fields are like latitude or longitude, For CER_BDS_TRMM, CER_BDS_Terra,
examples, we find a field name 'Colatitude of subsolar point CER_CRS_Aqua, CER_SSF_Aqua; no
at surface at observation'; this may confuse end users.        change in the latest version
                                                               CER_AVG_Aqua, CER_ES4_Aqua,
Tools have to figure out the full path of a data field because CER_ES9_Aqua,
the data field name may be shared by another field under a CER_SRBAVG3_Aqua,
different vgroup. Under most cases, the data field can be      CER_ZAVG_Aqua; no change in the
uniquely identified by its full path.                          latest version
                                                               CER_ISCCP-D2like-Day,
                                                               CER_ES9_Aqua-FM3, CER_AVG_Aqua-
                                                               FM3, CER_ES4_TRMM-PFM,
                                                               CER_ES4_Aqua-FM3, CER_ISCCP-
                                                               D2like-GEO, CER_SRBAVG3_Aqua-
It is not convenient for some tools to retrieve data fields.   FM3, CER_ZAVG_Aqua-FM4; no

All the value of latitude and longitude are euqal to 'fillvalue' CER_BDS_Aqua, CER_BDS_TRMM,
3.402823E38. That means there's no valid latitude and            CER_BDS_Terra, CER_ES8_Aqua,
longitude for this file                                          CER_SFC_Aqua
 Latitude and longitude are stored as multi-dimensional
arrays. However, the same value repeats for either the
whole column or the whole row. So the multi-dimensional
array can be reduced. In this case, both latitude and
longitude can be reduced to one-dimensional arrays since
the data is the rectangular grids with the geographic
projection. By reducing the dimensionality, the time to
generate plots can be greatly reduced for tools to generate   The latest file we found is from Year
plots or to analyze the data.                                 2009
Most tools cannot visualize swath that store latitude and
longitude in 1-D arrays.                                      no change in the latest version
PO.DAAC
                          Projects/Missions          product names

Wrong Information
                       avhrr                  bsst




                       quikscat               quickscat_L3



Need to obtain
                        seawinds              seawinds_L3E
information outside the
HDF files


                                              nscat_L30
                       nscat



                                              nscat_L17


                       nscat
                                              nscat_L17, nscat_L20
Non-Standard



                       quikscat               quikscat_S2B


                       nscat                  nscat_L17, nscat_L20

                                              nscat_L17, nscat_L20




                       avhrr                  bsst, msk1, msk2, qual




                                              quickscat_L3
Special files

                                              quikscat_S2B
                       quikscat
Special files


                quikscat




                           quikscat_S2B

                           quikscat_S2B


                seawinds
                           seawinds_L3E,
                           seawinds_L3
                     Issue                                           File


The value of the attribute 'units' is wrong.       2006001-2006005.s0454pfrt-bsst.hdf


Latitude and longitude information is missing
from the file                                      QS_XWGRD3_2008001.20080021608.hdf


Latitude and longitude information is missing
from the file                                      SW_S3E_2003100.20053531923.hdf


Latitude and longitude information is missing
from the file                                      S3096259.HDF



There are two pairs of latitude and longitude in
this file                                        S1700414.HDF


units' attribute for latitude and longitude does
not follow CF conventions                          S1700414.HDF


units' attribute for latitude and longitude does
not follow CF conventions                          QS_S2B44444.20080021548.hdf

need to apply 'scale_factor' and 'add_offset'
attributes on latitude and longitude               S1700414.HDF

Non-standard latitude and longitude name         S1700414.HDF
There are many zeroes inside some data fields.
It seems that these zeroes are 'Fill Value'. But
there is neither a 'Fill_Value' attribute nor a
'missing value' attribute.                       2006001-2006005.s0454pfrt-bsst.hdf
There are many zeroes inside some data fields.
It seems that these zeroes are 'Fill Value'. But
there is neither a 'Fill_Value' attribute nor a
'missing value' attribute.                       QS_XWGRD3_2008001.20080021608.hdf

need to apply 'scale_factor' and 'add_offset'
attributes on latitude and longitude               QS_S2B44444.20080021548.hdf
There are many zeroes inside the latitude and
longitude fields. It seems that these zeroes are
'Fill Value'. But there is neither a 'Fill_Value'
attribute nor a 'missing value' attribute.        QS_S2B44444.20080021548.hdf

Non-standard latitude and longitude name         QS_S2B44444.20080021548.hdf
There are many zeroes inside some data fields.
It seems that these zeroes are 'Fill Value'. But
there is neither a 'Fill_Value' attribute nor a
'missing value' attribute.                       SW_S3E_2003100.20053531923.hdf
                          Description                                             notes

The value of the 'units' attribute should be 'degrees-C'.
However, 'Temp' is assigned to 'units' in this file instead.      no change in latest version
The users are not able to find latitude and longitude
information from the file and need to figure out how to
caculate latitude and longitude based on personal
knowledge or additional information.                              no change in latest version
The users are not able to find latitude and longitude
information from the file and need to figure out how to
caculate latitude and longitude based on personal                 The latest file I found is just from
experience or additional information.                             Year 2003.
The users are not able to find latitude and longitude
information from the file and need to figure out how to
caculate latitude and longitude based on personal                 The latest file I found is just from
experience or additional information.                             Year 1998.

There are two pairs of latitude and longitude included in this
file (WVC_Lat, WVC_Lon and Cen_Lat, Cen_Lon). Users need          The latest file I found is just from
additional information to determine which pair to be used.        Year 1998.
units' attribute for latitude and longitude is 'degree', which
doesn't follow CF conventions. CF conventions use
'degrees_north' for latitude and 'degrees_east' for               The latest file I found is just from
"longitude".                                                      Year 1998.
units' attribute for latitude and longitude is 'degree', which
doesn't follow CF conventions. CF conventions use
'degrees_north' for latitude and 'degrees_east' for               The latest file I found is just from
"longitude".                                                      Year 2003.

                                                               The latest file I found is just from
                                                               Year 1998.
The data fields name for latitude and longitude are 'wvc_lat', The latest file I found is just from
'wvc_lon', 'Cen_lat' and 'Cen_lon'                             Year 1998.


For the data field 'bsst', users have to figure out if the zero
value inside the array is 'Fill Value' or not.                    no change in latest version


For the data field 'asc_avg_wind_speed', users have to figure
out if the zero value inside the array is 'Fill Value' or not. no change in latest version

                                                                  The latest file I found is just from
                                                                  Year 2003.
The geolocation fields 'wvc_lon' and 'wvc_lat' contain value
0 which is likely to be fillvalue. Users have to figure out if the   The latest file I found is just from
zero value inside the array is 'Fill Value' or not.                  Year 2003.
The data fields name for Latitude and longitude are 'wvc_lat'        The latest file I found is just from
and 'wvc_lon'.                                                       Year 2003.


The data field 'rep_wind_speed', users have to figure out if         The latest file I found is just from
the zero value inside the array is 'Fill Value' or not.              Year 2003.
OBPG                          Projects/Missions    Product Names
                             OCTS
                                                  OCTS_L3m
Wrong Information
                             SeaWiFS
                                                  SeaWiFS_L3m
                                                  CZCS_L3m,
                                                  CZCS_L1A
                             CZCS

                                                  CZCS_L3m
                                                  MODISA_L2,
                                                  MODISA_L3m
                             MODISA

                                                  MODISA_L1A
                                                  MODIST_L2,
Need to obtain information                        MODIST_L3m
outside the HDF files
                             MODIST


                                                  MODIST_L1A

                                                  OCTS_L3m
                             OCTS
                                                  OCTS_L1A

                             SeaWiFS
                                                  SeaWiFS_L1A




                             CZCS                 CZCS_l3m

                                                  CZCS_L1A,
                                                  CZCS_L2


                                                  MODISA_L3m
                             MODISA
                                                  MODISA_L2




Non-Standard
                MODISA



                          MODISA_L2

                MODIST
                          MODIST_L3m
Non-Standard

                          OCTS_L2

                OCTS

                          OCTS_L3m

                          OCTS_L2

                          SeaWiFS_L2
                          SeaWiFS_L3m


                SeaWiFS
                          SeaWiFS_L2




                          SeaWiFS_L3m

                          CZCS_L2,
                          CZCS_L1A


                          CZCS_L2

                CZCS

                          CZCS_L2




Special files
                          CZCS_l3m

                MODISA
                          MODISA_L2

                MODIST
                          MODIST_L2
       OCTS_L2
OCTS


       OCTS_L2
                             Issue

The value of attribute 'units' for one data field is blank.




The value of attribute 'units' for one data field is blank
Data fields contain 'Fill Values', but there is neither a
'Fill_Value' attribute nor a 'missing value' attribute.

Additional knowledge is needed to obtain latitude and
longitude values
Data fields contain 'Fill Values', but there is neither a
'Fill_Value' attribute nor a 'missing value' attribute.

Additional knowledge is required to obtain latitude and
longitude values
Data fields contain 'Fill Values', but there is neither a
'Fill_Value' attribute nor a 'missing value' attribute.




Additional knowledge is required to obtain latitude and
longitude values
Data fields contain 'Fill Values', but there is neither a
'Fill_Value' attribute nor a 'missing value' attribute.
Files do not provide latitude and longitude information for
data fields

Additional knowledge is required to obtain latitude and
longitude values


Data fields' attributes are stored in file level rather than the
data field level.

units' attribute for latitude and longitude does not follow CF
conventions

some data fields attributes are stored in file level rather than
the data field level.

units' attribute for latitude and longitude does not follow CF
conventions
Name for fillvalue attribute does not follow CF conventions

some data fields attributes are stored in file level rather than
the data field level.

units' attribute for latitude and longitude does not follow CF
conventions


Data fields' attributes are stored in file property rather than
data field property.

Name for fillvalue attribute does not follow CF conventions


Name for fillvalue attribute does not follow CF conventions

units' attribute for latitude and longitude does not follow CF
conventions


Data fields' attributes are stored in file property rather than
data field property.


Interpolation is needed to calculate latitude or longitude

One pair of latitude and longitude for the whole file that
have several groups

There are many zeroes inside some data fields. It seems that
these zeroes are 'Fill Value'. But there is neither a
'Fill_Value' attribute nor a 'missing value' attribute.




special usage of scale and offset attributes


Latitude or longitude needs additional processing


Latitude or longitude needs additional processing
Latitude or longitude needs additional processing
There are a lot of 0 inside data fields that seem to be viewed
as 'Fill Value' and there is neither a 'Fill_Value' attribute nor
a 'missing value' attribute.
                      File

O19970011997031.L3m_MO_A520_9.hdf




S1999001.L3m_DAY_CDOM_cdom_index_9km.hdf

C19860011986008.L3m_8D_CHLO_4.hdf


C19860011986008.L3m_8D_CHLO_4.hdf

A2002185000000.L2_LAC_SST.hdf


A2010001000000.L1A_LAC.hdf

T2010001000000.L2_LAC_SST.hdf




T2010001000000.L1A_LAC.hdf

O19970011997031.L3m_MO_A520_9.hdf

O1996306151612.L1A_GAC.hdf


S2003006001857.L1A_MLAC.hdf




C19860011986008.L3m_8D_CHLO_4.hdf


C1978303124834.L1A_LAC.hdf


A20021612002192.L3m_R32_NSST_4.hdf


A2010261120500.L2_LAC_SST.hdf
A2010261120500.L2_LAC_SST.hdf


T20000322000060.L3m_MO_NSST_4.hdf


O1996306152450.L2_GAC.hdf




O19970011997031.L3m_MO_A520_9.hdf

O1996306152450.L2_GAC.hdf

S1997247162631.L2_MLAC_OC.hdf
S1999001.L3m_DAY_CDOM_cdom_index_9km.hdf


S1997247162631.L2_MLAC_OC.hdf




S1999001.L3m_DAY_CDOM_cdom_index_9km.hdf


C1978303124834.L2_MLAC.hdf


C1978303124834.L2_MLAC.hdf




C1978303124834.L2_MLAC.hdf




C19860011986008.L3m_8D_CHLO_4.hdf


A2002185000000.L2_LAC_SST.h


T2010001000000.L2_LAC_SST.hdf
O1996306152450.L2_GAC.hdf


O1996306152450.L2_GAC.hdf
                       Description                                                notes
                                                               The latest file we ound is just from Year
                                                               1997.

                                                               It's not applicable for file
                                                               S1999001.L3m_DAY_CHL_chlor_a_9km.hd
                                                               f; Also, it's also blank in the latest version
                                                               The latest file we found is just from Year
The fillvalue of datafield 'l3m_data' is 65535                 1986.
Additional knowledge is required to correctly interpret
the attributes used to calculate the latitude and       The latest file we found is just from Year
longitude.                                              1986.
                                                        Corrected in the latest version
The fillvalue of datafield 'l3m_data' is -32767         (A2010261120500.L2_LAC_SST.hdf)
Additional knowledge is required to correctly interpret
the attributes used to calculate the latitude and
longitude.                                              The latest file I found is from Year 2010.

The fillvalue of datafield 'l3m_data' is -32767                no change in the latest version

The users are not able to find latitude and longitude
information from the file and need to figure out how to
caculate latitude and longitude based on personal
knowledge or additional information.                    The latest file we found is from Year 2010.
                                                        The latest file we found is just from Year
The fillvalue of datafield 'l3m_data' is 255            1997.
                                                        The latest file we found is just from Year
                                                        1997.
Additional knowledge is required to correctly interpret
the attributes used to calculate the latitude and
longitude.                                              no change in the latest version

There's only one data field. The metadata information
for this data field is stored as the global attribute of the   The latest file we found is just from Year
whole file rather than the attribute of the data field.        1986.
units' attribute for latitude and longitude is 'degree'. CF
conventions use 'degrees_north' for latitude and               The latest file we found is just from Year
'degrees_east' for "longitude".                                1986.
The metadata information for some data fields is
stored as the global attribute of the whole file rather
than the attribute of the data fields.                         no change in the latest version
units' attribute for latitude and longitude is 'degree'. CF
conventions use 'degrees_north' for latitude and
'degrees_east' for "longitude".                                The latest file we found is from Year 2010.
‘Fillvalue’ attribute is called ‘bad_value’                    This file is from Year 2010.

some data fields attributes are stored in file level rather
than the data field level. For examples, "units".              no change in the latest version
units' attribute for latitude and longitude is 'degree'. CF
conventions use 'degrees_north' for latitude and               The latest file we found is just from Year
'degrees_east' for "longitude".                                1997.
There's only one data field, metadata information for
this data field are stored as the file level attributes. For
examples, attributes 'Data Minimum' and 'Data                  The latest file we found is just from Year
Maximum'.                                                      1997.
                                                               The latest file we found is just from Year
‘Fillvalue’ attribute is called 'bad_value'                    1997.
Fillvalue' attribute is called 'bad_value_scaled' and
'bad_value_unscaled'                                           no change in the latest version
Fillvalue' attribute is called 'Fill'                          no change in the atest version
units' attribute for latitude and longitude is 'degree'. CF
conventions use 'degrees_north' for latitude and
'degrees_east' for "longitude".                                no change in the latest version
There's only one data field, metadata information for
this data field are stored as the file level attributes. For
examples, attributes 'Data Minimum' and 'Data
Maximum'.                                                      no change in the latest version
Users have to do the interpolation for latitude and
longitude and make it match the dimension size of data         The latest file we found is just from Year
fields.                                                        1986.
There are 3 groups in this file. All of them share one
pair of latitude and longitude stored under group              The latest file we found is just from Year
'Navigation'                                                   1986.


Such as data field 'nLw_443', users have to figure out if The latest file we found is just from Year
0 is 'Fill Value' or not.                                 1986.

There is a file-level attribute: 'Scaling Equation', which
mentioned the application of attribute 'Slope' and
'Intercept' is: float value = Base**((Slope*l3m_data) +        The latest file we found is just from Year
Intercept) = Parameter value                                   1986.
Users have to do an interpolation for latitude and
longitude and make it match the dimension size of data         Corrected in the latest version
fields.                                                        (A2010261120500.L2_LAC_SST.hdf)
Users have to do an interpolation for latitude and
longitude and make it match the dimension size of data
fields.                                                        no change in the latest version
Users have to do an interpolation for latitude and
longitude and make it match the dimension size of data The latest file we found is just from Year
fields.                                                1997.

For example, data field 'nLw_443', users have to figure The latest file we found is just from Year
out if zero is 'Fill Value' or not.                     1997.

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:2/13/2012
language:
pages:74