Skip to content

Minor website tweaks #130

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

Open
jeffkessler-keolis wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Minor website tweaks #130

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
956cd02
Correct revision history dates
jeffkessler-keolis Jan 2, 2026
57cefce
Update index.md
jeffkessler-keolis Jan 2, 2026
b7dc9ca
Correct standard version and date
jeffkessler-keolis Jan 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/en/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ Transit providers need the systems they use to schedule and operate their servic

TODS is an open standard which extends GTFS to define additional operational details necessary to operate the service such as deadheads and runs.

!!! warning "Does TODS Data has to be Open data?"
!!! warning "Does TODS Data have to be Open data?"

While GTFS data can and should be public so that riders can learn about service, TODS data is typically not published in order to preserve the privacy of internal operations data.

Expand All @@ -60,6 +60,8 @@ TODS is used by transit agencies and the software which supports them including:

:material-check-circle-outline: [MBTA](http://mbta.com) (in progress)

:material-check-circle-outline: [Keolis Commuter Services](https://www.keolisna.com/locations/boston-massachusetts) (in progress)

### TODS 1.0

:material-check-circle: [WETA](https://weta.sanfranciscobayferry.com/)
Expand Down
4 changes: 2 additions & 2 deletions docs/en/spec/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

# Reference

The Transit Operational Data Standard was last updated on April 3, 2024 (v2.0 DRAFT). View the full [revision history](./revision-history.md).
The Transit Operational Data Standard was last updated on September 4, 2025 (v2.1.0). View the full [revision history](./revision-history.md).

## Dataset Files

Expand Down Expand Up @@ -206,4 +206,4 @@ Primary Key: `(date, block_id, service_id)`

Not every block and date combo needs to have a vehicle specified.

*Note for future-compatibility:* `vehicle_id` field may change to conditionally required in a future version where assignments may be made to either an individual vehicle OR a grouping of vehicles. See [GTFS-Vehicles](http://bit.ly/gtfs-vehicles) for how vehicle categories (types) might be incorporated.
*Note for future-compatibility:* `vehicle_id` field may change to conditionally required in a future version where assignments may be made to either an individual vehicle OR a grouping of vehicles. See [GTFS-Vehicles](http://bit.ly/gtfs-vehicles) for how vehicle categories (types) might be incorporated.
4 changes: 2 additions & 2 deletions docs/en/spec/revision-history.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Revision History

## 16 April 2025
## 4 September 2025
TODS 2.1.0 is adopted

* Adds new TODS-specific files `vehicle_assignments.txt`, `vehicles.txt`, and `employee_run_dates.txt`.
* Adds new supplemental files `calendar_dates_supplement.txt` and `calendar_supplement.txt`

## 24 July 2025
Copy link
Collaborator

@jfabi jfabi Jan 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffkessler-keolis While this entry was first committed on 9 April 2025, I think this was intended to read 24 July 2024, which is the date the v2.0 voting closed.

Similarly, 16 April 2025 was when the voting for #85 and #87 end, though the former was not merged in until July.

Copy link
Collaborator Author

@jeffkessler-keolis jeffkessler-keolis Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it; that makes more sense! Was confused by the out-of-sequence dates when reviewing.

Also wasn't sure if we were saying the adoption is as of the vote close or the merge.

## 9 April 2025

TODS 2.0.0 is adopted, now to be implemented.

Expand Down