Elizabeth Sall

Bug: Running using documented Docker documentation fails

2

## **Bug report** **Describe the bug** I followed the directions in readme.md for running app via Docker but it did not work. Suspect documentation just needs to be adjusted. **How...

Fast Travel Between Far Stops not using `stops.stop_timezone`

12

## **Bug report** **Describe the bug** `Fast Travel Between Far Stops` warning incorrectly given where stops change time zones because the field `stops.stop_timezone` is not taken into account. This is...

Best Practice: stop names should be in mixed case (WARNING)

4

Provide stop names in mixed case, following local conventions, as per recommendation for all customer-facing text fields.

Best Practice: stop name shouldn't include 'stop' or 'station' unless that is really part of its name (WARNING)

6

> By default, stop_name should not contain generic or redundant words like “Station” or “Stop”, but some edge cases are allowed. > - When it is actually part of the...

Best Practice: Include agency_id in routes.txt (WARNING)

2

Including `agency_id` in `routes.txt` is a best practice and should generate a warning even though it is not required if there is only one. Implementatin thoughts: Rather than returning here...

Best Practice: If parent_station !=0, stop_name should include parent_station stop_name (WARNING)

6

> If parent_station !=0, stop_name should include parent_station stop_name >

Best Practice: Shape_dist_travelled must be included if route passes over same stop or segment (loop, lollipop, inlining) (WARNING)

4

> Shape_dist_travelled must be included if route passes over same stop or segment (loop, lollipop, inlining)

Best Practice: Date Validity (WARNING)

8

Per the best practices: - Dataset should be valid for at least the next seven days [ from publication date? ] - Dataset shouldn't include date ranges that have already...

Create issue templates, pull-requests and issue tags

1

Templates are helpful for helping organize development from many parties and providing consistent, comprehensive documentation about why, how, etc. Here is a collection of many to start from: https://github.com/stevemao/github-issue-templates I...

For example, in `link_tod`: - would we have multiple entries for each `link_id`, and time of day for each `allowed_uses`? - how would I define an HOT lane?