Green Mountain Transit Open Data
Overview
Green Mountain Transit (GMT) publishes open datasets to support transparency, analysis, and public understanding of transit operations in our urban service area. This site provides access to ridership, fare transaction, and stop-level boarding estimates, along with dashboards for exploring trends over time.
All datasets are updated on a monthly schedule and are freely available for informational and analytical use.
Ridership Data
Monthly ridership performance by route can be explored in the Ridership Tracker Dashboard.
Reported metrics include:
- Total ridership (passenger boardings)
- Total vehicle hours in operation
- Weekday ridership and vehicle hours
- Saturday ridership and vehicle hours
- Sunday ridership and vehicle hours
Ridership Data Downloads
| Dataset | Download |
|---|---|
| FY25 Route totals by month | CSV |
| FY26 Route totals by month | CSV |
Fare Transactions
Trends in fare usage can be explored in the Fare Tracker Dashboard.
Each time a rider boards a bus and validates a fare, a fare transaction is recorded. Fare transactions are summarized monthly and reported by:
- Fare Group - the broad category of fare a rider used
- Fare Capture Method - how the fare was validated when boarding
- Fare Funding Source - who ultimately paid for the ride
Fare transactions represent completed payments and may not correspond one-to-one with passenger boardings.
Fare Data Downloads
| Dataset | Download |
|---|---|
| FY26 Fare group totals by month | CSV |
| FY26 Fare group totals by month and route | CSV |
| FY26 Fare funding source totals by month | CSV |
| FY26 Fare capture method totals by month | CSV |
Notes:
The
pctcolumn represents the share of fare transactions within each month. For datasets that include route detail, percentages are calculated within each month and route. For datasets without route detail, percentages are calculated within each month across all routes.Routes 56 (Milton Commuter) and 96 (St. Albans Link) are reported together as Route 96 for consistency, following the absorption of Route 56 into Route 96 to create the Franklin County Commuter on August 25, 2025.
Boarding Estimates by Stop
Estimated boardings by stop can be explored in the Boarding Estimates by Stop Dashboard.
Stop-level boarding estimates are produced by matching fare transaction timestamps to vehicle GPS locations and associating each transaction with the nearest stop along the route based on the latest GTFS feed. Because these estimates rely on spatial and temporal inference, they should be interpreted as approximate.
Important considerations:
- Stop-level estimates will not sum to published ridership totals
- Stop-level data should not be aggregated to the route level
- Route-level analysis should use the ridership datasets above
- Because stop assignments are based on the GTFS feed at the time of processing, some historical transactions may be attributed to stops that were not in service at the time.
Stop Data Downloads
| Dataset | Download |
|---|---|
| FY26 boarding estimates by stop | CSV |
Data Limitations and Use
These datasets are provided for informational and analytical purposes only and are released without warranty. GMT makes no guarantees regarding completeness, accuracy, or fitness for any particular purpose.
Stop-level boarding estimates and other inferred values are subject to methodological limitations and should be interpreted with care. The data may not be suitable for detailed operational, financial, or regulatory reporting without additional validation.
Datasets are typically published within one month of the close of each reporting period. Substantive revisions to previously published data will be documented in the project changelog.
Contact and Feedback
Questions, feedback, or issue reports are welcome and may be submitted through this feedback form, our Github repository, or by contacting planning@ridegmt.com.
Public feedback helps improve data quality, documentation, and usability.