Data and credits

PAxMan is built on a small number of open datasets and services. This page records where each one came from and what its licence asks for. Attribution here is a requirement of those licences, not a courtesy.

Airport data

The list of airports in PAxMan — around 5,500 of them, with their codes, cities, countries, coordinates and time zones — is derived from the OpenFlights airport database.

• Source: https://openflights.org/data.html
• Licence: Open Database License (ODbL) v1.0 — https://opendatacommons.org/licenses/odbl/1-0/
• Contents of the individual records are under the Database Contents License.

PAxMan uses a filtered subset: entries that are real airports and that have both a usable IATA code and a valid IANA time zone, because the app needs the time zone to work out local arrival time. Nothing was added to the records.

Under the ODbL, this is a Derivative Database. It is credited here, and the filtering script that produces it is published with the app's source (tools/build_airports.py) so the derivation can be reproduced.

Weather

Destination forecasts come from Open-Meteo.

• Source: https://open-meteo.com
• Licence: CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/
• Terms: https://open-meteo.com/en/terms

Open-Meteo's forecasts are built on data from national weather services, including the German Weather Service (DWD), NOAA, Météo-France, ECMWF and others. It requires no key and no account, and PAxMan sends it nothing but a latitude, a longitude and a date range.

This is not aviation meteorological data. It is not a METAR, a TAF or any approved product, and it must never be used for an operational decision.

Time zones

Local times are worked out with the IANA Time Zone Database, through the operating system's own time zone support.

• Source: https://www.iana.org/time-zones
• The database is in the public domain.

Writing engines

The built-in PixelWriter engine is PAxMan's own and runs entirely on the device. If you choose another engine in Setup, your briefing is written by that provider's model under their own terms, using an API key you supply. PAxMan is not affiliated with any of them.

Everything else

The pixel typeface, the artwork, the icon, the fact set and the briefing engine were written for PAxMan.

Built with love by Pat — www.soypat.es