NOAA Office of Satellite and Product Operations

GOES User Information and Documents

GOES-16 Product Maturity Levels (3/1/17)

The evolving calibration and validation (cal/val) maturity of the Geostationary Operational Environmental Satellite R-Series (GOES-R) products is described by three levels: Beta, Provisional, and Full validation. Once Beta Maturity of the L1b products is achieved, the Level 2+ (L2+) will progress toward Beta maturity. Further levels of maturity (Provisional and Full validation) require additional activities that can continue over a longer time period than the Beta validation process. A detailed description of the three product maturity levels is given in Table 1. The three maturity levels are:

  • Beta Validation: The product is minimally validated and may still contain significant errors; based on product quick looks using the initial calibration parameters.
  • Provisional Validation: The product performance has been demonstrated through a large, but still (seasonally or otherwise) limited, number of independent measurements. The analysis is sufficient for limited qualitative determinations of product fitness-for-purpose, and the product is potentially ready for testing operational use.
  • Full Validation: The product performance has been demonstrated over a large and wide range of representative conditions, with comprehensive documentation of product performance, including known anomalies and their remediation strategies. Products are ready for operational use.

Table 1. GOES-R Product Validation Maturity Levels.

GOES-R Product (L1b and L2+) Maturity Level
Beta Validation
Preparation Activities
  • Initial calibration applied (L1b).
  • Rapid changes in product input tables, and possibly product algorighms, can be expected.
  • Product quick looks and initial comparisons with ground truth data (if any) are not adequate to determine product quality.
  • Anomalies may be found in the product and the resolution strategy may not exist.
End state
  • Products are made available to users to gain familiarity with data formats and parameters.
  • Product has been minimally validated and may still contain significant errors.
  • Product is not optimzed for operatonal use.
Provisional Validation
Preparation Activities
  • Validation and quality assurance (QA) activities are ongoing, and the general research community is now encouraged to participate.
  • Severe algorithm anomalies are identified and under alalysis. Solutions to anomalies are in development and testing.
  • Incremental product improvements may still be occurring.
  • Users are engaged in the Customer Forums (L2+ products only), and user feedback is assessed.
End state
  • Product performance (L1 or L2+) has been demonstrated through analysis of a small number of independent measurements obtained from selected locations, periods, and associated ground-truth/field efforts.
  • Product analysis are sufficient to communicate product performance to users relative to expectations.
  • Documentation of product performance exists that includes recommended remediation strategies for all anomalies and weaknesses. Any algorithm changes associated with severe anomalies have been documented, implemented, tested, and shared with the user community.
  • Testing has been fully documented.
  • Product ready for operational use and for use in comprehensive calibration/validation activities and product optimization.
Full Validation
Preparation Activities
  • Validation, QA, and anomaly resolution activities are ongoing.
  • Incremental product improvements may still be ocurring.
  • Users are engaged and user feedback is assessed.
End state
  • Product performance for all products is defined and documented over a wide range of representative conditions via ongoing ground-truth and validation efforts.
  • Products are operationally optimized, as necessary, considering mission parameters of cost, schedule, and technical competence as compared to user expectations.
  • All known product anomalies are documented and shared with the user community.
  • Product is operational.

The assessment and declaration of a product’s maturity level is performed during the Peer Stakeholder–Product Validation Review (PS-PVR). At each PS-PVR, the status of the products will be presented by members of the cal/val science teams. For L2+ products, Beta maturity PS-PVRs are held in close proximity with and prior to Operations Handover.

The SEISS PS-PVR for Beta maturity was conducted on February 10, 2017. The ABI (Level 1b and CMI) PS-PVR for Beta maturity was conducted on February 28. 2017. The planned dates for future PS-PVRs are listed below:

  • EXIS. The Beta PS-PVR was conditionally approved on March 8, 2017, and additional analysis of the EUVS files were conducted prior to adding EXIS data to the GRB.
  • Mag. The Beta PS-PVR for Mag is planned for March 29, 2017.
  • SUVI. The Beta PS-PVR for SUVI is planned for April 12, 2017.
  • GLM. The Beta PS-PVR for GLM Level 2+ products is April 26, 2017.

GOES-16 Known Issues at Beta Validation Maturity (3/1/17). The following issues are being resolved with an implementation target time of Provisional Validation Maturity:

  • Navigation - There is a known issue with navigation that can impact frame-to-frame registration.
  • Co-Registration - There is a known issue with co-registration among the spectral channels.
  • Image Striping/Banding - There is a known issue with occasional striping within some of the spectral channels.
  • Data drop-outs - There is a known issue with occasional input data drops that can result in fill data for some image regions.
  • Metadata – There is an issue with the GOES-16 ABI L1b metadata fields that may cause problems for some GRB and PDA users until it is resolved with a future software patch. In the ABI L1b file metadata, a number of fields, including Esun, kappa0, bc1, and bc2 were not updated when the ABI Calibration was updated in the pre-launch software build of DO.04.01.The result is that the metadata fields in the ABI L1b product are not correct. This may cause a problem for users who want to use those fields to convert from radiance to reflectance factor and brightness temperature. The problem is documented with a work request (WR). The fix is currently slated to be implemented by Provisional Status Maturity.

The correct Radiance-to-CMI metadata values for GOES-16 ABI are listed in the table below. These values will be corrected in the Radiance product. Two work requests document this issue and it should be resolved by Provisional Validation Maturity.


The radiance conversions are documented in the Product Definition and Users' Guide (PUG) Volume 4.

SCID Header Issue (2/27/17)

While reviewing the GRB Information Packets a user noted that a 10-bit SCID is being put into an 8-bit field with the leading 0x2 being lost in the process. There appears be a registry conflict between the 0x250 value listed here for GOES-R (a 10-bit SCID, assuming VN=0b00) and the 0x50 value actually used (8-bit SCID consistent with VN=01). A work request has been opened and the estimated timing for resolving the issue is currently being determined.

GOES-16 Data Caveat (2/27/17)

NOAA's GOES-16 satellite has not been declared operational and its data are preliminary and undergoing testing. Users receiving these data through any dissemination means (including, but not limited to, PDA and GRB) assume all risk related to their use of GOES-16 data and NOAA disclaims any and all warranties, whether express or implied, including (without limitation) any implied warranties of merchantability or fitness for a particular purpose.

A new Sensor Processing System (SPS) software was released on 4/21/2014 for GOES-15 and 4/22/2014 for GOES-13. The new SPS release 10.4.1 replaces version 10.2 and corrects the following issues observed with GOES-13/14/15 imagers and sounders.

GOES-15 Sounder Short-Wave striping. This problem was observed during GOES-15 Post-Launch Testing (PLT) and was discovered to be due to detector-to-detector and line-to-line (East to West vs. West to East) differences. The correction algorithm corrects both problems in real-time (line by line). More detail can be found in the paper, "A Real Time De-Striping Algorithm for Geostationary Operational Environmental Satellite (GOES) P Sounder Images" by Zhenping Li, and images in the presentation "GOES15 Sounder Destriping Correction" by University of Wisconsin scientists.

GOES-13 IR Channels 2 (3.9 um) and 4 (10.7 um) registration difference was discovered to be 1 pixel or greater at certain times of day. This can cause false fog data which uses the difference between these two channels. A registration correction algorithm was developed into SPS v10.4.1 which shifts one of these channels towards the other based on whichever is closer to visible channel. When channel-2 needs correction it is shifted one full pixel whenever the difference is more than 0.5 pixel. When channel-4 needs correction (GOES-14), the data are resampled to make full correction so the two channels registration better match. More detail can be found in the paper, "GOES IR Channel to Channel Co-Registration Correction Implementation and GVAR changes" by Zhenping Li.

GOES-13 Sounder Dropped Pixel Correction: The last significant element included in this software release is the implementation of an algorithm which utilizes a second sync-bit code if the first is not found. This algorithm will allow the software to recover what was previously considered as lost data blocks which are depicted as missing pixels (black spots) since July 2013. More detail can be found in the paper, "SPS 10.4.1 Release Notes" by David Herceg.