GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T21:48:22Z,
for the dataset file:///shared/bata2.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
TecTransIT
Feed Email:
support@tectransit.com
Feed Language:
English

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 13
  • Shapes: 4
  • Stops: 124
  • Trips: 103

Specification Compliance report

165 notices reported (0 errors, 165 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.
"feed_info.txt" 2 "feed_start_date"
"feed_info.txt" 2 "feed_end_date"
mixed_case_recommended_field WARNING 2

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_long_name" "express line" 2
"routes.txt" "route_desc" "express line" 2
same_name_and_description_for_route WARNING 13

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

Description of a route that provides useful, quality information. Do not simply duplicate the name of the route.

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. routeId (?) The id of the faulty record. routeDesc (?) The `routes.routes_desc` of the faulty record. specifiedField (?) Either `route_short_name` or `route_long_name`.
2 "express line" "express line" "route_long_name"
3 "Pumpkin 1" "Pumpkin 1" "route_long_name"
4 "Pumpkin 1 Sat" "Pumpkin 1 Sat" "route_long_name"
5 "Pumpkin 1 Sun" "Pumpkin 1 Sun" "route_long_name"
6 "Pumpkin 2" "Pumpkin 2" "route_long_name"
7 "Pumpkin 2 Sat" "Pumpkin 2 Sat" "route_long_name"
8 "Pumpkin 2 Sun" "Pumpkin 2 Sun" "route_long_name"
9 "Teal 1" "Teal 1" "route_long_name"
10 "Teal 1 Sat" "Teal 1 Sat" "route_long_name"
11 "Teal 1 Sun" "Teal 1 Sun" "route_long_name"
12 "Teal 2" "Teal 2" "route_long_name"
13 "Teal 2 Sat" "Teal 2 Sat" "route_long_name"
14 "Teal 2 Sun" "Teal 2 Sun" "route_long_name"
stop_without_stop_time WARNING 91

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

Only the first 50 of 91 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
2 "53" "W Badillo St & Vineland Ave"
4 "55" "Puente Ave & Central Ave"
5 "56" "Puente Ave & W Pacific Ave (SW)"
6 "57" "Puente Ave & Channing St (SW)"
8 "59" "Puente Ave & Merced Ave (SW)"
9 "60" "Puente Ave & Dalewood St (SW)"
10 "61" "Puente Ave & Francisquito Ave (SW)"
11 "62" "Francisquito Ave & Big Dalton Ave (NW)"
13 "64" "Francisquito Ave & Maine Ave (NB)"
14 "65" "Baldwin Park Blvd & Francisquito Ave"
16 "68" "Baldwin Park Blvd & Dalewood St"
17 "69" "Dalewood St (Kaiser Parking Lot Wb)"
18 "70" "Dalewood St & Leorita St (WB)"
19 "71" "Frazier St & Athol St"
20 "72" "Athol St & Bess Ave (NB)"
21 "73" "Fairgrove St & Athol St (NB)"
22 "74" "Fairgrove St & Barnes Ave (WB)"
23 "75" "Syracuse Ave & Fairgrove St"
24 "76" "Syracuse Ave & Royston St (NB)"
26 "78" "Ramona Blvd & Barnes Ave"
27 "79" "Ramona Blvd & Francisquito Ave (EB)"
28 "80" "Ramona Blvd & Earl Ave (EB)"
29 "81" "Ramona Blvd & Foster Ave (EB)"
30 "82" "Ramona Blvd & Monterey Ave (EB)"
31 "83" "Lubican St & Merced Ave (NB)"
32 "84" "Merced Ave & Palm Ave (NB)"
34 "86" "Los Angeles St & Center St (WB)"
35 "87" "Los Angeles St & Hornbrook Ave (WB)"
36 "88" "Littlejohn St (NB)"
37 "89" "Littlejohn St & Brooks Dr (NB)"
38 "90" "Commerce Dr & Rivergrade Dr (EB)"
41 "93" "Nubia St & Baldwin Park Blvd (EB)"
42 "94" "Nubia St & Landis Ave (EB)"
43 "95" "Nubia Ave & Wimmer Ave (EB)"
44 "96" "Maine Ave & Joanbridge St (NB)"
45 "97" "Bleeker St & Joanbridge St (SB)"
46 "98" "Nubia St. & Bleeker St. (EB)"
47 "99" "Nubia St & Elton St (EB)"
48 "100" "Nubia St & Lante St (EB)"
50 "102" "LA Sena Ave & Olive St"
51 "103" "Olive St & Fortin St"
52 "104" "Olive St & Stancroft Ave"
53 "105" "Olive St & Bleeker St (WB)"
55 "107" "Maine Ave & Ohio St (SB)"
56 "108" "Maine Ave & Los Angeles St (SB)"
59 "111" "Ramona Blvd & Maine Ave (EB)"
61 "114" "Downing Ave & Pacific Ave"
62 "115" "Ramona Blvd & Bogart"
64 "118" "Maine Ave & Los Angeles St (NB)"
65 "119" "Maine Ave & Ohio St (NB)"
unusable_trip WARNING 28

unusable_trip

Trips must have more than one stop to be usable.

A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's id.
32 "248"
34 "250"
53 "269"
54 "270"
56 "272"
58 "274"
60 "276"
62 "278"
64 "280"
66 "282"
69 "285"
71 "287"
73 "289"
75 "291"
77 "293"
80 "296"
82 "298"
84 "300"
86 "302"
88 "304"
90 "306"
93 "309"
95 "311"
97 "313"
99 "315"
101 "317"
103 "319"
104 "320"
unused_shape WARNING 1

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"4" 2
unused_trip WARNING 28

unused_trip

Trip is not be used in stop_times.txt

Trips should be referred to at least once in stop_times.txt.

You can see more about this notice here.

tripId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"248" 32
"250" 34
"269" 53
"270" 54
"272" 56
"274" 58
"276" 60
"278" 62
"280" 64
"282" 66
"285" 69
"287" 71
"289" 73
"291" 75
"293" 77
"296" 80
"298" 82
"300" 84
"302" 86
"304" 88
"306" 90
"309" 93
"311" 95
"313" 97
"315" 99
"317" 101
"319" 103
"320" 104