NOAA Climate Data Online Download and Formats: Weather Records, Station Data, APIs, and GIS Workflows
NOAA Climate Data Online (CDO) is a discovery and access system for historical weather and climate observations maintained by NOAA’s National Centers for Environmental Information. It provides access to global and U.S. station records, daily through annual summaries, temperature and precipitation measurements, wind, degree days, radar-related data, station histories, and climate normals. Users can search by station, place, ZIP code, county, state, country, or station identifier, then download selected products or access records programmatically through the CDO API. CDO is best understood as a collection of related datasets and access services rather than one standardized geospatial layer: coverage, temporal resolution, variables, file formats, licensing details, and update timing vary by product.
NOAA Climate Data Online is a practical entry point for finding historical observations tied to real places on Earth. It connects weather and climate measurements to observing stations, locations, dates, dataset identifiers, and station histories. That makes it useful for mapping environmental conditions, building regional climate summaries, checking weather history near infrastructure, and joining observations to roads, buildings, watersheds, administrative areas, and other geographic features. It is not a global basemap, a continuous weather surface, a live forecast service, or a single normalized database. The main challenge is choosing the correct CDO dataset, station, period of record, variable, and output format before beginning analysis.
How EDK fits
For: GIS analysts, climatologists, environmental researchers, data engineers, planners, infrastructure teams, educators, and developers who need downloadable or programmatic access to historical weather and climate observations tied to geographic locations.
NOAA Climate Data Online is relevant to a world model because it adds time-indexed environmental observations to the physical places where measurements were made. CDO can help answer questions such as which observing stations are near a road, building, watershed, construction site, park, utility corridor, or other geographic feature; how precipitation or temperature varies across a region; and which locations have sufficiently long or complete records for comparison. The connection is complementary rather than substitutive: CDO supplies observations and station metadata, while a broader geographic model can provide the surrounding physical features, boundaries, infrastructure, imagery, and spatial relationships needed to interpret those observations. CDO records should not be treated as measurements available at every point on Earth, and station values should not automatically be interpolated into a continuous surface without an appropriate modeling method.
- •Join NOAA station locations and selected climate summaries to nearby roads, buildings, public assets, watersheds, vegetation, or infrastructure, then rank or filter physical features by observed climate conditions or distance to a station.
- •Aggregate station observations by a geographic region, compare periods across locations, or calculate proximity and coverage metrics to identify places that are well served—or poorly served—by available climate observations.
Dataset profile
Formats
CSV
Plain text
JSON through CDO API v2
PDF for selected reports and products
Product-specific binary formats for some radar data
Related NCEI service formats including XML, Shapefile, KMZ, and NetCDF
Access methods
CDO web search by station, location, identifier, dataset, date, or data type
Cart-based ordering and download
Climate Data Online Web Services API v2
NCEI station and product access pages
Related NCEI GIS, catalog, THREDDS, OPeNDAP, and specialized data services
Quality and limits
Station coverage is uneven and observations are not available at every geographic location.
Periods of record, variables, units, temporal granularity, and data completeness vary by product and station.
Station relocations, instrument changes, observing-practice changes, missing data, and quality-control adjustments can affect comparisons.
The most recent records may be delayed, incomplete, revised, or unavailable for some stations and datasets.
A station observation is not automatically representative of nearby buildings, roads, watersheds, or infrastructure.
CDO does not provide one universal schema, projection, update cadence, or spatial-resolution guarantee.
Some data hosted or indexed by NCEI may originate from non-federal contributors with product-specific provenance or conditions.
Analysis workflows
Select the exact CDO dataset, variable, station network, date range, units, and quality requirements before downloading.
Retrieve station metadata and observations together, preserving station identifiers, coordinates, dates, units, flags, and source dataset names.
Convert tabular observations into GIS point layers or analytical tables and join them to administrative boundaries, watersheds, roads, buildings, infrastructure, or environmental features.
Calculate nearest-station, buffer, point-in-polygon, station-density, seasonal, annual, anomaly, or climate-normal summaries.
Assess missingness, period-of-record overlap, station history, instrument changes, and data revisions before comparing locations or time periods.
Use interpolation or gridded modeling as a separate documented process rather than assuming CDO station values form a continuous surface.
Record dataset identifiers, station identifiers, access dates, request parameters, product versions, and citations for reproducibility.
Value inside EDK
What NOAA Climate Data Online contains
Climate Data Online provides free access to NOAA’s archive of historical weather and climate data, including station history information. NOAA describes the collection as including quality-controlled daily, monthly, seasonal, and yearly measurements of temperature, precipitation, wind, and degree days, as well as radar data and 30-year Climate Normals. The system also exposes station and location metadata that help users identify where observations were collected. (ncei.noaa.gov)
The CDO ecosystem is organized around several related concepts: datasets, data categories, data types, locations, stations, and individual data records. A station is an observing platform; a location may be a city, county, state, country, ZIP code, or other geographic entity; and a data record represents an observed value with associated attributes at a place and time. This structure matters in GIS because a station point is not the same thing as a climate region, a modeled raster cell, or a measurement applicable to every nearby feature. (ncei.noaa.gov)
- •Station observations and station-history metadata
- •Daily, monthly, seasonal, and annual summaries
- •Temperature, precipitation, wind, snowfall, degree days, and related variables
- •U.S. Climate Normals and selected international or territorial products
- •Selected radar, marine, and climatological data products
- •Location and station search by name, identifier, ZIP code, administrative area, or coordinates
Geography, temporal coverage, and update cadence
CDO has global reach for some datasets, but coverage is not uniform. NOAA states that CDO provides access to global historical weather and climate data, while specific products may be limited to the United States, U.S. territories, selected international stations, marine platforms, or particular observing networks. The available period of record also varies substantially by station and variable: some stations have long historical records, while others are newer, intermittent, relocated, or specialized. (ncei.noaa.gov)
The primary geographic object is often a station or platform rather than a polygon or regularly spaced raster. Station coordinates, identifiers, observation methods, periods of record, and metadata should be retained when records are exported. NOAA’s station-history resources are particularly important when a long series includes moves, instrument changes, observing-practice changes, or gaps. A nearby station is not automatically representative of a target site, especially across elevation changes, coastlines, urban heat islands, mountains, or strong precipitation gradients.
- •Global availability exists for some products, while others are U.S.-only or network-specific.
- •Spatial resolution is commonly station-based; CDO is not automatically a continuous grid.
- •Periods of record differ by station, variable, and dataset.
- •The latest standard U.S. Climate Normals period is 1991–2020.
- •Update timing is dataset-specific rather than governed by one CDO-wide schedule.
Download options, file formats, and access methods
Users can search CDO through the web interface by station, location, identifier, date range, dataset, or data type. Search results can be added to a cart and ordered for download. NOAA’s interface documents CSV and text outputs for many products, PDF for certain report-style products, and product-specific binary delivery for radar data. The exact format options depend on the selected dataset and product. (ncei.noaa.gov)
For programmatic access, the CDO Web Services API v2 provides endpoints for datasets, data categories, data types, locations, stations, and data. API responses are JSON and include result metadata such as counts, limits, and offsets. An access token is required. NOAA documents a limit of five requests per second and 10,000 requests per day per token, so a robust workflow should use pagination, caching, retries with backoff, and a local record of completed requests. (ncei.noaa.gov)
- •Web search and cart-based ordering for selected date ranges and stations
- •CSV and plain-text downloads for many tabular products
- •PDF reports for selected climatological products
- •JSON through the CDO API v2
- •Related NOAA services with product-specific JSON, XML, Shapefile, KMZ, or NetCDF access
- •Station and product metadata that should be stored with downloaded observations
Suitable GIS and spatial-analysis workflows
A defensible GIS workflow begins with product selection rather than map display. First identify the variable, temporal unit, dataset identifier, station network, period of record, and quality requirements. Then retrieve station metadata and observations together. Preserve station identifiers, coordinates, elevation where supplied, observation dates, units, flags, and source dataset names before converting records into a GIS point layer or analytical table.
For local analysis, station points can be joined to administrative boundaries, watersheds, road corridors, building inventories, public assets, land-cover classes, or infrastructure features. Common operations include nearest-station searches, buffer summaries, point-in-polygon aggregation, station-density mapping, date-range filtering, missing-value assessment, and comparison of climate statistics among regions. A proximity result should be described as proximity to an observing station—not as proof that the station’s measurements represent every feature inside the buffer.
- •Create a station point layer from coordinates and retain the original identifiers.
- •Join observations to administrative areas, watersheds, infrastructure, buildings, or other physical features.
- •Filter by date, variable, station network, quality flag, and period of record before aggregation.
- •Use time-aware summaries for seasonal, annual, anomaly, or climate-normal analysis.
- •Validate units, missing values, station moves, and changes in observing practice.
- •Use interpolation or gridded modeling only as a separate, documented analytical step.
License, strengths, and tradeoffs
NOAA’s NCEI Open Data Policy states that environmental data and information produced by NOAA or another federal agency are available openly unless an explicit legal, regulatory, or policy exception applies, and that these data are in the public domain in the United States. NCEI also works to apply CC0 for international users where appropriate. This policy does not mean that every record hosted by NCEI has identical provenance or terms: datasets supplied by non-federal contributors can have separate rights or conditions, so the product metadata should remain part of the citation and distribution workflow. (ncei.noaa.gov)
The main strength of CDO is breadth combined with several access paths: a human-facing search interface, downloadable products, APIs, station metadata, and specialized tools. The main tradeoff is heterogeneity. Different datasets use different identifiers, variables, units, temporal structures, formats, quality rules, and geographic coverage. A successful workflow treats CDO as a catalog of related climate-data products, not as a single analysis-ready geospatial schema.
- •Strength: Broad historical coverage across many weather and climate observation networks.
- •Strength: Search, download, API, station metadata, and specialized access tools support different workflows.
- •Strength: Many NOAA-produced records are openly available and reusable in the United States.
- •Tradeoff: Coverage, variables, formats, quality controls, and update timing vary by dataset.
- •Tradeoff: Station observations are spatially sparse and may not represent nearby locations without additional modeling.
- •Tradeoff: Historical comparisons can be affected by missing data, station moves, instrument changes, and changing observing practices.
Questions teams ask
Is NOAA Climate Data Online one dataset or many datasets?
It is an access and discovery system for multiple NOAA weather and climate datasets. The available variables, periods of record, station networks, formats, geographic coverage, and quality rules depend on the specific product selected.
Can I download NOAA Climate Data Online data as CSV?
Many CDO products support CSV or text downloads, but the exact options depend on the dataset and product. Some report-style products are available as PDF, and radar or other specialized products may use different delivery formats. Check the selected product’s download options before designing an automated workflow.
How do I access CDO programmatically?
Use the Climate Data Online Web Services API v2. It exposes endpoints for datasets, data categories, data types, locations, stations, and observations, returns JSON, requires an access token, and documents rate limits of five requests per second and 10,000 requests per day per token.
Can I use a CDO station value as the climate value for a nearby building or road?
Only with an explicit interpretation. A nearby station provides an observation at the station location, not a guaranteed measurement for every nearby feature. Distance, elevation, land cover, coastal exposure, urban effects, station history, and weather patterns can all affect representativeness. For broader geographic estimates, use a documented interpolation, gridded product, or modeling workflow.
Keep exploring
noaa climate data online analysis workflow
A complementary workflow page focused on selecting CDO products, validating station records, and performing reproducible spatial analysis.
global surface water analysis workflow
Pairs station-based climate observations with satellite-derived surface-water history for hydrology, floodplain, and environmental analysis.
landsat collection 2 analysis workflow
Provides an imagery-based environmental layer that can be combined with climate observations for vegetation, water, urban, and land-change studies.
Sources
NOAA Climate Data Online
Official overview of CDO coverage, historical weather and climate data, station history, climate summaries, radar data, and Climate Normals.
Open sourceClimate Data Online Web Services API v2 Documentation
Official API documentation covering endpoints, JSON responses, access tokens, pagination, and rate limits.
Open sourceNCEI Web Services
Official inventory of CDO APIs and related NCEI services and formats, including CSV, JSON, XML, Shapefile, KMZ, and NetCDF pathways.
Open sourceU.S. Climate Normals
Official documentation for the 1991–2020 normals, station coverage, decadal production cycle, access methods, and interpretation.
Open sourceNCEI Open Data Policy
Official policy describing public access, public-domain status in the United States, and treatment of NOAA and contributed environmental data.
Open source