data

How the Folder Directory Structure Works

The developer / user must retain a relative directory structure as shown in the figure below:

Within the folders are sub-folders created basd on the GTFS static update and the date of the near real-time GTFS.

1. 0_external: Where the near real-time and static GTFS files are stored.


2. 1_raw: Empty folder - nothing is stored in this.


3. 2_staging: Where individual routes, stops, and trip_ids are stored per GTFS static update as csv and shapefiles.


4. 3_interim: Per GTFS static update per near real-time GTFS date are a csv file per route that contains snapped locations of the vehicles (*_located.csv) and cleaner version of it (*_cleaned.csv).


5. 4_processed: Per GTFS static update per near real-time GTFS date are a csv file per route that supplements the spatio-temporal locations of the vehicles.


6. 5_conformed: Per GTFS static update per near real-time GTFS date are a csv file per route containing interpolated results (original & cleaned version).


7. 6_analyses: Per GTFS static update per near real-time GTFS date are a geojson file containing general aggregated results. The aggregated results are structured per route per trip_id per stop.


8. 7_requests: Per GTFS static update per near real-time GTFS date are two geojson files containing daily and hourly aggregated results.