Access NOAA's Climate Data Online (CDO) API at ncei.noaa.gov/cdo-web/api/v2/ using a free token requested at ncei.noaa.gov/cdo-web/token; the CDO API provides access to NOAA's full archive of historical station-level climate data including daily HDD and CDD.
Query the GHCND (Global Historical Climatology Network - Daily) dataset for the target weather station using GET /data?datasetid=GHCND&stationid={stationid}&startdate={YYYY-MM-DD}&enddate={YYYY-MM-DD}&datatypeid=HDD,CDD&limit=1000; note that HDD and CDD in GHCND are computed relative to a 65°F (18.3°C) base temperature.
Identify the nearest suitable weather station using the /stations endpoint filtered by location (latitude/longitude bounding box or FIPS code) and datasetid=GHCND; select a station with long record completeness and minimal missing data for the load forecasting period.
For weekly and monthly aggregate degree day summaries and forecasts, supplement CDO data with NOAA's Climate Prediction Center (CPC) degree day products at cpc.ncep.noaa.gov/products/analysis_monitoring/cdus/degree_days/; these provide regional summaries and seasonal forecasts but without a JSON API.
For custom base temperatures (e.g., 60°F for a particular building type), derive HDD and CDD from hourly dry-bulb temperature data using the NOAA ISD (Integrated Surface Data) dataset, available from ncei.noaa.gov/products/land-based-station/integrated-surface-database.
Join degree day data to your load time series by date and station proximity; validate the degree day–load correlation before using in a forecasting model, as correlation degrades for highly insulated or process-dominated facilities.
Known gotchas
NOAA CDO station data frequently contains missing values, especially for older or rural stations; the HDD and CDD fields in GHCND are not interpolated — missing days must be filled by your pipeline using adjacent station data or reanalysis products (e.g., ERA5) before regression modeling.
The GHCND HDD and CDD datatypes are computed using a fixed 65°F base; if your load model requires a different base temperature, you cannot use the pre-computed GHCND values and must instead derive degree days from raw temperature records (TMAX, TMIN, or hourly ISD data).
CPC regional degree day products are published as flat text files, not a REST API; any integration must scrape or parse fixed-format text files that may change layout without versioned notice — treat them as best-effort supplementary data rather than a primary pipeline source.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp