IWXXM explained: the XML form of METAR, SPECI and TAF
IWXXM is the ICAO Meteorological Information Exchange Model, a WMO-maintained XML representation of aviation weather reports such as METAR, SPECI and TAF, described as the official representation required by ICAO Annex 3. It carries the same content as the text codes in a machine-readable form, and text reports remain in use alongside it.
Key points
- IWXXM is published by the WMO as an information model for the operational exchange of aviation weather data, with XML schemas and Schematron rules.
- The 2025-2 release has a METAR and SPECI package at version 3.2.0 and a TAF package at version 3.0.2, matching Amendment 82 of Annex 3.
- ICAO Council adopted Amendment 79 to Annex 3 on 9 March 2020, with an applicability date of 5 November 2020 and some provisions on 4 November 2021.
- The US National Weather Service issues TAFs in both traditional alphanumeric code and IWXXM, using FT and LT in the bulletin heading.
- The sources read do not say that text codes are withdrawn, so this page describes IWXXM as an addition, not a replacement.

What IWXXM is
IWXXM is the ICAO Meteorological Information Exchange Model. The World Meteorological Organization describes it on its site as an information model designed for the operational exchange of meteorological information for aviation. It includes representations for METAR, SPECI and TAF, among other products, and is described as the official representation of the meteorological information required by ICAO Annex 3.
The key word is representation. A METAR carries a fixed set of facts: an aerodrome, a time, wind, visibility, weather, cloud, temperature and pressure. The text code writes them in a compact line made for teletype links, as the history of the METAR explains. IWXXM writes the same kind of facts in XML, where each fact has a named element, a unit attribute and a defined place in a schema. A program can check the structure without guessing where a group ends.
Why a second form exists
The text codes were designed for people and for narrow communication links. They are brief, but a machine must parse them with rules and exceptions, and national variants add more rules, as the parsers page shows. A model-based representation removes ambiguity. Validation is possible with a schema, and Schematron rules can express checks that a schema alone cannot, for instance that a value must be present when a related flag is set.
The WMO repository describes itself as XML schema and Schematron for aviation weather data exchange. Documentation on the WMO site describes the model with UML and GML, though the details of the encoding are in the schemas and are not summarized here.
Timeline of what is documented
| Date | Event | Source |
|---|---|---|
| 9 March 2020 | ICAO Council adopted Amendment 79 to Annex 3 | WMO Amendment 79 page |
| 20 July 2020 | Effective date of Amendment 79 | WMO Amendment 79 page |
| 5 November 2020 | Applicability date | WMO Amendment 79 page |
| 4 November 2021 | Embedded applicability date of some provisions | WMO Amendment 79 page |
| 2 June 2023 | GitHub release v2023-1 of the schemas | GitHub |
| 25 November 2025 | GitHub release v2025-2 of the schemas | GitHub |
The WMO page for Amendment 79 says the amendment aligns the WMO regulations with ICAO's Amendment 79 to Annex 3, and that the text of the ICAO amendment is the basis for the WMO one. The table lists documented dates only. It does not give the date of the first IWXXM release, because none of the sources read gives one.
Versions
The WMO site and its version table link each IWXXM version to an amendment of Annex 3. The table maps earlier versions to Amendments 76 to 82. The 2025-2 release is described as having a METAR and SPECI package at version 3.2.0 and a TAF package at version 3.0.2, and as corresponding to Amendment 82 of Annex 3. Since version 3.0 the packages for different report types are versioned separately, so a single release number does not give the version of each package. A program must record which package version it validates against.
The regulations page explains how Annex 3 amendments, WMO manuals and national rules fit together, and why the XML form follows the Annex.
Where IWXXM appears in practice
Two public examples are documented. The Aviation Weather Center Data API lists IWXXM among the output formats for METAR, TAF and AIRMET. See the data sources page for its limits. And the US National Weather Service instruction on TAFs, NWSI 10-813 dated 30 October 2024, says forecast offices disseminate TAFs in both traditional alphanumeric code and IWXXM. In the bulletin heading, FT designates a TAC product and LT designates the message in IWXXM.
The same instruction ties US practice to ICAO Annex 3, the WMO Technical Regulations, the WMO Manual on Codes and FAA regulations. The WMO library page lists WMO-No. 306 Volume I.3, Part D, representations derived from data models, dated 2023, which is the manual part where the data-model representations are filed.
Reading IWXXM
A human reader rarely needs the XML, since the same report is available as text or decoded by an interface such as the METAR decoder. A developer, though, may need it for two reasons. Validation: a message can be tested against the schema and Schematron rules. Interchange: an agency that exchanges data with others can rely on a defined model.
A schematic report
The following outline shows the shape of an IWXXM METAR in plain words. It is conceptual. Element names and namespaces are versioned and are in the schemas.
report
report status (for example normal, amended, corrected)
issue and observation times
aerodrome (identifier, name, location)
observed conditions
wind (direction, speed, gust, units)
visibility (value, units)
present and recent weather
cloud layers
air temperature and dew point
pressure (QNH)
trend forecast, when the report has one
remarks, when the report has them
In real reports
A text METAR such as the examples on the how to read a METAR page can be matched to this outline group by group. The wind group fills the wind block, the visibility group fills the visibility block, the cloud groups fill the layer list, and the temperature and pressure groups fill the last two. How modifiers such as AUTO or COR are encoded is specific to each schema version and was not checked.
Method and limits
- The WMO IWXXM page and version table were read in summary. They give no calendar dates for versions or for Annex 3 amendments, so the only dates in the timeline come from the Amendment 79 page and from GitHub releases.
- Secondary sources seen during research give other applicability dates for IWXXM provisions, for example 4 November 2021 as a general date and 12 August 2021 for the European Union. They conflict with each other in part and were not used beyond the Amendment 79 page.
- The licence of the GitHub repository and of the WMO page was not stated on the pages read.
- No schema was opened and no sample IWXXM document was validated. The outline above is not a schema extract.
- The sources do not say whether text METAR and TAF will be withdrawn. No end date for text is given.
- ICAO Annex 3 itself is sold by ICAO and was not read. Its current edition and amendment number were not verified, beyond what the WMO pages state.
Training and reference only. For flight planning, always use official briefing sources (your national weather service, AIS or approved provider).
Frequently asked questions
What does IWXXM stand for?
IWXXM stands for ICAO Meteorological Information Exchange Model. The WMO describes it as an information model designed for the operational exchange of meteorological information for aviation, with representations for reports and forecasts such as METAR, SPECI and TAF, expressed in XML.
Does IWXXM replace the text METAR and TAF?
The sources read for this page do not state that text codes are withdrawn. The US NWSI 10-813 instruction says forecast offices disseminate TAFs in both traditional alphanumeric code and IWXXM, so the two forms coexist. Rules in other countries were not checked.
Where can the IWXXM schemas be downloaded?
The WMO maintains an open repository on GitHub named wmo-im/iwxxm, described as XML schema and Schematron for aviation weather data exchange. Its latest release at the consultation date was v2025-2, published on 2025-11-25. No license file is indicated on the repository page.
Can a pilot get IWXXM from the AWC API?
Yes for some products. The Aviation Weather Center Data API page lists IWXXM among the output formats for METAR, TAF and AIRMET. It is an XML document intended for software, not for reading in flight, and the plain text form remains available through the same API.
Sources
- World Meteorological Organization (2025). IWXXM, ICAO Meteorological Information Exchange Model
- WMO Community (2025). IWXXM version table
- GitHub, WMO Integrated Mapping (2026). wmo-im/iwxxm repository
- WMO Community (2026). Amendment 79 to the Technical Regulations, WMO-No. 49, Volume II
- National Weather Service, NOAA (2024). NWSI 10-813, Terminal Aerodrome Forecasts
- NOAA National Weather Service, Aviation Weather Center (2026). Aviation Weather Center Data API