=== Leadovation Aero Weather METAR TAF ===
Contributors: wptechnology
Tags: metar, taf, aviation, weather, aeronautical
Requires at least: 6.0
Tested up to: 7.1
Requires PHP: 8.0
Stable tag: 1.8.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Aeronautical METAR and TAF weather for WordPress: live data, flight categories, shortcodes and Gutenberg blocks.

== Description ==

Leadovation Aero Weather METAR TAF displays aeronautical observations (METAR) and forecasts (TAF) for any aerodrome, by its ICAO code, on your WordPress site. Built for flying club, flight school, FBO and pilot websites.

There is no cap on the number of aerodromes, no cap on the number of displays, and no screen that switches off:

* Raw METAR and raw TAF for any ICAO code.
* Plain-language decoding of METAR and TAF: wind, visibility, clouds, temperature, QNH.
* Flight category badge (VFR / MVFR / IFR / LIFR), NOAA profile by default or an indicative European metric profile.
* Tabbed panel, compact view, category pill, single data field, aerodrome details, webcam, visitor selector.
* Eleven shortcodes, six Gutenberg blocks, one widget and two template tags.

A paid Pro version is sold separately, and it is an add-on rather than a key: it installs alongside and brings nine more displays with it, built on the club's own minima and runways, plus six native Avada / Fusion Builder elements, updates and priority support.

**Disclaimer.** The data is provided for information only and is not an official source for flight preparation. Always consult approved sources (national weather service, AIS, NOTAM). The VFR/MVFR/IFR/LIFR categories are a display convention (NOAA reference) and do not represent EASA/SERA regulatory minima.

== External services ==

This plugin fetches METAR and TAF data from the public API of the NOAA Aviation Weather Center (aviationweather.gov).

* Endpoints: https://aviationweather.gov/api/data/metar and https://aviationweather.gov/api/data/taf
* Data sent: the requested ICAO code or codes (for example LFPN), when a widget is displayed, when the plugin dashboard is opened in the WordPress admin, or when the cache is refreshed.
* No personal data is sent.
* Service: NOAA Aviation Weather Center, https://aviationweather.gov
* Terms and notices: https://www.weather.gov/disclaimer

The plugin also fetches aerodrome information (runways, elevation, frequencies) from the public API of the NOAA Aviation Weather Center.

* Endpoint: https://aviationweather.gov/api/data/airport
* Data sent: the ICAO code of the requested aerodrome (for example LFPN), cached server-side for 30 days.
* No personal data is sent.
* Service: NOAA Aviation Weather Center, https://aviationweather.gov
* Terms and notices: https://www.weather.gov/disclaimer

These are the only two services the plugin calls. The webcam image used by the `[aero_weather_webcam]` shortcode is an address the site administrator enters in the settings; the plugin neither chooses it nor calls anything of its own.

== Installation ==

1. Install the plugin from the WordPress Plugins screen, or upload the folder to `wp-content/plugins/`.
2. Activate the plugin.
3. Use the `[aero_weather taf LFPN]` shortcode (or a Gutenberg block) on a page or a post.

== Frequently Asked Questions ==

= Is the data official? =

No. It is provided for information only. For flight preparation, always refer to approved sources (national weather service, AIS, NOTAM).

= Do I need an API key? =

No. The data comes from the free, public NOAA API.

= Is anything locked behind a licence? =

No. Nothing here is closed, counted or timed: what this package carries, it carries in full, for any number of aerodromes. The Pro version is a separate add-on that brings its own displays with it; this package contains neither them nor anything that refuses them.

= For developers =

The plugin exposes two template-tag functions for theme integrators:

```
<?php echo aero_weather_metar( 'LFPN', 'decoded' ); ?>
<?php echo aero_weather_taf( 'LFPN' ); ?>
```

These are equivalent to the unified `[aero_weather]` shortcode and use the same views (raw, decoded, data, compact, badge, panel). An unknown view falls back to 'raw'.

== Changelog ==

= 1.8.0 =
* The test bench now lists only the displays this package carries. It described twenty-one, including the nine that left the free package in 1.5.0: copying one of those handed you a shortcode nothing registers, and the published package carried the named list of the paid features. The paid add-on registers its own through the `aero_weather_bench_features` filter.
* The "Max" pills are gone, along with the three usage tabs that held nothing but paid displays. An empty tab told the visitor something was missing.
* The Pro cards and this readme now say what the free package holds and what the paid one adds. Three of them still claimed every display was included.

= 1.7.0 =
* The source strings are now in English, as the directory expects, and French moved to a translation catalogue in /languages. A French site reads exactly what it read before.
* Every string that carries a placeholder now has a translators comment.

= 1.4.0 =
* WordPress.org directory compliance: no display is conditioned on a licence any more. The tier map, the two licence functions and the fifteen refusals they commanded are gone. Decoding, panel, table, timeline, screen mode, Go/No-Go thresholds, aerodrome groups, club colour and logo are open to everyone.
* The paid Pro version is now only what it actually added on its own: the six Avada / Fusion Builder elements, updates and support.
* The published package is built by a script, and a test reopens the produced archive to check what it does and does not contain.
* This readme is now in English, as the directory requires.

= 1.3.0 =
* The admin screen adopts the aero product line design.

= 1.2.0 =
* Public names (shortcodes, options, hooks, CSS classes) join the aero product line.

= 1.1.0 =
* The plugin joins the aero product line: shared core, registry, roles.

= 1.0.0 =
* First release under the WPTechnology brand (derived from WPTafMetar2).
* Unified flight category engine (NOAA and European metric profiles).
* Optional, editable "for information only" disclaimer.
