GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-23T07:10:00Z,
for the dataset file:///shared/muni.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • San Francisco Municipal Transportation Agency

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2025-08-30
Feed End Date:
2026-02-14

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: 1875
  • Routes: 68
  • Shapes: 289
  • Stops: 3207
  • Trips: 34588

Specification Compliance report

46 notices reported (0 errors, 46 warnings, 0 infos)

Notice Code Severity Total
missing_recommended_field WARNING 2

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
mixed_case_recommended_field WARNING 40

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"routes.txt" "route_desc" "5am-12 midnight daily" 2
"routes.txt" "route_desc" "6am-10pm daily" 3
"routes.txt" "route_desc" "24 hour service daily" 4
"routes.txt" "route_desc" "5am-10pm daily" 5
"routes.txt" "route_desc" "6am-10pm daily" 7
"routes.txt" "route_desc" "5am-10pm daily" 8
"routes.txt" "route_desc" "6:30am-7pm daily" 10
"routes.txt" "route_desc" "24 hour service daily" 11
"routes.txt" "route_desc" "6am-10pm daily" 12
"routes.txt" "route_desc" "24 hour service daily" 14
"routes.txt" "route_desc" "5am-10pm daily" 15
"routes.txt" "route_desc" "5am-12 midnight daily" 16
"routes.txt" "route_desc" "5am-12 midnight daily" 18
"routes.txt" "route_desc" "5am-10pm daily" 21
"routes.txt" "route_desc" "5am-10pm daily" 22
"routes.txt" "route_desc" "7am-9pm daily" 23
"routes.txt" "route_desc" "24 hour service daily" 26
"routes.txt" "route_desc" "9am-7pm daily" 28
"routes.txt" "route_desc" "5am-12 midnight daily" 29
"routes.txt" "route_desc" "5am-10pm daily" 31
"routes.txt" "route_desc" "5am-12 midnight daily" 33
"routes.txt" "route_desc" "5am-10pm daily" 36
"routes.txt" "route_desc" "5am-10pm daily" 37
"routes.txt" "route_desc" "7am-9pm daily" 38
"routes.txt" "route_desc" "5am-10pm daily" 39
"routes.txt" "route_desc" "5am-10pm daily" 42
"routes.txt" "route_desc" "5am-10pm daily" 45
"routes.txt" "route_desc" "5am-12 midnight daily" 47
"routes.txt" "route_short_name" "8ax" 48
"routes.txt" "route_short_name" "8bx" 49
"routes.txt" "route_desc" "5am-12 midnight daily" 50
"routes.txt" "route_desc" "12 midnight-5am daily" 51
"routes.txt" "route_desc" "12 midnight-5am daily" 52
"routes.txt" "route_desc" "7 am-8:30 pm daily" 54
"routes.txt" "route_desc" "7am-10pm daily" 55
"routes.txt" "route_desc" "5am-12 midnight daily" 57
"routes.txt" "route_desc" "10pm-5am nightly" 61
"routes.txt" "route_desc" "12 midnight-5am nightly" 65
"routes.txt" "route_desc" "7 am-10 pm daily" 66
"routes.txt" "route_desc" "7 am-10 pm daily" 67
stop_too_far_from_shape WARNING 4

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
17856 "105787-1206" "105787-11939869" 654710 "105787-5334" "Main St & Howard St" [37.79177059449053,-122.39312565424278] 103.06192376879068
17517 "105787-9666" "105787-11929116_M11" 644004 "105787-5418" "Balboa Park Bart/Mezzanine Level" [37.72119004298725,-122.44624682511957] 124.39943943082999
16731 "105787-9665" "105787-11929066_M11" 616922 "105787-5418" "Balboa Park Bart/Mezzanine Level" [37.72119004298725,-122.44624682511957] 124.39943943082999
23760 "105787-851" "105787-11902394_M11" 875489 "105787-4811" "Geneva Ave & Cayuga Ave" [37.717838,-122.44235100000003] 144.4257933468738