Skip to content

Issues: MobilityData/gtfs-validator

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

Clear current search query, filters, and sorts
150 Open 733 Closed
150 Open 733 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

API for Web UI enhancement New feature request or improvement on an existing feature
#495 opened Nov 30, 2020 by NomeQ Future work
@Cristhian-HA
4
Implement feed dates verification (GTFS rule) 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 python validator Rules implemented in the original Google Python Validator status: Needs discussion We need a discussion on requirements before calling this issue ready
#140 opened Apr 29, 2020 by maximearmstrong Future work
1
Implement service gap verification for feed (GTFS rule) 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 python validator Rules implemented in the original Google Python Validator
#142 opened Apr 29, 2020 by maximearmstrong Future work
6
Implement station usage verification (GTFS rule) 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 python validator Rules implemented in the original Google Python Validator status: Ready An issue that is ready to be worked on.
#153 opened May 1, 2020 by maximearmstrong Future work
9
Implement stops and stations too close validation (GTFS Rule) 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 python validator Rules implemented in the original Google Python Validator status: Blocked Can't work on it currently because of an external factor.
#154 opened May 1, 2020 by maximearmstrong Future work
3
Implement walking speed verification for a transfer 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 python validator Rules implemented in the original Google Python Validator status: Blocked Can't work on it currently because of an external factor.
#158 opened May 4, 2020 by maximearmstrong Future work
1
Implement minimum transfer time verification 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 python validator Rules implemented in the original Google Python Validator status: Blocked Can't work on it currently because of an external factor.
#159 opened May 4, 2020 by maximearmstrong Future work
1
4
[REQUEST] Implement shapes exists for a trip verification (GTFS rule) python validator Rules implemented in the original Google Python Validator status: Ready An issue that is ready to be worked on.
#164 opened May 4, 2020 by maximearmstrong
1
4
Implement trip consecutive stops verification (GTFS rule) 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 python validator Rules implemented in the original Google Python Validator status: Blocked Can't work on it currently because of an external factor.
#178 opened May 4, 2020 by maximearmstrong Future work
3
Implement transfer distance verification 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 python validator Rules implemented in the original Google Python Validator status: Blocked Can't work on it currently because of an external factor.
#203 opened May 11, 2020 by maximearmstrong Future work
2
Add command-line option to exclude certain rules enhancement New feature request or improvement on an existing feature status: Needs discussion We need a discussion on requirements before calling this issue ready
#215 opened May 27, 2020 by lionel-nj
1
@lionel-nj
2
Implement verbosity option enhancement New feature request or improvement on an existing feature help wanted We need help from the community status: Ready An issue that is ready to be worked on.
#256 opened Jun 5, 2020 by lionel-nj Future work
1
Implement calendar has active days (GTFS rule) 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 python validator Rules implemented in the original Google Python Validator status: Needs discussion We need a discussion on requirements before calling this issue ready
#134 opened Apr 29, 2020 by maximearmstrong Future work
7
Trigger warning for duplicated stop_code 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.
#471 opened Oct 29, 2020 by antrim Future work
5
Move utility methods into core efficiency Used for efficiency-related issues (remove code duplication, refactor, etc). enhancement New feature request or improvement on an existing feature status: Needs discussion We need a discussion on requirements before calling this issue ready
#791 opened Mar 4, 2021 by lionel-nj
Cover autogenerated end-range validators by unit tests in processor efficiency Used for efficiency-related issues (remove code duplication, refactor, etc). enhancement New feature request or improvement on an existing feature status: Needs discussion We need a discussion on requirements before calling this issue ready tests Anything related to our tests.
#818 opened Mar 17, 2021 by aababilov
Parsing errors enhancement New feature request or improvement on an existing feature parsing errors Related to improving validator parsing and clearer parsing error messages.
#840 opened Mar 29, 2021 by lionel-nj Future work
3
Cover autogenerated lat-lon validators by unit tests in "processor" efficiency Used for efficiency-related issues (remove code duplication, refactor, etc). enhancement New feature request or improvement on an existing feature status: Needs discussion We need a discussion on requirements before calling this issue ready tests Anything related to our tests.
#846 opened Apr 1, 2021 by lionel-nj
Improvement: merge INVALID_HEADERS and UNPARSABLE_ROWS to a single status PARSING_FAILED in a separate PR. efficiency Used for efficiency-related issues (remove code duplication, refactor, etc). enhancement New feature request or improvement on an existing feature status: Needs discussion We need a discussion on requirements before calling this issue ready
#879 opened Apr 28, 2021 by lionel-nj
Best Practice: stop name shouldn't include 'stop' or 'station' unless that is really part of its name (WARNING) good first issue Good task for newcomers to work on. GTFS Best Practices Used for Adding or changing rules that belong in the GTFS Best Practices new rule New rule to be added status: Blocked Can't work on it currently because of an external factor. status: Needs discussion We need a discussion on requirements before calling this issue ready
#882 opened Apr 29, 2021 by e-lo
6
Best Practice: If parent_station !=0, stop_name should include parent_station stop_name (WARNING) good first issue Good task for newcomers to work on. GTFS Best Practices Used for Adding or changing rules that belong in the GTFS Best Practices new rule New rule to be added status: Needs discussion We need a discussion on requirements before calling this issue ready
#883 opened Apr 29, 2021 by e-lo
6
Best Practice: Shape_dist_travelled must be included if route passes over same stop or segment (loop, lollipop, inlining) (WARNING) good first issue Good task for newcomers to work on. GTFS Best Practices Used for Adding or changing rules that belong in the GTFS Best Practices new rule New rule to be added status: Needs discussion We need a discussion on requirements before calling this issue ready
#884 opened Apr 29, 2021 by e-lo
4
Allow non ASCII but printable characters in ID field community rules This is used for Out of Spec / Out of Best Practice rules that we'd like to include in the validator enhancement New feature request or improvement on an existing feature GTFS Reference Used for Adding or changing rules that belong in the GTFS reference status: Blocked Can't work on it currently because of an external factor.
#918 opened Jun 24, 2021 by niyalist Future work
3
Allow Extended GTFS Route Type values community rules This is used for Out of Spec / Out of Best Practice rules that we'd like to include in the validator enhancement New feature request or improvement on an existing feature status: Needs discussion We need a discussion on requirements before calling this issue ready
#927 opened Jul 15, 2021 by naxxfish Future work
1
6
Validator v6 Fails to Validate GTFS File (UNPARSABLE_ROWS) bug Something isn't working (crash, a rule has a problem) status: Needs triage Applied to all new issues
#1918 opened Nov 7, 2024 by tafflin
@qcdyx
3
ProTip! Adding no:label will show everything without a label.