Skip to content
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

Clarification: Copy guiding principle from GTFS Realtime to GTFS #313

Merged

Conversation

barbeau
Copy link
Collaborator

@barbeau barbeau commented Mar 31, 2022

A question recently came up - "is GTFS focused on passenger information?"

I tried to find the reference in the spec that says this, but couldn't.

Then I realized that, for some reason, this guiding principle is listed under GTFS Realtime but not GTFS.

GTFS Realtime CHANGES.md says that this principle applies to both GTFS and GTFS Realtime:

The spec is about passenger information.

Like GTFS before it, GTFS Realtime is primarily concerned with passenger information. That is, the spec should include information that can help power tools for riders, first and foremost. There is potentially a large amount of operations-oriented information that transit agencies might want to transmit internally between systems. GTFS Realtime is not intended for that purpose and there are potentially other operations-oriented data-standards that may be more appropriate.

This pull request copies the same guiding principle from GTFS Realtime to GTFS and updates the wording accordingly.

I think there is a legitimate debate over whether this should still be a guiding principle for GTFS, although I'd prefer to have that discussion in a separate issue.

IMHO it's pretty clear from the existing text that this guiding principle is intended for GTFS as well, and this changes focuses on making that clear to readers of the GTFS docs that don't review the GTFS Realtime documentation.

@barbeau barbeau added GTFS Schedule Issues and Pull Requests that focus on GTFS Schedule documentation labels Mar 31, 2022
@github-actions
Copy link

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.

@github-actions github-actions bot added the Status: Stale Issues and Pull Requests that have remained inactive for 30 calendar days or more. label Apr 24, 2022
@scmcca scmcca merged commit 6b7a2e8 into google:master Apr 26, 2022
@barbeau barbeau deleted the gtfs-guiding-principles-passenger-info branch April 26, 2022 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GTFS Schedule Issues and Pull Requests that focus on GTFS Schedule Status: Stale Issues and Pull Requests that have remained inactive for 30 calendar days or more.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants