Topic: Status of GOES-16 SUVI L1b Data

Date/Time Issued: May 9, 2018 1400 UTC

Product(s) or Data Impacted: GOES-16 SUVI L1b Data

Date/Time of Initial Impact: May 4, 2018 at 2000 UTC

Date/Time of Expected End: M-BN/A

Length of Event: M-BN/A

Details/Specifics of Change: The GOES-R Peer Stakeholder - Product Validation Review (PS-PVR) for Solar Ultraviolet Imager (SUVI) Extreme Ultraviolet Imagery (EUV) L1b Provisional Maturity was held on May 4, 2018. As a result of this review, NOAA has confirmed that the SUVI L1b data are at Provisional Validation Maturity as of May 4, 2018. PDA users who have pending subscriptions for these products may now request those subscriptions to be approved by emailing Please include your PDA user group name and the specific subscription name.


SUVI data consist of solar images is six extreme-ultraviolet passbands M-bM-^@M-^T 94 M-CM-^E, 131 M-CM-^E, 171 M-CM-^E, 195 M-CM-^E, 284 M-CM-^E, and 304 M-CM-^E M-bM-^@M-^T with a variety of exposure times and filters in place to ensure each image set captures the full dynamic range of solar phenomena. SUVI images have a pixel resolution of 1280M-CM-^W1280 pixels, each with an angular resolution of 2.5 arcsec per pixel, for a total field of view of 53.3 arcmin square. Some corners of each passband are obscured by instrumental vignetting.


SUVI files come in two varieties: netCDF and Flexible Image Transport System (FITS). In both cases, image metadata provide the image navigation information necessary to locate and orient the Sun with respect to well-known astronomical coordinate systems. For both file formats, these metadata follow the World Coordinate System ( conventions for FITS files. Users who are unfamiliar with these conventions are highly encouraged to review M-bM-^@M-^\Coordinate Systems for Solar Image DataM-bM-^@M-^] (Thompson, 2006), which is linked from this page.


Images are reported in units of radiance (W/m2 str-1), but care must be taken to handle the data array appropriately. In netCDF files, users should be sure to apply the M-bM-^@M-^Xscale_factorM-bM-^@M-^Y and M-bM-^@M-^Xadd_offsetM-bM-^@M-^Y attributes. In FITS files, users should apply the BSCALE and BZERO FITS keywords following the standard convention for each file format. Some FITS and netCDF readers may apply these corrections by default.

Provisional validation means:



Users of the GOES-16 SUVI L1b data bear responsibility for inspecting the data and understanding the known caveats prior to use. Below is the list of caveats that have been identified and are under analysis. Solutions are in development and testing:


  1. No SUVI L1b data prior to declaration of Provisional Maturity should be used. NCEI will reprocess and release the early mission data using the Provisional Maturity algorithm and look-up tables.

  2. Some metadata entries in SUVI L1b files may be incorrect or incomplete. The BUNIT keyword specifying image units is not present in SUVI FITS products. Image observation times and other time/date fields such as the DATE-OBS keyword are missing from SUVI L1b FITS products on the first of every month. The EFF_AREA keyword does not include the effect of the camera quantum efficiency on the instrumental effective area.

  3. The location of Sun center specified by the CRPIX1 and CRPIX2 keywords could be erroneous in the event of special SUVI operations. Users should validate that this information is correct before performing calculations that require accurate information in these fields.

  4. Spikes in the images resulting from particle impacts with the SUVI camera can, in some cases, cause significant contamination in the radiometric signal. These problems have a particularly pronounced effect on the in aggregate radiometric metadata fields in short exposures images.

  5. Bad pixels are not presently fully tracked and repaired in SUVI images, users may encounter negative valued pixels or NANs in the image array. Note also that the bad pixel table (or Data Quality Flag) in SUVI L1b files is not presently representative of either the location or correction of these bad or patched pixels. It should not be used.

  6. The GOES-16 platform location presently is specified in Earth-Centered Earth-Fixed (ECEF) coordinates by the OBSGEO-X, -Y, and -Z keywords. Users requiring platform location in heliocentric coordinate systems can refer to Hapgood (1992; for information on coordinate conversions.

  7. Some users may encounter compatibility issues between some netCDF readers and FITS standard keywords that include a hyphen such as DATE-OBS when they appear in the netCDF version of SUVI L1b files. Users are encouraged to contact NCEI to report such problems and for guidance on possible workarounds.


Users are encouraged to contact the GOES-R SUVI team in the event they have questions or encounter difficulties with SUVI files. The NCEI website provides additional information and access to SUVI L1b files


Contact for further information: Kathryn Mozer at


NCEI contacts for specific information on the SUVI L1b data:

Dan Seaton

Jonathan Darnel

Margaret Tilton


This message was sent to You have been sent this and other notifications because you have opted in to receive it. If for any reason, you wish to unsubscribe, please contact ESPC Help Desk at or (301) 817-3880. Please note: it may take up to two business days to process your unsubscribe request.