-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GTFS-Occupancies (part 2) #290
Conversation
I think we still have to discuss the start_time / end_time for frequency based trips. |
The definition we have for
Correct me if I'm wrong, but should this be rephrased to refer to the first departure time of the stop specified by I propose the following reword to
Following this, here is a proposal for defining
Does this work? |
Thanks @scmcca - yes, I believe that works. One option here to make sure is to wait to adopt the start_time and end_time fields until we have producers/consuemers for those specific fields (i.e., frequencies data). |
@barbeau I added them for now but agree that they aren't necessary for initial adoption |
I do have a bigger question. Does the standard currently state anything regarding a requirement that the files must be bundled as a single zip archive? In our case we would like to add the latest predictions we receive but forcing hundreds of megabytes of unchanged data data just does not make sense. |
@skinkie we were also thinking about this @mbta. We might include it in our GTFS (which updates a few times a week) as well as a standalone file (updated as frequently as necessary). |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This pull request has been closed due to inactivity. Pull requests can always be reopened after they have been closed. See the Specification Amendment Process. |
Due to GitHub workflow and CLA issues, this pull request is a continuation of discussions at #240.
GTFS-Occupancies is an extension proposal to describe usual or expected vehicle occupancy levels in GTFS Schedule.
As occupancies can currently be described in GTFS Realtime using
occupancy_status
andoccupancy_percentage
, GTFS-Occupancies aims to complement the availability of crowdedness information by providing static predictions for future trips based on historical trends, which can help riders plan trips based on their crowdedness preferences and comfortability.To be resolved:
OccupancyStatus
andoccupancy_percentage
are experimental. Ideally, we want consistency between static and realtime occupancy indicators. Whichever becomes official in GTFS Realtime will be the one used here.TfNSW has published a dataset: #240 (comment).