METAR and TAF data sources: APIs, cache files and archives

Tafrob editorial team · Updated · 7 min read

Short answer

Current METAR and TAF data is available from the Aviation Weather Center Data API, limited to 100 requests per minute, 400 entries per request and 30 days of history, or from gzipped cache files updated once a minute. For older reports, the Iowa Environmental Mesonet, NOAA ISD and Ogimet offer archives.

Key points

  • The AWC Data API is rate limited to 100 requests per minute, returns at most 400 entries on most endpoints and covers the previous 30 days.
  • Cache files such as metars.cache.csv.gz and tafs.cache.xml.gz are updated once a minute and suit bulk downloads.
  • The Iowa Environmental Mesonet archive adds older observations but states that very little quality control is done.
  • NOAA ISD merges more than 100 original sources and has a record starting in 1901, with gaps at many stations.
  • Ogimet serves METAR, SPECI and TAF text for a chosen period and says its data should not be used for any critical mission.
Close-up of colored HTML and JavaScript source code on a dark screen
Photo: Martin Vorel, CC BY-SA 4.0, via Wikimedia Commons

Four kinds of source

Raw METAR and TAF text is published by national weather services and then redistributed by several organizations. Which source fits depends on one question: current or historical. A flight-planning tool needs the latest report and tolerates no delay. A statistics project needs months or years of reports and tolerates gaps. This page compares the sources that were opened for this review: the Aviation Weather Center Data API and cache files, the Iowa Environmental Mesonet archive, NOAA's Integrated Surface Database and the Ogimet retrieval form. Each description reflects the pages as read on 2026-11-19, and limits can change.

The Aviation Weather Center Data API

The Aviation Weather Center, part of the US National Weather Service, documents a REST interface under /api/data. Its page gives one complete example, https://aviationweather.gov/api/data/metar?ids=KMCI&format=json, and points to an OpenAPI description at /data/schema/openapi.yaml for the other endpoints. The products named on the page include METAR, TAF, pilot reports, SIGMET, G-AIRMET, AIRMET for Alaska, area forecasts, center weather advisories, station information and airport information.

The output format depends on the product. For METAR the page lists raw text, JSON, GeoJSON, CSV, XML and IWXXM. For TAF it lists raw text, JSON, GeoJSON, XML and IWXXM. The IWXXM page explains what that last format is.

The page states the constraints in plain words:

  • All requests are rate limited to 100 requests per minute.
  • Most endpoints return a maximum of 400 entries.
  • The weather database allows access to up to the previous 30 days of data.
  • Cross-origin resource sharing is not permitted at this time.
  • Undocumented query parameters are restricted and produce an error.
  • Exceeding request limits results in access being blocked.

It also recommends setting a custom user agent so that automated filtering does not block valid traffic. Only the ids and format parameters appear on the page itself. Other parameters exist in the OpenAPI description, and this page does not list them because they were not read there.

The cache files

For anything larger than a few hundred reports, the API page itself points to cache files. They are gzipped snapshots of everything current:

File Content Update
metars.cache.xml.gz and metars.cache.csv.gz All current METARs Once a minute
tafs.cache.xml.gz All current TAFs, XML Once a minute
sigmets.cache.xml.gz and .json.gz All current SIGMETs Once a minute
gairmets.cache.xml.gz Current CONUS G-AIRMETs Once a minute
aircraftreports.cache.xml.gz and .csv.gz Current AIREPs and PIREPs Once a minute
stations.cache.xml.gz and .json.gz Station listing Once a day

A cache file is a picture of the present, not an archive. Someone who wants a history has to save these files at a regular interval, which is how this site builds its own statistics, described on the METAR statistics and TAF statistics pages. The cache directory page itself could not be opened directly during this review, so the table above comes from the list on the API page.

Iowa Environmental Mesonet

The Iowa Environmental Mesonet at Iowa State University offers a download form for airport observations labeled ASOS, AWOS and METAR. Selectable fields include temperature, dew point, relative humidity, wind direction, speed and gusts, altimeter, sea-level pressure, visibility, sky cover and height for four levels, present weather codes and the raw METAR. Report types include routine hourly reports and specials, plus a MADIS high-frequency option. A separate one-minute dataset is described for US ASOS from 2000 and for Iowa AWOS from 1995 to 2011.

Two statements on the form matter to anyone doing analysis. First, the archive is described as a collection of observations as received, with very little quality control. Missing values, marked M, can mean the value was missing, failed quality control or was never reported. Second, the form limits a download without station selection to a 24-hour period of all data, and a selection of stations to 1,000 station-years in aggregate. The form does not state a licence or a citation requirement. It links to a disclaimer that was not read for this review.

The form says precipitation is unavailable for non-US sites, which is a reminder that decoded fields depend on remarks that only some countries include. See the remarks page for the US additions.

NOAA Integrated Surface Database

NOAA's National Centers for Environmental Information describe the Integrated Surface Database, or ISD, as a global collection of surface observations compiled into a single ASCII format and common data model. Its page gives three station figures: over 35,000 stations have contributed historically, more than 14,000 are active and updated daily, and the Global Hourly product has data from more than 20,000 stations. The record starts in 1901, with many stations showing gaps. The database integrates more than 100 original data sources, including paper forms key-entered decades ago.

Access ranges from a data access application to bulk downloads over HTTPS and several web services. ISDLite is a derived fixed-width subset with eight common surface parameters. The database is a climate archive, so it fits studies of conditions rather than the verbatim text of a METAR. The page contains no licence text and no use restrictions, only a link to a quality control document.

Ogimet

Ogimet is a private site that offers a query form for METAR, SPECI and TAF text. A user enters one or more ICAO location indicators, picks a type (all, METAR and SPECI, SPECI only, short TAF or long TAF), sets a start and end in UTC, and chooses HTML or plain text. Years from 2005 to 2028 appear in the selector. The page says the information is merely informative and that no critical mission should use it. It carries a copyright notice and links to a license page and a documentation page that were not read here. The page says nothing about automated access or rate limits, so a script should not assume that bulk retrieval is allowed.

National open data

Many national weather services publish their own observation and forecast data, and some also operate APIs with registration. Meteorological offices differ on licence, format and latency. No national portal other than the US sources above was successfully read for this review, so none is described here. The ICAO airport codes page explains how location indicators map to countries, which is the first step to finding the right national source.

Choosing and combining sources

Need Likely fit Main caveat
Latest report for one or a few stations AWC Data API 100 requests per minute, 400 entries
Snapshot of every current report AWC cache files No history
Hourly archive of US and some world stations Iowa Environmental Mesonet Little quality control
Climate-style archive since 1901 NOAA ISD Gaps, no verbatim text
TAF and METAR text for a past period Ogimet Not for critical use

A pipeline that needs both freshness and history usually combines two sources: the cache files for the present, and an archive to backfill. Reports from different sources can differ in small ways, for instance in whether corrected reports replace the originals, so a merge should key on station, issue time and report type. Decoding the raw text is a separate step, covered on the parsers page. Units also vary by country, as the units page shows.

A schematic report

The following is a schematic request and response, not a captured live example. It uses the one URL pattern documented on the API page.

GET https://aviationweather.gov/api/data/metar?ids=KMCI&format=json
User-Agent: a descriptive name of the client application

200 OK
[ { one object per report, holding the station,
    the observation time, the raw text and
    the decoded fields } ]

The number of objects is capped, and the exact field names should be read from the OpenAPI description rather than assumed.

In real reports

A raw METAR or TAF from any of these sources starts with the same elements: a type word, a four-letter location indicator, a day and time group and then the body. The same report can appear as text from Ogimet, as a row with a raw METAR column from the Iowa archive, or as XML from the API. The METAR decoder shows the groups one by one.

Method and limits

  • The AWC API page was read on 2026-11-19. The cache directory page returned an error when opened directly, so file names and update rates come from the API page.
  • No licence or terms of reuse for AWC data were found on the pages read. Anyone redistributing data should check the current terms.
  • The Iowa and NOAA pages were read in summary form. The Iowa disclaimer, the Ogimet license and documentation pages, and the NOAA quality control document were not opened.
  • No national open data portal, including the French one, could be verified. None is described.
  • Endpoint parameters other than ids and format, and exact JSON field names, were not read and are not stated.
  • Limits and archive coverage change over time. Treat the figures as of the consultation date.

This page is educational. It is not a source for operational weather decisions.

Training and reference only. For flight planning, always use official briefing sources (your national weather service, AIS or approved provider).

Frequently asked questions

Is there an official free API for METAR and TAF?

The Aviation Weather Center, part of the US National Weather Service, runs a REST Data API under /api/data. It serves METAR and TAF in several formats, including JSON and IWXXM. Its documentation sets a 100 requests per minute limit and blocks users who exceed it.

How far back can the AWC Data API go?

The API page states that the weather database allows access to up to the previous 30 days of data. Longer histories need another source, such as the Iowa Environmental Mesonet archive, NOAA ISD or the Ogimet retrieval form, each with its own coverage and quality notes.

Can a web page call the AWC API directly from the browser?

The API page says cross-origin resource sharing is not permitted at this time. A script running in a browser on another domain is therefore expected to be blocked, and requests usually go through a server that sets a custom user agent and respects the rate limit.

Which source suits statistics over many months?

The AWC cache files hold only current reports, and the API only 30 days, so a long study needs either regular snapshots saved over time or an archive such as the Iowa Environmental Mesonet or NOAA ISD. Each archive differs in coverage, completeness and quality control.

Sources

  1. NOAA National Weather Service, Aviation Weather Center (2026). Aviation Weather Center Data API
  2. Iowa State University, Iowa Environmental Mesonet (2026). IEM ASOS/AWOS/METAR data download
  3. NOAA National Centers for Environmental Information (2026). Integrated Surface Database (ISD)
  4. Ogimet (2026). METAR and TAF retrieval form