Hi Mark,
I wanted to share some uses cases we have for our Mobility project:
- We would like to know the expected wait time at departure for all routes that gtfs_traveltimes found (which would be a function of the frequency of the service). Because we don't know which service gtfs_traveltimes uses, we compute for now a crude approximation, based on the average headway between all services at a given stop.
- We would like to know the breakdown of travel times (and distances) per route type (bus, subway...). For now we can only approximate this, based on the most probable service type departing from the first stop and the one arriving at the last stop.
Did you already consider expanding the output of gtfs_traveltimes (adding columns for first / last trip ids, and the breakdown of travel times per route type) ?
Using gtfs_route on each route gound by gtfs_traveltimes is too slow even for smallish feeds (~ 4000 stops).
Hi Mark,
I wanted to share some uses cases we have for our Mobility project:
Did you already consider expanding the output of gtfs_traveltimes (adding columns for first / last trip ids, and the breakdown of travel times per route type) ?
Using gtfs_route on each route gound by gtfs_traveltimes is too slow even for smallish feeds (~ 4000 stops).