Skip to content

sfomuseum-data/sfomuseum-data-flights-2019-12

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

79 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

sfomuseum-data-flight-2019-12

Flight data for arrivals and departures at SFO (December, 2019)

Background

Details to follow. Until then please consult https://millsfield.sfomuseum.org/blog/tags/flightdata for details and specifically:

Notes

Some (but still not all) flights have "alternate" geometries representing the planned route for the flight as well as the actual flight path in and out of SFO. Respectively they identified using the following naming convention:

  • {WHOSONFIRST_ID}-alt-swim-route.geojson
  • {WHOSONFIRST_ID}-alt-swim-path.geojson

There are a few things to keep in mind when using this data:

  • These alternate geometries are currently not availble for "code share" flights.
  • Routes and paths are clipped at the exterior boundaries of airports as well as the United States. We hope to have more detailed data soon, but today this is what we have to work with.
  • Elevation, speeds and point-in-time data for flight paths (not routes) are stored in the swim:altitudes and swim:speeds and swim:timestamps properties respectively. Each is an array and each index maps to a corresponding entry in the feature's coordinates array.
  • Elevation data are currently encoded as raw SWIM simpleAltitude Type values. The documentation describes these values as:

"Simple type used to place constraints on a flight's altitude. The altitude can represent a number of values as reported by NAS. Please refer to NAS MD-314 section 3.1 for details. The message from HADDS to TFMS is constrained to include an assigned altitude, nnn, or a beacon reported altitude, nnn + 'C', or an interim altitude, nnn + 'T'. Allowed format: [0-9]{0,3}[C,T]{0,1}. Where C = Beacon reported altitude is within Altitude Conformance Limits (ALCT) feet and T = Interim altitude is currently being displayed in the assigned altitude field."

License

This data is published under the Community Data License Agreement – Permissive – Version 1.0 license, but we'd love a shout-out and generally to hear what you're doing if you use the data.

See also

About

Flight data for arrivals and departures at SFO (December, 2019)

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published