You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our GTFS schedule reports use our underlying gtfs_schedule_type2 data. Since we've got most of this information up in views, it'd be useful to migrate to using the views directly.
Let's put up a quick dashboard in metabase that reproduces this part of the report.
Notes:
create two filters
views.gtfs_schedule_dim_feeds.calitp_feed_name
month (e.g. gets data at the beginning of the month; or for the full month where needed)
summary info
feed_info.feed_publish_date (or feed_start_date?)
feed_end_date
days expired (skip for now)
number of feed routes (fact_daily_feeds)
number of feed stops (fact_daily_feeds; may need to add)
Service hours per day for month (views.gtfs_schedule_fact_daily_service)
Part 1 (implement in Metabase) seems to actually mostly be already accomplished in the GTFS Guidelines dashboards that Evan has already made.
Part 2 (use views instead of schedule_type2 is also partially implemented already but there are a few aspects that still need to be refactored (notably validation notices).
Currently, our GTFS schedule reports use our underlying gtfs_schedule_type2 data. Since we've got most of this information up in views, it'd be useful to migrate to using the views directly.
Let's put up a quick dashboard in metabase that reproduces this part of the report.
Notes:
The text was updated successfully, but these errors were encountered: