-
Notifications
You must be signed in to change notification settings - Fork 179
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
"Service date" vs. "service day" #43
Labels
GTFS Schedule
Issues and Pull Requests that focus on GTFS Schedule
Comments
Agreed, "service day" makes more sense to me in this context. |
I confirm, "service day" is widely used in the FOSS GTFS community, source code comments, etc. |
+1 |
antrim
added a commit
to Trillium-Solutions/transit
that referenced
this issue
Jan 27, 2017
see discussion in google#43
Closing. Spec changed in #45. |
emmambd
added
the
GTFS Schedule
Issues and Pull Requests that focus on GTFS Schedule
label
May 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Spec refers to "service date". Trips occur on a particular "service date". The service date begins on a particular calendar date, and may continue to the next calendar date. (i.e. if there is transit service past midnight, trips may begin at 25:00:00, etc.).
It appears that "service day" is a more accepted term in transit, and this feels more intuitive to me.
Examples of the use of the term "service day":
The text was updated successfully, but these errors were encountered: