Skip to content

Orion Data Flow

Jump to bottom
Eddy Ionescu edited this page Jul 15, 2018 · 5 revisions

Orion format for storing vehicle locations. Note that each agency has its own bucket. JSON formatted as such:

[{
  vtime
  vid
  lat
  lon
  rid
  did
  ...other agency-specific fields (currently none)
}]

  1. orion-realtime-transit-to-s3 - gets realtime transit data (via GTFS-RT and Nextbus via Restbus) and writes it to S3. Polls every 15 seconds, and writes entire response to a new file in the S3 bucket for its agency. Also writes it in orion format.

  2. orion-avl-to-s3 - script for reading in AVL (from SFMTA) and writing it to S3 for Muni based on Nextbus format.

  3. orion-trip-generator - reads orion format files and generates trip files (like Muni #1 going from Ferry Building to Church/30th). Also inserts vehicle locations corresponding to generated trips to locations-db.

  4. tryn-graph [TODO]

a. generate time-distance graph for trips along a route (slopes are speeds and horizontal lines are dwell or traffic light waiting times) - visualizes speed & reliability.

b. generate bar-graph where travel-times for a segment during a time-interval are put in buckets and shown on a bar-graph (by mode) as to visualize reliability, including the relative standard deviation.

  1. tryn-metrics - analyze trips and store it such that speed & reliability (ie. all data in above graphs) can be easily computed for any route segment and time interval.

  2. tryn-visualize - slope of 4a can be visualized along a road in the web-app, and can be stored differently too. Waiting times at stops could also be somehow visualized.

Clone this wiki locally