GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-16T19:51:37Z,
for the dataset file:///shared/rapid-bus-penang.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. routes.txt
  4. shapes.txt
  5. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 48
  • Shapes: 98
  • Stops: 1926
  • Trips: 8030

Specification Compliance report

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

Notice Code Severity Total
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 8043

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.

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

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"stops.txt" "stop_name" "PUSAT PERNIAGAAN PADANG SERAI" 186
"stops.txt" "stop_name" "TAMAN SELESA" 219
"stops.txt" "stop_name" "TAMAN LAGENDA" 690
"stops.txt" "stop_name" "(M1) JETTY B" 740
"stops.txt" "stop_name" "KTM BM" 826
"stops.txt" "stop_name" "PEKAN PADANG SERAI" 906
"stops.txt" "stop_name" "PEKAN PADANG SERAI" 938
"stops.txt" "stop_name" "TAMAN MAHSURI" 939
"stops.txt" "stop_name" "(M1) JETTY A" 1078
"stops.txt" "stop_name" "PUSAT PERNIAGAAN PADANG SERAI" 1181
"stops.txt" "stop_name" "PUSAT SERENTI KG. SELAMAT" 1408
"stops.txt" "stop_name" "(M2) RECSAM" 1501
"stops.txt" "stop_name" "TAMAN SERAI WANGI" 1628
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 2
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 3
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 4
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 5
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 6
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 7
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 8
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 9
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 10
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 11
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 12
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 13
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 14
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 15
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 16
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 17
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 18
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 19
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 20
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 21
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 22
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 23
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 24
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 25
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 26
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 27
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 28
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 29
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 30
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 31
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 32
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 33
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 34
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 35
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 36
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 37
"trips.txt" "trip_headsign" "TLK.BAHANG-JETI" 38
route_long_name_contains_short_name WARNING 48

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"30000019" 2 "401" "401"
"30000051" 3 "CAT" "CAT"
"30000009" 4 "206" "206"
"30000006" 5 "202" "202"
"30000040" 6 "708" "708"
"30000089" 7 "613" "613"
"30000038" 8 "703" "703"
"30000048" 9 "11" "11"
"30000001" 10 "101" "101"
"30000007" 11 "203" "203"
"30000021" 12 "403" "403"
"30000117" 13 "CT14" "CT14"
"30000100" 14 "CT13" "CT13"
"30000020" 15 "401E" "401E"
"30000010" 16 "301" "301"
"30000014" 17 "304" "304"
"30000005" 18 "201" "201"
"30000012" 19 "302" "302"
"30000018" 20 "308" "308"
"30000034" 21 "610" "610"
"30000119" 22 "T310" "T310"
"30000026" 23 "601" "601"
"30000028" 24 "604" "604"
"30000041" 25 "709" "709"
"30000013" 26 "303" "303"
"30000042" 27 "801" "801"
"30000008" 28 "204" "204"
"30000022" 29 "404" "404"
"30000049" 30 "12" "12"
"30000032" 31 "606" "606"
"30000016" 32 "306" "306"
"30000139" 33 "CT15" "CT15"
"30000037" 34 "702" "702"
"30000031" 35 "605" "605"
"30000046" 36 "EB60" "EB60"
"30000043" 37 "802" "802"
"30000003" 38 "103" "103"
"30000141" 39 "502." "502."
"30000045" 40 "EB80" "EB80"
"30000002" 41 "102" "102"
"30000004" 42 "104" "104"
"30000104" 43 "C13C" "C13C"
"30000142" 44 "502C" "502C"
"30000036" 45 "701" "701"
"30000050" 46 "13" "13"
"30000027" 47 "603" "603"
"30000140" 48 "T713" "T713"
"30000103" 49 "C13A" "C13A"
stop_too_far_from_shape_using_user_distance WARNING 3

stop_too_far_from_shape_using_user_distance

Stop time too far from shape.

A stop time entry that is a large distance away from the location of the shape in shapes.txt as defined by shape_dist_traveled values.

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.
8031 "1000001039" "260114043099S2" 90628 "12002113" "(M1) JETTY A" [5.415365635811549,100.34128885844703] 168.42718205237495
8031 "1000001039" "260114043099S2" 90629 "12000007" "Container Hotel" [5.415663196955158,100.34214644393556] 254.63024574861626
752 "1000000931" "260114049030S6" 106805 "12002981" "Terminal UTC Ukir Square" [5.641310363678774,100.49065263586601] 115.4481884277258
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260116" "20260119" "20260209"