Closed
Conversation
Adds the files of MobilityData's GTFS-MeanOccupancies proposal to the GTFS Static reference.
+ add precision in mean_occupancy_status
PR update to Option C as appears in the GTFS-Occupancies proposal working document, replacing Option A.
Minor editorial corrections to syntax of some text.
Removal of fields that were apart of the Option A proposal, but are no longer relevant for Option C.
(1) Removed weekly pattern structure (Option C) in favor of individual date structure (Option B). (2) Edit of `occupancy_percentage` to bring it in technical conformity with the GTFS Realtime description.
- Occupancy descriptions at individual date or weekly pattern level that accomodates either approach efficiently. - Removal of `occupancy_percentage` until further needs are expressed. - Removal of `data_source`. - Added `occupancies.exception` to be able to describe occupancy exceptions to weekly pattern. - Added "Conditionally Forbidden" Term Definition. - Updated wording to "Conditionally Required" for semantic clarity.
Added "or empty" to date descriptions
- require `end_date` - patch `stop_sequence` to optional - remove `exception`
This reverts commit b23784c.
Co-authored-by: Jeff Kessler <31969870+jeffkessler-keolis@users.noreply.github.com>
sccmcca
added
the
GTFS Schedule
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 usingoccupancy_statusandoccupancy_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:- Officializing an occupancy indicator in GTFS Realtime: Currently, bothOccupancyStatusandoccupancy_percentageare experimental. Ideally, we want consistency between static and realtime occupancy indicators. Whichever becomes official in GTFS Realtime will be the one used here.- Elaborating GTFS-Occupancies to support frequency-based service. Some thinking on this here.TfNSW has published a dataset: #240 (comment).