General check information.
| # | Location | Name | Date Checked | Standard Name |
|---|---|---|---|---|
| 1 | /data/data312/jcruzcruz/NVPS_VI/compliance/SAMPLE_DAILY_AASR | VI-DLY-GLB_v4r0_j01_s20250105_e20250105_c202507302156310.nc | 2025-08-06 18:01:19 | CCAP/NCCF |
File name check. This check is a required check for the NCCF/CCAP standard.
| # |
Name
|
Value |
Check
|
Message |
|---|---|---|---|---|
| 1 | short_name | VI-DLY-GLB | True | The short name is valid. |
| 2 | version | v4r0 | True | Version is valid. |
| 3 | platform_id | j01 | True | The platform id is valid. |
| 4 | date_start | s20250105 | False | The start date is not valid. The length of the date string must be 16 characters long. Current length: 9. |
| 5 | date_end | e20250105 | False | The end date is not valid. The length of the date string must be 16 characters long. Current length: 9. |
| 6 | date_creation | c202507302156310 | True | The creation date is valid. |
| 7 | field_number | 6 | True | The number of fields is correct. |
| 8 | first_three_fields_length | 17 -> "VI-DLY-GLBv4r0j01" | True | The combined length of the first three fields is too long. The combined length of the first three fields must not be more than 38 characters long. This is not mandatory, but strongly suggested! Current length: 17. |
| 9 | total_length | 56 | True | The name has a valid length; i.e., it is less than or equal to 95 characters, and has at least one non-blank character. |
Optional Grid root metadata check.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | geospatial_lat_resolution | True | |
| 2 | geospatial_lon_resolution | True |
Required Grid root metadata check.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | geospatial_lat_max | True | |
| 2 | geospatial_lat_min | True | |
| 3 | geospatial_lon_max | True | |
| 4 | geospatial_lon_min | False | The value must be in the range [-180.00, 180.00). Current value: -180.00. Remember that the values are rounded to 2 decimal places. Remember that "Banker's Rounding" is being used, i.e., all the values are rounded to the nearest even number. |
Required Orbit root metadata check.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | ascend_descend_data_flag | False | The metadata field does not exist. |
| 2 | end_orbit_number | False | The metadata field does not exist. |
| 3 | start_orbit_number | False | The metadata field does not exist. |
Optional root metadata check.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | keywords_vocabulary | False | The metadata field does not exist. |
| 2 | references | False | The metadata field does not exist. |
| 3 | sensor_band_identifier | False | The metadata field does not exist. |
| 4 | sensor_central_radiation_frequency | False | The metadata field does not exist. |
Recommended root metadata check.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | time_coverage_end | True | |
| 2 | time_coverage_start | True | |
| 3 | title | False | The value must be one of the following values: "VI_DLY_GLB". Current value: VI-DLY-GLB. |
Required Grid/Swath root metadata check.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | geospatial_lat_units | True | |
| 2 | geospatial_lon_units | True |
Required root metadata check.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | Conventions | True | |
| 2 | cdm_data_type | True | |
| 3 | creator_email | True | |
| 4 | creator_name | True | |
| 5 | creator_url | True | |
| 6 | date_created | True | |
| 7 | day_night_data_flag | False | The metadata field does not exist. |
| 8 | history | True | |
| 9 | id | True | |
| 10 | institution | True | |
| 11 | instrument | True | |
| 12 | keywords | True | |
| 13 | metadata_link | False | The metadata link must be: "https://data.noaa.gov/onestop/". Current value: VI-DLY-GLB_v4r0_j01_s20250105_e20250105_c202507302156310.nc. |
| 14 | naming_authority | False | The value must be one of the following values: "gov.noaa.nesdis.ncei.", "gov.noaa.nesdis.ncei". Current value: gov.noaa.nesdis.ospo. |
| 15 | platform | True | |
| 16 | platform_type | False | The metadata field does not exist. |
| 17 | processing_level | True | |
| 18 | production_environment | False | The value must be one of the following values: "dev", "uat", "prod". Current value: DEV. |
| 19 | production_site | False | The value must be one of the following values: "NCCF". Current value: STAR. |
| 20 | project | True | |
| 21 | publisher_email | True | |
| 22 | publisher_name | True | |
| 23 | publisher_url | True | |
| 24 | source | True | |
| 25 | standard_name_vocabulary | False | The standard name vocabulary must be "CF Standard Name Table" followed by the version number. Example: "CF Standard Name Table v50" or "CF Standard Name Table version 50". Current value: CF Standard Name Table v1.5. |
| 26 | summary | True |
Required Swath root metadata check.
| # |
Name
|
Check
|
Message |
|---|
The "quality_information" does not exist, checks related to this variable will not be performed until it is added to the netcdf file.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | quality_information | False | Variable not found. |
Extended geospatial metadata consistency check. Keep in mind that these checks are dependent on the value of the "cdm_datatype". Thus, if the "cdm_datatype" is not "Grid" or "Swath" these variables will not be checked.Current "cdm_datatype" value: Grid.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | cardinal_points_check | False | The grid values will not be checked because the geospatial coordinates are not valid; i.e., the polygon , the maximum/minimum values of the latitudes and/or longitude values are not valid or don't exist. |
| 2 | latitude_min/max_ordering | True | The variables geospatial_geospatial_min/max are ordered correctly. The comparison yielded: -90.0 <= 90.0. |
| 3 | longitude_min/max_ordering | False | One or more of the variables - geospatial_lon_max, geospatial_lon_min - do not exist, thus, this quantity will not be checked. Look at the check results for more information. Keep in mind that this quantity will not be checked until the aforementioned variables exist and are valid. |
| 4 | orbit_number_ordering | False | One or more of the variables - start_orbit_number, end_orbit_number - do not exist, thus, this quantity will not be checked. Look at the check results for more information. Keep in mind that this quantity will not be checked until the aforementioned variables exist and are valid. |
Extended time ordering metadata consistency check.
| # |
Name
|
Check
|
Message |
|---|---|---|---|
| 1 | data_time_end_created_ordering | True | The date '2025-01-05 23:59:59' is before the date '2025-07-30 21:56:31' as expected. The difference between the dates is 17790992.0 seconds. Dates are allowed to be equal. |
| 2 | data_time_start_end_ordering | True | The date '2025-01-05 00:00:00' is before the date '2025-01-05 23:59:59' as expected. The difference between the dates is 86399.0 seconds. Dates are allowed to be equal. |
| 3 | date_matching_created | True | The data date '2025-07-30T21:56:31Z' matches the file date 'c202507302156310'; to the second. |
| 4 | date_matching_end | False | Cannot check the matching of the dates date_end and time_coverage_end because one or both of them are not valid or do not exist. |
| 5 | date_matching_start | False | Cannot check the matching of the dates date_start and time_coverage_start because one or both of them are not valid or do not exist. |
| 6 | file_time_end_created_ordering | False | Cannot check the ordering of the dates date_end and date_creation because one or both of them are not valid or do not exist. |
| 7 | file_time_start_end_ordering | False | Cannot check the ordering of the dates date_start and date_end because one or both of them are not valid or do not exist. |
This is a summary of the metadata check for the root of the netcdf file and the metadata of the "quality_information" variable. Please look at the errors/warnings generated for each parameter.
This is a summary of the check for the root metadata. Please look at the errors/warnings generated for each parameter.
| # |
Parameter Name
|
Current Value | Expected Type | Current Type | Exists | Description |
|---|---|---|---|---|---|---|
| 1 | keywords_vocabulary | None | str | NoneType | False | If you are using a controlled vocabulary for the words/phrases in your 'keywords' attribute, this is the unique name or identifier of the vocabulary from which keywords are taken. |
| 2 | references | None | str | NoneType | False | Published or Web-based references describing the data or methods used to produce the product. |
| 3 | sensor_central_radiation_frequency | None | str | NoneType | False | This attribute should be set to the center frequencies (s-1) of those channels used to generate the product. If more than one channel, please use the comma to separate them. Also make sure the order is the same as the one in the "sensor_band_identifier". |
| 4 | sensor_band_identifier | None | str | NoneType | False | This attribute should be set to the instrument channels used to generate the product. If more than one channel, please use a comma to separate them like "01, 02, 04". |
| 5 | geospatial_lat_resolution | 0.008999999612569809 | float | float32 | True | Optional attribute for lon/lat grids only: the (uniform) spacing of points in latitude, in "degrees_north". Not applicable to swath-type data. |
| 6 | geospatial_lon_resolution | 0.008999999612569809 | float | float32 | True | Optional attribute for lon/lat grids only: the (uniform) spacing of points in latitude, in "degrees_east". Not applicable to swath-type data. |
| 7 | Conventions | "CF-1.5" | str | str | True | At a minimum, compliance with CF Convention 1.5 ("CF-1.5"), but recommends "CF-1.6" and "ACDD-1.3". Example: "CF-1.6, ACDD-1.3". |
| 8 | cdm_data_type | "Grid" | str | str | True | This attribute describes the geographic category the NUP data represents. This should be "Swath" for native 2-D satellite swath data; Full Disk, CONUS, Meso (as applicable) for Geostaionary. |
| 9 | creator_email | "Yunyue.Yu@noaa.gov, yuan.zhou@noaa.gov, corinne.carter@noaa.gov, zhensong@umd.edu" | str | str | True | Include an email for the algorithm development team. This attribute offers users the opportunity to contact developers directly (e.g., miirs_team@noaa.gov). This may be a list of emails separated by commas. |
| 10 | creator_name | "DOC/NOAA/NESDIS/STAR > Land Team, Center for Satellite Applications and Research, NESDIS, NOAA, Department of Commerce" | str | str | True | This attribute should include STAR and the name of the algorithm team responsible for development of the NUP (e.g., "DOC/NOAA/NESDIS/STAR > MiRS Team, Center for Satellite Applications and Research, NESDIS, NOAA, Department of Commerce"). |
| 11 | creator_url | "https://www.star.nesdis.noaa.gov/jpss/vi.php" | str | str | True | All NUP projects should have a website that users can access. Include the URL in this attribute (e.g., http://mirs.nesdis.noaa.gov). |
| 12 | date_created | "2025-07-30T21:56:31Z" | str | str | True | This attribute should be set to the UTC time the product file was created by NDE as "YYYY-MM-DDThh:mm:ssZ"; notice the capitalization on the T and Z. |
| 13 | day_night_data_flag | None | str | NoneType | False | As applicable, this attribute should be set to "day, "night" or "both" depending on the sunlit conditions for the observation. |
| 14 | geospatial_lat_units | "degrees_north" | str | str | True | This attribute should be set to "degrees_north". |
| 15 | geospatial_lon_units | "degrees_east" | str | str | True | This attribute should be set to "degrees_east". |
| 16 | history | "Created by VI algorithm v4.0" | str | str | True | This attribute should reflect the algorithm name and version used to produce the NUP (e.g., "Enterprise MiRS Version 8."). |
| 17 | id | "6325e642-2cc4-4753-b785-c40aef28e051" | str | str | True | A Unique User Identifier (UUID) Version 4. Version 4 UUIDs have the form xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx where x is any hexadecimal digit and y is one of 8, 9, "a", or "b", creating an identifier like: 3c7a4360-0a4f-4cbf-8a5f-5c5b5b6c9b44. NOT case sensitive and not "-" sensitive. |
| 18 | institution | "DOC/NOAA/NESDIS/OSPO > Office of Satellite and Product Operations, NESDIS, NOAA, U.S. Department of Commerce." | str | str | True | For files created by the NCCF, this attribute should be "DOC/NOAA/NESDIS/STAR > Center for Satellite Applications and Research, NESDIS, NOAA, U.S. Department of Commerce". |
| 19 | instrument | "VIIRS" | str | str | True | This attribute should reflect the instrument(s) used to derive the NUP. For the S-NPP satellite these are "ATMS", "CERES", "CrIS", "OMPS" and/or "VIIRS". If multiple instruments were use then they must be separated by commmas. It is recommended to check with NCEI on instrument vocabulary. |
| 20 | keywords | "Vegetation Index,NDVI,EVI,Land Product" | str | str | True | A comma-separated list of key words and/or phrases. Keywords may be common words or phrases, terms from a controlled vocabulary (GCMD is often used), or URIs for terms from a controlled vocabulary (see also the "keywords_vocabulary" attribute). |
| 21 | metadata_link | "VI-DLY-GLB_v4r0_j01_s20250105_e20250105_c202507302156310.nc" | str | str | True | A URL that gives the location of more complete metadata or a product information web page. This variable must take the value: https://data.noaa.gov/onestop/. |
| 22 | naming_authority | "gov.noaa.nesdis.ospo" | str | str | True | This attribute should be the organization that provides the "id" attribute, which is the NCEI.= (gov.noaa.nesdis.ncei). For products not archived it should be OSPO (gov.noaa.nesdis.ospo). |
| 23 | platform | "J01" | str | str | True | This attribute should reflect the satellite(s) used to derive the NUP (e.g., S-NPP, NOAA-20, GOES-16). |
| 24 | platform_type | None | str | NoneType | False | This attribute should reflect the type of the satellite. This should be either: "Polar" for polar orbiting satellite products, "Geostationary" for geostationary satellite products or "Multi" for products using both Geostationary and Polar satellites.. |
| 25 | processing_level | "NOAA Level 3" | str | str | True | This attribute describes the level of processing (e.g., "NOAA Level 2"). Level 2 products represent Environmental Data Records (EDRs). Level 3 are products derived from Level 2 (e.g., composites). |
| 26 | production_environment | "DEV" | str | str | True | This attribute is passed through the PCF and describes the processing string generating the product. This should be: "dev" for Development, "uat" for User Acceptance Test, "prod" for Operational Production, etc. |
| 27 | production_site | "STAR" | str | str | True | This attribute is passed through the PCF and describes the processing site for the product. This should be "NCCF". |
| 28 | project | "NESDIS Common Cloud Framework" | str | str | True | For all files that are created by the NCCF, this attribute should be "NESDIS Common Cloud Framework". |
| 29 | publisher_email | "espcoperations@noaa.gov" | str | str | True | This attribute should be the OSPO ESPC Help Desk e-mail "espcoperations@noaa.gov". |
| 30 | publisher_name | "DOC/NOAA/NESDIS/OSPO > Office of Satellite and Product Operations, NESDIS, NOAA, U.S. Department of Commerce." | str | str | True | NCCF is responsible for generating all NUPs. This attribute should be "DOC/NOAA/NESDIS/OSPO > Office of Satellite and Product Operations, NESDIS, NOAA, U.S. Department of Commerce". |
| 31 | publisher_url | "http://www.ospo.noaa.gov" | str | str | True | This attribute should be the OSPO website "http://www.ospo.noaa.gov". |
| 32 | source | "GITCO, JRR-AOD, JRR-CloudMask, SurfRefl, SVI01, SVI02" | str | str | True | This attribute should list all major input files as a comma delimited list. |
| 33 | standard_name_vocabulary | "CF Standard Name Table v1.5" | str | str | True | Standard naming vocabulary is derived from the CF Standard Name Table. However, some data quality attributes may be unique to NESDIS. These attributes should be "CF Standard Name Table" followed by the version number and the developer should specify the table version. Example: "CF Standard Name Table v50" or "CF Standard Name Table version 50". |
| 34 | summary | "The output file includes three primary VI products(NDVI_TOA, NDVI_TOC and EVI_TOC) and attach five reflectances(I1_TOA,I2_TOA,I1_TOC,I2_TOC,M3_TOC), three angles(VZA,SZA, RAA),two quality flags(QF1,QF2)and coordinates(latitude, longitude) derived from VIIRS observations" | str | str | True | This attribute should briefly describe the product (e.g., "Water and temperature profiles"). |
| 35 | time_coverage_end | "2025-01-05T23:59:59Z" | str | str | True | This attribute must be set to the UTC end time of an observation as a string in the format "YYYY-MM-DDThh:mm:ssZ". |
| 36 | time_coverage_start | "2025-01-05T00:00:00Z" | str | str | True | This attribute must be set to the UTC start time of an observation as a string in the format "YYYY-MM-DDThh:mm:ssZ". |
| 37 | title | "VI-DLY-GLB" | str | str | True | This should be set to the NUP product short name (e.g., MIRS_IMG). Product short name must be unique and descriptive, and use underscores for separation. |
| 38 | geospatial_lat_max | 90.0 | float | float32 | True | This attribute describes the maximum latitude of the geospatial coverage of the grid. Is part of the bounding latitudes and longitudes of the geospatial coverage of the grid. Latitude values include -90 (south) to 90 (north) degrees and longitude values include -180 (west) to 180 (east). |
| 39 | geospatial_lat_min | -90.0 | float | float32 | True | This attribute describes the minimum latitude of the geospatial coverage of the grid. Is part of the bounding latitudes and longitudes of the geospatial coverage of the grid. Latitude values include -90 (south) to 90 (north) degrees and longitude values include -180 (west) to 180 (east). |
| 40 | geospatial_lon_max | 180.0 | float | float32 | True | This attribute describes the maximum longitude of the geospatial coverage of the grid. Is part of the bounding latitudes and longitudes of the geospatial coverage of the grid. Latitude values include -90 (south) to 90 (north) degrees and longitude values include -180 (west) to 180 (east). |
| 41 | geospatial_lon_min | -180.0 | float | float32 | True | This attribute describes the minimum longitude of the geospatial coverage of the grid. Is part of the bounding latitudes and longitudes of the geospatial coverage of the grid. Latitude values include -90 (south) to 90 (north) degrees and longitude values include -180 (west) to 180 (east). |
| 42 | ascend_descend_data_flag | None | float | NoneType | False | As applicable for Granule/Orbit products: This atrribute indicates whether the satellite is moving northward or southward. The center time of an observation is used. This attribute should be set to "0" for ascending/northward, "1" for descending/southward, and "2" for transitioning. |
| 43 | end_orbit_number | None | int | NoneType | False | This attribute is a sequential whole number set by the S-NPP/JPSS Ground System in the xDR metadata. Orbits are incremented on the northward equatorial node. |
| 44 | start_orbit_number | None | int | NoneType | False | This attribute is a sequential whole number set by the S-NPP/JPSS Ground System in the xDR metadata. Orbits are incremented on the northward equatorial node. |
| # |
Parameter Name
|
Current Value | Expected Type | Current Type | Exists | Description |
|---|---|---|---|---|---|---|
| 1 | quality_information | None | var | None | False | The variable "quality_information" has not been found. This variable must exist for the metadata checks to take place. |