Do I need an account with NOAA?

Yes. You connect your own NOAA account once, from Ingest, and the data comes from what that account can see.

How fresh is the data?

As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.

Will running it again create duplicate rows?

No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.

Do I need to write code?

No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

NOAA

Weather

Ready to use

NOAA data, published as NOAA publishes it. Ingest delivers this data to a data warehouse you own as 6 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What you get

Table	Each row is
datacategories `datacategories`	All CDO data categories (Annual Agricultural, Annual Precipitation, ...). Small reference list; each run re-reads it whole and merges on the category id.
datasets `datasets`	All CDO datasets (e.g. GHCND Daily Summaries). Small, slowly changing reference list; each run re-reads the whole list and merges on the dataset id.
datatypes `datatypes`	All CDO data types (TMAX, TMIN, PRCP, ...) with their available date ranges. Reference list of about 1,566 rows; each run re-reads it whole and merges on the data-type id.
locationcategories `locationcategories`	All CDO location category codes (City, County, Climate Division, ZIP, ...). Small reference list; each run re-reads it whole and merges on the category id.
locations `locations`	All CDO locations (country, state, county, city, ZIP, climate division and region) with their available date ranges. About 38,862 rows; each run reads the whole list and merges on the location id (e.g. ZIP:97495). Names repeat across locations, so the id is the identity.
stations `stations`	All CDO stations (about 156,907 rows) with coordinates, elevation and their available date ranges. Each run reads the whole list and merges on the station id (e.g. COOP:010008, WBAN:34061); coordinates are not unique, so the id is the identity.

How it works

Choose NOAA. Connect your NOAA account once, from Ingest.
Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
Pick a schedule. Daily is the default, and weekly and monthly are there too.
Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

Do I need an account with NOAA?: Yes. You connect your own NOAA account once, from Ingest, and the data comes from what that account can see.
Which warehouses can NOAA data go to?: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?: As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?: No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
Do I need to write code?: No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

For your data team: technical reference

Connector noaa, version 0.1.0, a REST source, status beta, authentication api_key.

Vendor documentation: https://www.ncei.noaa.gov/cdo-web/webservices/v2

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`datacategories` All CDO data categories (Annual Agricultural, Annual Precipitation, ...). Small reference list; each run re-reads it whole and merges on the category id.	beta	full	merge	`id`	-
`datasets` All CDO datasets (e.g. GHCND Daily Summaries). Small, slowly changing reference list; each run re-reads the whole list and merges on the dataset id.	beta	full	merge	`id`	-
`datatypes` All CDO data types (TMAX, TMIN, PRCP, ...) with their available date ranges. Reference list of about 1,566 rows; each run re-reads it whole and merges on the data-type id.	beta	full	merge	`id`	-
`locationcategories` All CDO location category codes (City, County, Climate Division, ZIP, ...). Small reference list; each run re-reads it whole and merges on the category id.	beta	full	merge	`id`	-
`locations` All CDO locations (country, state, county, city, ZIP, climate division and region) with their available date ranges. About 38,862 rows; each run reads the whole list and merges on the location id (e.g. ZIP:97495). Names repeat across locations, so the id is the identity.	beta	full	merge	`id`	-
`stations` All CDO stations (about 156,907 rows) with coordinates, elevation and their available date ranges. Each run reads the whole list and merges on the station id (e.g. COOP:010008, WBAN:34061); coordinates are not unique, so the id is the identity.	beta	full	merge	`id`	-

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Get NOAA data into your warehouse

Last updated 2026-10-16.