Open westontrillium opened 2 years ago
I do think that the use cases for the information that can be found in this dataset do not justify the privacy implications should such data be made publicly available. However, part of the benefit that I would hope to get out of GTFS-ride should it be adopted by my agency is the ability to use and develop tools to work with non-public datasets that can, because of the common format, be shared with other agencies. I am more hesitant to say rider_trip is of no use whatsoever for intra-agency purposes. If it were eliminated, I would hope to see some kind of standardized point-to-point trip propensity dataset.
A use case example: we are planning to split up a longer, regional route within our service area into two routes so that we can increase the frequency of the more heavily used northern portion of the route and split up our blocking to reduce operator travel time. The planned split point is at a commuter rail station about halfway along the route.
I mock up the new service and run it through a publicly available comparison tool. The comparison tool uses the EFC and Point-in-Time survey data to identify that a substantial number of riders I'd assumed were transferring from commuter rail were actually traveling through the planned terminus, getting off at a transfer point three stops later, transferring to a cross-town route, and all arriving at a single employment center.
Instead of simply deviating the crosstown route to the commuter rail station, I propose extending the southern route to terminate at the employment center, and reduce the frequency of the crosstown route.
The way I see it there are two ways the information in this scenario would be usable:
I'd love to hear your thoughts.
Problem statements
rider_type
) be generated?Solutions considered
rider_type
,transaction_type
,fare_media
, etc.)Looking forward to discussing further!