Skip to content

Epic - GTFS Digest (exploratory portfolio) #989

@tiffanychu90

Description

@tiffanychu90

After receiving a research request, use this template to plan and track your work. Be sure to also add the appropriate project-level label to this issue (eg gtfs-rt, DLA).

Epic Information - GTFS Digest (exploratory portfolio)

Summary

  • Track the portfolio work displaying everything we can display with GTFS schedule, speeds, RT vs schedule across all our 4 major workstreams within GTFS (schedule, speeds, RT vs schedule, predictions)
  • Outline all the differences in columns so we can land on a standardized way to approach this
    • Make sure every dataset has similar columns so we can merge in our time-series datasets
    • Keep track of the tables we have created / aggregated and use this to inform any new tables we are creating

Speed Tables

GCS

dataset grain geometry time_category single_multi operator_ids timeseries_postprocessing
shape-stop_segments (shape_array_key) shape_id stop_sequence segment_geom (select one trip per shape) peak, off peak, all-day single
multi
(gtfs_dataset_key) org_source_record_id, org_name cannot be used for multiple months, as shape_id will appear distinct even in a 6 month period
route_direction- stop_segments route_id, direction_id, stop_pair segment_geom peak, off peak, all-day single (gtfs_dataset_key) org_source_record_id, org_name put through script to standardize / parse route_id over time so we can identify the same route over time (route_id2)
route_direction- stop_segments route_id, direction_id, stop_pair segment_geom peak, offpeak, all-day weekday, weekend, month, year multi (gtfs_dataset_key) org_source_record_id, org_name put through script to standardize / parse route_id over time so we can identify the same route over time (route_id2)
trip avg speed trip_instance_key tabular has time_of_day column, but is disaggregated single gtfs_dataset_key
route_direction avg speed route_id, direction_id common_shape geom peak, offpeak, all-day single
multi
(gtfs_dataset_key) org_source_record_id, org_name put through script to standardize / parse route_id over time so we can identify the same route over time (route_id2)

RT vs Schedule Tables

GCS

dataset grain geometry time_category single_multi operator_ids timeseries_postprocessing
trip trip_instance_key tabular has time_of_day column, but is disaggregated single gtfs_dataset_key not used beyond single day
route-direction route_id, direction_id tabular peak, offpeak, all-day single (gtfs_dataset_key) org_source_id, org_name put through script to standardize / parse route_id over time so we can identify the same route over time (route_id2)

Schedule Tables

GCS

dataset grain geometry time_category single_multi operator_ids timeseries_postprocessing
trip trip_instance_key tabular has time_of_day column, but is disaggregated single (gtfs_dataset_key) org_source_id, org_name not used beyond single day
route-direction route_id, direction_id tabular peak, offpeak, all-day single (gtfs_dataset_key) org_source_id, org_name put through script to standardize / parse route_id over time so we can identify the same route over time (route_id2)
monthly route-direction service route_id, direction_id tabular time_of_day, day_type multiple (month aggregation) source_record_id put through script to standardize / parse route_id over time so we can identify the same route over time (route_id2)

Issues

Metadata

Metadata

Labels

SB125Issues related to SB125 discussionepicRepresenting research requests - large segments of work and their dependenciesgtfs-rtWork related to GTFS-Realtimeportfolio workWork related to the analytics portfolio

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions