Reference · built on requestCommons signalWeather & climate

NCEI Access Data Service

Historical station records such as daily summaries by station, date range, or bounding box as CSV, JSON, or NetCDF from NOAA NCEI.

Request accessPricing ↗

About

NOAA's National Centers for Environmental Information hold the archive of observed weather. The Access Data Service at www.ncei.noaa.gov/access/services/data/v1 returns records from a named dataset for a station list, a date range, or a bounding box, in CSV, JSON, NetCDF, PDF, or SSV. Documented datasets include daily-summaries, global-marine, and global-summary-of-the-year, with new datasets added quarterly. The daily summaries come from GHCNd, which draws on more than 100,000 stations in 180 countries and territories and receives daily updates. A companion Search Service at /access/services/search/v1/data finds stations and datasets by text, bbox, and date.

Through Fibric, an operator reads the station history behind a question and proposes an answer with the rows attached: was it the weather, and by how much.

This is a reference listing. It documents what Fibric would read from NCEI Access Data Service 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

  • Records from daily-summaries, global-marine, global-summary-of-the-year, and other datasets by the dataset parameter
  • Station selection by comma-separated stations ids or by boundingBox as north, west, south, east
  • dataTypes such as PRCP, SNOW, DP01, DT32, and DX90, case-sensitive, with includeAttributes for each value's attributes
  • startDate and endDate in ISO 8601, to the day or to the second, with UTC offsets URL-encoded
  • Output as CSV, JSON, NetCDF, PDF, or SSV, with units converted to metric or standard
  • Station and dataset discovery through the Search Service with text, bbox, dataTypes, limit, and offset

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

  • Check a carrier's weather excuse

    Daily summaries for the station nearest the delivery address show precipitation, snowfall, and temperature on the day claimed. The operator attaches the rows and proposes whether to accept the delay.

    With Delivery Dispute

  • Normalise a utility bill for the weather

    Daily maxima and minima for the billing period give degree days per site. The operator proposes which bills deviate from the weather-adjusted expectation and why.

    With Bill Reconcile

  • Compare sites on the same weather

    Each site's nearest station supplies its temperature and precipitation history. The operator ranks sites after removing weather and proposes which gaps are worth a visit.

    With Site Benchmark

  • Explain a forecast miss with the record

    Actual station records for the period sit beside the demand forecast and the outcome. The operator proposes how much of the variance the weather explains.

    With Forecast Variance

Requirements

  • The dataset identifier and the exact, case-sensitive dataTypes names for the records you want
  • Station identifiers, or a boundingBox, since the default extent is the whole globe
  • HTTPS on every request, per federal policy
  • A citation for each dataset you use, such as Menne et al. 2012 for GHCN-Daily
Authentication
No key or token; the Data Service and Search Service answer plain HTTPS GET requests.

Limits

  • The documentation says not all NCEI datasets are available through the Access Data Service; check the dataset list first
  • Daily summaries are rebuilt each weekend and archive-quality sources can lag 45 to 60 days, so recent values may change
  • NOAA and NCEI make no warranty regarding these data; station observations were not managed to climate-monitoring standards
  • Malformed requests return HTTP 400 with a JSON errorMessage and errorCode

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 NCEI Access Data Service ↗

Questions and answers

Which datasets can I request?
The documentation names daily-summaries, global-marine, and global-summary-of-the-year as examples and says new datasets are added quarterly. It also states that not every NCEI dataset is reachable through this service. Use the Search Service to confirm a dataset and its stations before you build on it.
How current are daily summaries?
GHCNd receives daily updates from its data streams and is rebuilt each weekend from more than 25 sources. Archive-quality sources arrive 45 to 60 days after a month closes, and a finalised value can replace an earlier real-time one.
Do I need a token?
No. The Access Data Service and Search Service take plain HTTPS GET requests. NCEI's separate Climate Data Online web services do require a token and are limited to 5 requests a second and 10,000 a day; this listing does not cover them.
Ask about NCEI Access Data Service

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 National Centers for Environmental Information (www.ncei.noaa.gov). 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