What our guides cover
Our travel guides cover destinations (how they are made): things to do, where to stay, food, the best time to visit, month-by-month weather, itineraries and day trips. Airport and route guides describe airports, routes between cities, getting from the airport into town, the airports near a city or in a country, and comparisons between two airports. Research and data stories analyse our data across the world, and articles explain travel concepts and decisions. Our trip tools run the same calculations for the places you choose.
Guides help you decide before you search. Their own text never quotes fares: live prices appear when you run a search, and the flight-price calendar some travel guides embed shows a partner’s cached results, not guaranteed prices.
Where the data comes from
- OurAirports open data (OurAirports (David Megginson and contributors); Public Domain) — Community-maintained global airport database: names, IATA/ICAO codes, coordinates, elevation, runways and official links.
- Natural Earth 1:110m land (Natural Earth (via the world-atlas package); Public Domain) — Coastline geometry used to draw AMZBooking’s dotted world map.
- Natural Earth 1:50m admin-0 countries (Natural Earth; Public Domain) — Country outlines used to draw the maps on country airport pages.
- Natural Earth 1:10m admin-0 countries (Natural Earth; Public Domain) — Country boundaries used to compute land neighbours, country areas and which countries a natural area lies in.
- Natural Earth 1:10m populated places (Natural Earth; Public Domain) — Locations of about 7,300 populated places (a representative point, roughly the city centre), with time zones and Wikidata ids.
- Natural Earth 1:10m admin-1 states and provinces (Natural Earth; Public Domain) — First-order administrative boundaries (states, provinces, departments, counties) with ISO 3166-2 codes. Used to decide which airports lie inside a region and how far others are from its border.
- Natural Earth 1:10m admin-2 counties (United States) (Natural Earth; Public Domain) — US county and county-equivalent boundaries with FIPS codes.
- Natural Earth 1:10m time zones (Natural Earth; Public Domain) — Standard-offset time-zone bands, used only together with the tz database to place an airport in one of its country’s zones; bands that disagree with tzdb are ignored.
- Natural Earth 1:10m physical regions and elevation points (Natural Earth; Public Domain) — Named islands, island groups, mountain ranges, deserts, peninsulas and other physical regions, lakes and reservoirs, plus named peaks with elevations.
- Natural Earth 1:10m parks and protected lands (US National Park Service) (Natural Earth, from US National Park Service boundaries; Public Domain) — Boundaries of major US National Park Service units with their NPS unit codes and types.
- timezone-boundary-builder (Evan Siroky and contributors, from OpenStreetMap data; ODbL 1.0 (© OpenStreetMap contributors)) — Polygons of every IANA time zone, released in step with tzdb. Used to place a city in its zone where Natural Earth has no zone or lists one with a different clock.
- Unicode Common Locale Data Repository (CLDR) (Unicode Consortium; Unicode License v3) — Locale reference data: legal-tender currencies, official languages, measurement and unit conventions, ISO 3166-2 subdivision hierarchy and UN M49 region membership.
- AMZBooking editorial curation — groupings such as which airports serve a city and destination themes. These are flagged for human review before a page that relies on them can be indexed.
- AMZBooking destination research — one research file per travel-guide destination (sights, areas, foods, climate averages, cost estimates, day trips), compiled with AI assistance; each guide lists official sources for the destination.
- Wikimedia Commons — the photos in our travel guides, each credited with its author and licence.
Our airport data currently covers 3,244 large and medium airports with scheduled passenger service and an IATA code, retrieved on 2026-10-18. Full details are in Data and methodology.
Every fact keeps its source
Each changeable fact we store — an airport’s codes, its location, a distance — carries its provenance: the source, the publisher, the date it was retrieved or reviewed, the type of fact, and a confidence and status. Guide pages list their sources, and calculated findings say how they were worked out. A fact marked disputed or retracted, or held with low confidence, can’t appear on a page we ask search engines to index.
Articles cite their sources too. A source we have located but not yet read in full is shown as such, and a page that relies on it stays out of search engines until an editor has checked it.
What we calculate
- Distances and bearings are great-circle values between airport reference points (method). They are not the distance flown or a flight time.
- Nearby airports are airports with scheduled service within a stated radius (method).
- Counts, rankings and findings state what was counted and over which set. A ranking orders one measurable attribute, such as elevation or runway length — never quality, service or popularity (method).
What we don’t publish
We don’t invent prices, schedules, baggage fees, entry requirements, ratings or endorsements. When we don’t have reliable data for part of a page, we leave it out and say so, rather than fill the gap.
Freshness
Every kind of fact has a refresh window, from a couple of days for fast-changing facts to years for ones that rarely change. A fact that passes its window without being re-checked is removed from indexable pages rather than presented as current (details). Update dates on our pages move only when content changes substantively.
Review before indexing
A page is published for visitors first and stays marked noindex until it qualifies. An airport, route, destination, time-difference or daylight guide, an article or a research story qualifies when it:
- scores at least 80 out of 100 on our quality checks (or a stricter bar for its type) — data completeness, sourced and unique facts, original calculations, freshness, distinctiveness from similar pages, depth, links and metadata;
- has no blocking issue, such as a missing source or a near-duplicate of another page;
- is approved by a person. For pages built from data, such as airport and destination guides, a person approves each type of page once, after its quality checks and a set of sample pages; each page of that type must then pass the automated checks above on its own. Hand-written articles and research stories are reviewed one by one.
Airport-transfer guides qualify when they score at least 85 out of 100 on their own model, with every fare and journey time taken from an official page. Travel guides are checked automatically rather than by a person: each needs enough destination-specific text, a title and heading no other guide uses, links to and from related guides, valid structured data and partner links, and must not be a near-duplicate of another guide about the same destination (details).
Only pages that qualify go into our sitemaps. Read more in our editorial policy and how pages qualify for search.
Commissions don’t change guides
Partners may pay us a commission when you book through our links. That never decides what a guide says, which airports it lists or how it ranks them (how we operate).
Spotted an error?
Use the “Report an issue” link at the end of any article, research story or Help page, or see reporting an error. We review reports and fix confirmed errors; articles and Help pages also record each correction in their update history (corrections policy).