Research Request - create schedule stops table with other GTFS stop metrics

[tiffanychu90]

Complete the below when receiving a research request, and continue to add to this issue as you receive additional details and produce deliverables. Be sure to also add the appropriate project-level label to this issue (eg gtfs-rt, DLA).

Research Question

Single sentence description: Add columns for (scheduled) stops table that provides certain metrics like hours in service, number of arrivals (stop_times), number of routes served, number of route types served, etc.

• Epic - GTFS analytics pipeline - stop + operator grains  #1232

Detailed description: Use this table for our Geoportal ca_transit_stops because there are some additional columns of interest here.

• Note: previously, ca_transit_stops does publish stop with route_ids, and creates multiple rows for the same stop if there are multiple routes that share it. Now, we'll publish unique stops and aggregate up the n_routes, and n_route_types to better capture that.

• Refactor ca_transit_stops with columns + patch in previous dates Feature Request: Published data products should patch in earlier data if it's missing #1225
• Refactor ca_transit_routes to patch in previous dates
• Refactor metadata publishing scripts, see if we can consolidate some
• Update data_dictionary.yml and metadata.yml since we're adding new columns

How will this research be used?

Existing Geoportal tables

Deliverables

Update these scripts: open_data/create_stops_data.py and open_data/create_routes_data.py