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.

Sign up for GitHub

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

Jump to bottom

Notice when wheelchair_boarding and wheelchair_accessible fields are missing from stops.txt and trips.txt #1276

Open
owades opened this issue Oct 17, 2022 · 2 comments
Open

Notice when wheelchair_boarding and wheelchair_accessible fields are missing from stops.txt and trips.txt #1276

owades opened this issue Oct 17, 2022 · 2 comments
Labels
community rules This is used for Out of Spec / Out of Best Practice rules that we'd like to include in the validator new rule New rule to be added status: Blocked Can't work on it currently because of an external factor.

Comments

@owades
Copy link

owades commented Oct 17, 2022

Describe the problem

Per the California Minimum General Transit Feed Specification (GTFS) Guidelines, the file stops.txt is required to have a non-null value in the wheelchair_boarding column for all rows, and same with wheelchair_accessible in trips.txt. We don't yet have a validation rule for these.

Describe the new validation rule

In stops.txt, if any row has a null value in the wheelchair_boarding column, trigger a 'missing_accessibility_fields' notice.
In trips.txt, if any row has a null value in the wheelchair_accessible column, trigger a 'missing_accessibility_fields' notice.

Sample GTFS datasets

No response

Severity

Warning

Additional context

No response
@owades owades added new rule New rule to be added status: Needs triage Applied to all new issues labels Oct 17, 2022
@isabelle-dr
Copy link
Contributor

Please refer to my comment in issue #1275

@isabelle-dr isabelle-dr added status: Needs discussion We need a discussion on requirements before calling this issue ready community rules This is used for Out of Spec / Out of Best Practice rules that we'd like to include in the validator status: Blocked Can't work on it currently because of an external factor. and removed status: Needs triage Applied to all new issues status: Needs discussion We need a discussion on requirements before calling this issue ready labels Nov 3, 2022
@isabelle-dr
Copy link
Contributor

Labeling as blocked, let's come back to this issue when we close issue #1067.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
community rules This is used for Out of Spec / Out of Best Practice rules that we'd like to include in the validator new rule New rule to be added status: Blocked Can't work on it currently because of an external factor.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@owades @isabelle-dr