LIVESFO · data and licences
Live SFO builds its airports, coastline, buildings and bridges from open data, chiefly OpenStreetMap and the FAA's. Map data © OpenStreetMap contributors.
The files marked ODbL contain data from OpenStreetMap and are made available under the Open Database License 1.0: you may copy, adapt and share them under that licence, crediting OpenStreetMap's contributors. Each is linked below, in the form the site serves it, with how it was made. Data from US government agencies (FAA, USGS, USDA, NASA, NWS) is in the public domain.
Airports
San Francisco International (SFO)
ODbL Runways, taxiways, aprons, stands, gates, jet bridges, holding positions, buildings, roads and the shoreline round the airport.
- Sources: OpenStreetMap through the Overpass API (37.585–37.648° N, 122.415–122.335° W, and the aerodrome's outline), as of 7 Nov 2026; the FAA's airport-mapping layers (cycle of 29 Oct 2026) and Digital Obstacle File, public domain.
- How: converted into metres on a plane at the airport's reference point; the FAA's polygons for paved surfaces, OpenStreetMap's lines for taxiway centrelines, stands and bridges; building heights from OpenStreetMap, else from the FAA's obstacle file. Runways are painted and lit to the FAA's standards.
- Files: /vendor/airport/91_sfo_data.js · /api/v1/airport/ksfo
Oakland (OAK) and San José (SJC)
ODbL Each airport in four stages: its core, the airfield (taxiways, aprons, stands, holds, gates, jet bridges, airport buildings), the neighbourhood within 3 km, and the towns beyond.
- Sources: OpenStreetMap through the Overpass API, as of 14 Nov 2026; the FAA's airport data (14 Nov 2026), public domain; at Oakland, taxiway pavement traced on USDA NAIP 2022 aerial imagery, public domain.
- How: taxiways built to the FAA's design standard (Advisory Circular 150/5300-13B) on OpenStreetMap's
centrelines, one width per taxiway by its class, with fillets at junctions; aprons, stands, holds, gates and
buildings as OpenStreetMap maps them; everything in metres on a plane at each airport's reference point. Each
file's
meta.provenancenames the layers that come from OpenStreetMap. - Files:
/vendor/fields/oak/koak_core.js ·
koak_airfield.js ·
koak_near.js ·
koak_towns.js ·
/api/v1/airport/koak
/vendor/fields/sjc/ksjc_core.js · ksjc_airfield.js · ksjc_near.js · ksjc_towns.js · /api/v1/airport/ksjc
Seattle–Tacoma (SEA)
ODbL Built for Live SFO's first airport beyond the Bay; not shown on the site yet. The same four stages as Oakland's and San José's.
- Sources: OpenStreetMap through the Overpass API, as of 15 Nov 2026; the FAA's airport-mapping layers (15 Nov 2026), public domain.
- How: as Oakland's and San José's; paved surfaces from the FAA's airport-mapping polygons.
- Files: /vendor/fields/sea/ksea_core.js · ksea_airfield.js · ksea_near.js · ksea_towns.js · /shared/airports/ksea.json (the model the server reasons with: runways, stands, gates, taxiway lines, holds, aprons; five parking positions OpenStreetMap lacks, found in our own traffic and checked on USDA NAIP 2017 imagery, public domain, each marked with its source)
New York: JFK, LaGuardia (LGA) and Newark (EWR)
ODbL Built for New York; not shown on the site yet. The same four stages for each airport as Oakland's and San José's.
- Sources: OpenStreetMap through the Overpass API, as of 15 Nov 2026; the FAA's airport data (effective 29 Oct 2026), airport-mapping layers and Digital Obstacle File (15 Nov 2026), public domain.
- How: as Oakland's and San José's; paved surfaces from the FAA's airport-mapping polygons.
- Files:
/vendor/fields/jfk/kjfk_core.js ·
kjfk_airfield.js ·
kjfk_near.js ·
kjfk_towns.js
/vendor/fields/lga/klga_core.js · klga_airfield.js · klga_near.js · klga_towns.js
/vendor/fields/ewr/kewr_core.js · kewr_airfield.js · kewr_near.js · kewr_towns.js
/shared/airports/kjfk.json · klga.json · kewr.json (the models the server reasons with: runways, stands, gates, taxiway lines, holds, aprons)
The Bay Area round them
Coastline
ODbL OpenStreetMap's coastline, closed into land polygons and simplified.
/shared/airports/bayarea-coast.json · /shared/airports/bayarea-coast-wide.json
San Francisco's and Oakland's tall buildings
ODbL OpenStreetMap's building outlines and parts with their heights (San Francisco's largely from the city's 2016 LiDAR import), each standing on USGS 3DEP ground.
Bridges
ODbL The Bay's bridges on their OpenStreetMap centrelines, built from their published dimensions.
Towns beyond the airports
ODbL Buildings placed on developed land from the USGS's National Land Cover Database (public domain), sized and spaced like the OpenStreetMap buildings round SFO, and round Oakland and San José like theirs.
/data/land/filler-desktop.bin · /data/land/filler-phone.bin · /data/land/filler-oak-desktop.bin · /data/land/filler-oak-phone.bin · /data/land/filler-sjc-desktop.bin · /data/land/filler-sjc-phone.bin
Seattle's coastline and tall buildings
ODbL For the first region beyond the Bay; not shown on the site yet. Puget Sound's coastline from OpenStreetMap, closed into land and simplified; downtown's buildings 25 m and taller, from OpenStreetMap's outlines and heights, each standing on USGS 3DEP ground.
/data/land/sea/coast.json · /data/land/sea/skyline.json · /data/land/sea/skyline-phone.json
New York's coastline, rivers and tall buildings
ODbL For the next region; not shown on the site yet. The harbour's, Long Island's and the Jersey Shore's coastline from OpenStreetMap, closed into land with the tidal Hudson, Harlem, Hackensack, Passaic and Raritan cut out of it from OpenStreetMap's water areas, and simplified; the tallest buildings from OpenStreetMap's outlines and parts with their heights (New York City's from the city's footprints, imported in 2013–14), each standing on USGS 3DEP ground, and where OpenStreetMap has none yet, the city's own footprints and roof heights (NYC Open Data, Building Footprints, NYC Office of Technology and Innovation; no restrictions on use). The buildings from 25 to 75 m, streamed round the camera on desktops, in 1 km tiles (an index, then one file a tile): the same sources, the city's buildings with their setbacks and rooftop structures from the city's 3-D model (NYC Open Data, 3-D Building Model, NYC Office of Technology and Innovation, 2014; no restrictions on use). Each building's walls (glass, masonry or stone) are chosen from OpenStreetMap's materials and the footprints' construction years. Four landmark towers are our own models, built from their published dimensions in place of their OpenStreetMap parts: the Empire State Building, the Chrysler Building, One World Trade Center and 432 Park Avenue (heights and plans from the Council on Tall Buildings and Urban Habitat, the owners and architects, the Chrysler Building's 1930 plans, and the FAA's Digital Obstacle File; their night lighting as the owners describe it).
/data/land/nyc/coast.json · /data/land/nyc/skyline.json · /data/land/nyc/skyline-phone.json · /data/land/nyc/mid/index.json · /data/land/nyc/landmarks.json
New York's and Seattle's ground photos and streets
Public domain ODbL The ground round the camera from aerial photos: The National Map's orthoimagery (USDA, USGS The National Map: Orthoimagery; public domain), as Web Mercator tiles at about 14 m and 3.5 m a pixel. With each photo tile a mask: the streets from OpenStreetMap's roads, drawn at their widths (their width or lanes as tagged, else their class's), and the ground under and beside each building 25 m and taller (the buildings above), where the photo's leaning towers are covered over in the sidewalks' concrete. The street lights' colours on them at night by place: New York City's LED conversion (3,000 K; 4,000 K in Brooklyn and Queens, from OpenStreetMap's borough boundaries) and New Jersey's sodium.
/data/land/nyc/ortho/index.json (and its tiles, /data/land/nyc/ortho/{zoom}/{x}_{y}.jpg and .png) · /data/land/sea/ortho/index.json (likewise)
Hills, land cover and night lights
Public domain Elevation from USGS 3DEP, land cover from USGS NLCD, night lights from NASA Black Marble, cut to the OpenStreetMap coastline above.
Live data
- Aircraft positions: ADS-B from the volunteer networks adsb.fi and adsb.lol (ODbL); in Seattle, from FlyItalyADSB, flyitalyadsb.com (CC BY-SA 4.0).
- Flights: the airports' own boards (flysfo.com, flysanjose.com); routes from Virtual Radar Server's standing data (CC0).
- New York and Seattle: surface movements at JFK, LaGuardia, Newark and Seattle–Tacoma, and flights' routes and departure gates, include data from the FAA's System Wide Information Management (SWIM), for scheduled airlines' flights only. It isn't for operational use. When the SWIM feed is interrupted, the airport's flight list says so.
- Weather: METARs from the NWS Aviation Weather Center, public domain.
Some aircraft are hidden or shown without their details: see privacy. The detailed aircraft models and their licence: credits.
Corrections
OpenStreetMap is mapped by volunteers. If something at an airport is wrong, it can be fixed at openstreetmap.org, and the fix reaches Live SFO when that airport is next rebuilt. Back to Live SFO.