JFK Central Terminal Area · Digital Twin

The terminal-area roads (OpenDRIVE + SUMO) built from OpenStreetMap and corrected by where our cars actually drive, with every curb stop our cars made at the terminals. Simulated cars come in, stop at a terminal curb for as long as real cars do, and leave. Top left: a real dashcam drive with the car shown on the map. Drag to pan, scroll or pinch to zoom.
Real dashcam ·
Imagery: NYS ITS Geospatial Services · roads © OpenStreetMap contributors
Departures roadway (upper) Arrivals roadway (lower) Other roads Map corrections (roads our cars use that the map lacked) Driven but on no map The real car in the dashcam

What's in the map

Real curb stops by terminal (seconds)

CurbSharep10 / median / p90

Stops of 15 s or more on a terminal's departures or arrivals roadway by our cars. Upper and lower decks share the same footprint, so the level comes from which named roadway the stop snaps to.

Real vs simulated time in the terminal area (minutes)

p10 / median / p90

When do the curbs fill up?

Map corrections from real driving

Limits

  • All behaviour comes from our cars (mostly for-hire), not all traffic at JFK. Shares and dwell times describe our fleet.
  • Total traffic volume isn't observable from our fleet. The volume sweep shows how the curbs behave as traffic grows; pinning it needs the Port Authority's counts.
  • GPS can't tell the departures deck from the arrivals deck below it. Stops are assigned to the named roadway they snap to, which can be wrong under the overpass.
  • The road network is OpenStreetMap, corrected only where our cars drove at least 3 times. Rarely driven changes are missed.
  • JFK is mid-reconstruction (New Terminal One, T6). Imagery and the map lag the real layout; our cars show the current one.
  • Faces and licence plates in the dashcam clip are blurred.