OpenStreetMap for spotters: find taxiways, aprons, paths and parking

On an aerial photo, every airport looks the same: gray surfaces, white lines, a few buildings. Whether the dirt track along the fence is public, what the taxiway in front of your spot is called and where the nearest legal parking lot is – the photo won’t tell you. OpenStreetMap for spotters closes exactly this gap. Behind the free world map is a database in which volunteers have recorded runways, taxiways, aprons, parking stands, dirt tracks and parking lots, complete with designations and access rules, at many airports. This guide shows you which details matter to you, how to query them precisely and where you’d better not trust the map blindly.

OpenStreetMap at the airport: the short answer

OpenStreetMap (OSM) is a freely usable geodatabase maintained by a worldwide community. Every object – a path, a parking lot, a taxiway – carries so-called tags, key-value pairs such as aeroway=taxiway or access=private. For spotters that means: you can not only look at a map but also ask specifically for taxiways, parking stands, viewpoints and parking lots and have the answer projected onto your map section.

The data is released under the Open Database License (ODbL). Many apps draw on it, including offline navigation apps such as OsmAnd and Organic Maps. If you see a dirt track along the airport fence there, it most likely comes from OSM.

The most important aeroway tags for spotters

Everything on the airport grounds that has to do with aviation runs under the key aeroway in OSM. The OSM wiki documents a good two dozen values. These are the most relevant for spotters:

Tag	What it is	What you can read from it
aeroway=aerodrome	the entire airport grounds	outline, often with iata and icao as identifiers
aeroway=runway	runway, as a line along the centerline	runway designation in ref, often also length, width, surface
aeroway=taxiway	taxiway between runway and apron	taxiway designation in ref, sometimes width
aeroway=taxilane	taxilane on the apron leading to the stands	how aircraft maneuver between the parking stands
aeroway=apron	apron, the parking and handling area	where aircraft park, refuel and are loaded
aeroway=parking_position	individual parking stand	stand number in ref, for a line also the aircraft’s orientation
aeroway=holding_position	holding point before a runway crossing	where aircraft wait before takeoff – often a good photo subject
aeroway=terminal, gate, jet_bridge	terminal, gate, passenger boarding bridge	where the passenger aircraft stand
aeroway=hangar	aircraft hangar	maintenance and overhaul areas, often with movements outside scheduled service
aeroway=windsock, navigationaid	windsock, approach aids such as PAPI	reference points and hints about the landing direction

A few details matter in practice. According to the wiki, runways are drawn as a line along the centerline; the surface can additionally be recorded with area:aeroway=runway. The ref field holds the designation with the smaller number first, for example 08L/26R. Why the two numbers always differ by 18 and what L, C and R mean is explained in the article runway designations at airports.

For parking stands, a close look pays off: if a parking_position is recorded as a line, it leads from the taxiway to the point where the nose wheel stops. The direction of the line therefore tells you how the aircraft ends up standing – useful if you want to know whether you’ll see more nose or tail from your spot. You’ll find more on gates and remote stands in the guide apron positions and gates.

Reading taxiways and holding points

For rolling shots, the taxiway in front of your spot is almost as important as the runway. This is where OSM shows its strength: at well-mapped airports, every taxiway segment carries its designation in the ref field – letters, often combined with a number. If you hear over radio recordings or see on a live map that an aircraft is being routed along a particular taxiway, you can quickly find it again in OSM.

How the designations are systematically built and what the signs at the edge mean is covered in the article understanding taxiways, holding points and signs. The lighting you see at dusk is covered in the guide runway and taxiway lighting.

Two additional details on the taxiway are also interesting:

• width gives, according to the wiki, the actual width of the paved taxiway.
• clearance describes, if recorded, the maximum wingspan permitted in this section. It shows you where widebody aircraft such as the Airbus A380 can taxi at all.

Paths, parking lots and viewpoints around the fence

The aviation tags tell you where the aircraft are. For you as a spotter, how you get there is just as important. The completely ordinary OSM categories handle that:

• Paths: highway=track stands for farm and field tracks, highway=footway, cycleway and path for footpaths and bike paths. Many spotting locations lie right on such paths along the fence.
• Parking lots: amenity=parking marks parking areas, often with fee (paid), capacity or access.
• Viewpoints: tourism=viewpoint marks, according to the wiki, places with a good view. Some visitors’ hills or platforms are recorded this way, sometimes with direction for the viewing direction.
• Stops: highway=bus_stop and train stations help you reach spots without a car. More in the guide getting to the spot by public transit or car.

The most important addition is the access tag. According to the OSM wiki, it primarily describes legal accessibility:

Value	Meaning	What you make of it
yes	public right of way	generally usable
permissive	use tolerated, revocable at any time	usable, but watch for new signs
destination	local access only	usually off limits by car
agricultural, forestry	agricultural or forestry traffic only	don’t drive on it by car
customers	customers only	parking lot belongs to a business or hotel
private	authorized persons only	not for you
no	no entry	hands off

The wiki itself points out that some mappers record the actual rather than the legal state. The access tag is therefore a good first filter but doesn’t replace a look at the signs. What awaits you when parking on dirt tracks is summarized in the article parking at spotting locations, and the basic rules at the fence are in Is plane spotting allowed?.

Querying features on openstreetmap.org

The easiest way in costs nothing and needs no account. Open openstreetmap.org, zoom to the airport and use the “Query features” function (the question mark icon on the right). If you then click a point on the map, OSM lists all nearby objects with their tags. In seconds you see what a taxiway is called, whether a path carries access=private or whether a parking lot charges a fee.

The map image itself doesn’t show all tags. Which designations are labeled depends on the map style and zoom level. If a taxiway designation is missing, that doesn’t mean it isn’t in the database – the feature query shows it to you anyway.

Filtering precisely with Overpass Turbo

It gets really exciting with Overpass Turbo (overpass-turbo.eu). The web tool sends queries to the Overpass API and shows the hits on an interactive map. Instead of clicking through all objects, you fetch only what you need for your trip. A simple wizard also translates search terms into queries.

This query shows runways, taxiways, parking stands, holding points, viewpoints and parking lots for the current map section:

[out:json][timeout:25];
(
  way["aeroway"="runway"]({{bbox}});
  way["aeroway"="taxiway"]({{bbox}});
  nwr["aeroway"="parking_position"]({{bbox}});
  nwr["aeroway"="holding_position"]({{bbox}});
  nwr["tourism"="viewpoint"]({{bbox}});
  nwr["amenity"="parking"]({{bbox}});
);
out geom;

Zoom to the airport first, otherwise the section gets too large and the query slow. If you click a result, you see all its tags. With the export function you can save the hits as GeoJSON or GPX, for example. According to the wiki, for a GPX export you should add center to the output (such as out center;) so that every object becomes a point – handy if you want to transfer parking lots and viewpoints to your phone as waypoints. How to collect such points together with your sightings on a map of your own is shown in the guide visualizing sightings and spots on a map.

From map point to spot

OSM gives you raw material, not a finished spotting location. You only get the real value when you combine the data with other information:

• Runway direction and light: From the runway’s ref you know the axis. With it you can estimate at what time of day a path north or south of the runway gets front light – details in the guide planning sun position.
• Runway direction in use: Which half of the runway is currently used depends on the wind. A spot at the runway end only works with the matching runway direction in use, as the article understanding the runway direction in use shows.
• Aerial imagery: Trees, noise barriers or containers block the view without OSM knowing about them. How to scout in advance with satellite images and Street View is described in exploring airports with satellite maps.
• Official charts: For the exact position of taxiways, holding points and stands, the aerodrome chart in the aeronautical information publication is the reference. How to read it is explained in reading AIP aerodrome charts. For airspaces and smaller fields, openAIP helps as well.

At large airports such as Munich Airport or Frankfurt Airport, the well-known spots such as the Munich Airport visitors’ hill or the Zeppelinheim viewing platform have of course long been described. There, OSM helps you more with the question of which taxiway lies in front of you and where you can park. At smaller fields, on the other hand, the free map is often the best available source for paths around the fence.

Limits and pitfalls

OSM is only as good as the people who maintain it. That leads to a few typical problems:

• Uneven level of detail: At some airports every parking stand is recorded, at others only the outline with one runway. Missing objects don’t mean they don’t exist.
• Outdated states: New taxiways, relocated aprons or closed dirt tracks only show up once someone adds them. With offline maps, the state of your last download comes on top.
• Missing closures: Temporary barriers, for example during construction or major events, are rarely in the map.
• No substitute for signs: A path without an access tag isn’t automatically public. Prohibition signs on site always apply, even if the map shows something else.

And quite fundamentally: the fence is the boundary. No map justifies entering restricted grounds. What you risk for violations and how to behave properly at the fence is covered in proper behavior at the airport fence.

Map it yourself and mind the license

If a dirt track, a parking lot or a viewpoint is missing, you can add it yourself. Registration at openstreetmap.org is free, and the browser editor starts right from the map. Record only what you have seen yourself or can derive from permitted sources, and never go behind barriers while exploring. All the spotters who come after you benefit.

If you use OSM maps or data on your website, in a spot guide or in social media graphics, the ODbL applies: credit OpenStreetMap as the source and note that the data is released under this license. According to OSM, a link to openstreetmap.org/copyright satisfies this notice; in printed media you give the full address.

Conclusion

For spotters, OpenStreetMap is far more than a free street map. With the aeroway tags you read out runways, taxiways, holding points and parking stands complete with designations; with the path, parking and access tags you plan the way to the fence. Overpass Turbo turns that into a tailor-made spotter map in a few minutes that you can take along offline. A critical eye remains important: the data is only as current as its last edit, it is never binding for aviation, and on site the signs decide.