Reference · built on requestCommons signalAviation & marine

NOAA GOES on AWS

GOES-16, 17, 18, and 19 ABI, GLM, and SUVI products as NetCDF4 in public S3 buckets, with an SNS notification for each new file.

Request accessPricing ↗

About

NOAA's Open Data Dissemination program places the output of the GOES-R series satellites in four public Amazon S3 buckets in us-east-1: noaa-goes16, noaa-goes17, noaa-goes18, and noaa-goes19. Files are NetCDF4 under the key scheme <Product>/<Year>/<Day of Year>/<Hour>/<Filename>. Products include ABI Level 1b radiances (RadF, RadC, RadM) and Level 2 products such as CMIP and MCMIP, GLM-L2-LCFA lightning, and the SUVI, EXIS, MAG, and SEIS space-weather series. Each bucket has an SNS topic, for example NewGOES16Object, that fires when a file lands. NODD states data are added as soon as available and are open to the public.

An operator subscribes to the topic for your region, reads the products it needs, and proposes a lightning hold, a storm reserve, or a solar-yield note for your approval.

This is a reference listing. It documents what Fibric would read from NOAA GOES on AWS and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • ABI Level 1b radiances: ABI-L1b-RadF full disk, ABI-L1b-RadC CONUS, ABI-L1b-RadM mesoscale, one file per band and scan
  • ABI Level 2 products including CMIP and MCMIP cloud and moisture imagery in F, C, and M variants, among over 50 derived products
  • GLM-L2-LCFA lightning events, groups, and flashes from the Geostationary Lightning Mapper
  • SUVI-L1b bands Fe093 to He303, EXIS-L1b-SFEU and SFXR, MAG-L1b-GEOF, and SEIS particle files
  • New-object notifications on SNS topics arn:aws:sns:us-east-1:123901341784:NewGOES16Object through NewGOES19Object
  • Filename fields s, e, and c giving scan start, scan end, and file creation time, as in OR_ABI-L1b-RadF-M3C02_G16_s..._e..._c....nc

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Pause outdoor work when lightning nears

    Read GLM-L2-LCFA flashes from the SNS-triggered files. When flashes fall inside your radius around a site, the operator proposes a hold on hot work and roof access for your approval.

    With Severe Weather Notice, Hot Work Permit

  • Explain a low solar day

    Sample ABI cloud imagery over an array at each CONUS scan. When cloud cover explains a yield drop, the operator proposes an annotation instead of a fault ticket.

    With Array Yield, Change Annotation

  • Stage a storm reserve

    Watch ABI full-disk imagery for a system developing over your coast. Paired with a forecast, the operator proposes a fuel and generator check ahead of arrival.

    With Storm Reserve, Storm Prep

Requirements

  • An S3 client able to read public buckets and a NetCDF4 reader for the .nc files
  • The bucket and product prefixes for the satellite covering your sites, chosen from noaa-goes16 through noaa-goes19
  • An AWS account to subscribe a queue or function to the NewGOES16Object to NewGOES19Object SNS topics
  • Capacity for volume: full disk, CONUS every five minutes, and mesoscale every minute arrive continuously
Authentication
None. The buckets are public S3 reads; subscribing to the SNS topics is done from your own AWS account.

Limits

  • Objects move from S3 Standard to Infrequent Access after 30 days
  • Level 1b and Level 2 files are science-format NetCDF4; a site value means projecting the fixed grid to your coordinates
  • No per-point API; you fetch whole scenes and subset them yourself
  • The NODD README documents the noaa-goes16 and noaa-goes17 layout; the 18 and 19 buckets are listed on the registry page

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request NOAA GOES on AWS ↗

Questions and answers

Which satellites are in the buckets?
Four: noaa-goes16, noaa-goes17, noaa-goes18, and noaa-goes19, all in the us-east-1 region. The registry page describes GOES-16, 17, 18, and 19 as providing continuous weather imagery and monitoring of meteorological and space environment data across North America.
How do I learn about a new file without polling?
Subscribe to the SNS topic for the bucket, for example arn:aws:sns:us-east-1:123901341784:NewGOES16Object. NODD publishes a notification for each new object and states that new data is added as soon as it is available.
How often do the imagers scan?
The NODD README says the ABI full disk is normally every 15 minutes, CONUS every 5 minutes, and each of the two mesoscale regions usually every minute. In mode 4 the instrument scans the full disk every five minutes with no CONUS or mesoscale data.
Ask about NOAA GOES on AWS

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by NOAA Open Data Dissemination (noaa-goes16, noaa-goes17, noaa-goes18, noaa-goes19 S3 buckets in us-east-1). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy