Warehouse: Where to Begin

Warehouse: Where to Begin#

There is a large selection of data available in the warehouse. Consider this a short guide to the most commonly used tables in our work.

Trips#

On a given day:

  • fct_scheduled_trips

    • Use gtfs_utils_v2.get_trips().

    • Answer how many trips a provider is scheduled to run and how many trips a particular route may make?

  • fct_observed_trips

    • Realtime observations of trips to get a full picture of what occurred.

    • Find a trip’s start time, where it went, and which route it is associated with.

Shapes#

  • fct_daily_scheduled_shapes

    • Use gtfs_utils_v2.get_shapes().

    • Contains point geometry, so you can see the length and location of a route a provider can run on a given date.

    • Each shape has its own shape_id and shape_array_key.

    • An express version and the regular version of a route are considered two different shapes.

Daily#

For a given day:

  • fct_daily_scheduled_stops

    • Use gtfs_utils_v2.get_stops().

    • Contains point geometry.

    • How many stops did a provider make? Where did they stop?

    • How many stops did a particular transit type (streetcar, rail, ferry…)?

    • Detailed information such as how passengers embark/disembark (ex: on a stop/at a station) onto a vehicle.

  • fct_daily_schedule_feeds

    • Use gtfs_utils_v2.schedule_daily_feed_to_organization() to find feed names, regional feed type, and gtfs dataset key.

    • Please note,the name column returned from the function above refers to a name of the feed, not to a provider.

    • Use gtfs_utils_v2.schedule_daily_feed_to_organization() to find regional feed type, gtfs dataset key, and feed type for an organization.

Other#