GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T14:20:00Z,
for the dataset file:///shared/green-mountain.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2025-09-01
Feed End Date:
2026-05-01

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 8
  • Routes: 7
  • Shapes: 29
  • Stops: 79
  • Trips: 150

Specification Compliance report

8 notices reported (0 errors, 4 warnings, 4 infos)

Notice Code Severity Total
expired_calendar WARNING 1

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "225-c_18079_b_85076_d_31"
fast_travel_between_consecutive_stops WARNING 3

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type Description Threshold, km/h
0 Light rail 100
1 Subway 150
2 Rail 500
3 Bus 150
4 Ferry 80
5 Cable tram 30
6 Aerial lift 50
7 Funicular 50
11 Trolleybus 150
12 Monorail 150
- Unknown 200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
134 "225-t_6116954_b_85722_tn_0" "225-1443" 2137.0519690006386 0.5936255469446218 1206 0 "225-801460" "Stewart's Pownal" "12:30:00" 1207 1 "225-4248598" "Svmc Pownal Campus" "12:30:01"
133 "225-t_6116953_b_85722_tn_0" "225-1443" 2137.0519690006386 0.5936255469446218 1199 0 "225-801460" "Stewart's Pownal" "10:35:00" 1200 1 "225-4248598" "Svmc Pownal Campus" "10:35:01"
126 "225-t_6116947_b_85722_tn_0" "225-1443" 262.88818836651234 4.381469806108539 1152 6 "225-770832" "Stewart's Pownal" "09:00:00" 1153 7 "225-4258626" "Field Park" "09:00:00"
stop_without_zone_id INFO 4

stop_without_zone_id

Stop without value for stops.zone_id contained in a route with a zone-dependent fare rule.

If fare_rules.txt is provided, and fare_rules.txt uses at least one column among origin_id, destination_id, and contains_id, then all stops and platforms (location_type = 0) must have stops.zone_id assigned if they are defined in a trip defined in a route defined in a fare rule which also defines at least one of origin_id, destination_id, or contains_id.

You can see more about this notice here.

stopId (?) The faulty record's id. stopName (?) The faulty record's `stops.stop_name`. csvRowNumber (?) The row number of the faulty record.
"225-4248598" "Svmc Pownal Campus" 19
"225-4249014" "Solomon Wright Library Pownal" 20
"225-4258453" "Manchester Park and Ride" 24
"225-4258626" "Field Park" 25