GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-23T07:30:28Z,
for the dataset file:///shared/mumbai.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. calendar_dates.txt
  4. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 36
  • Routes: 2
  • Shapes: 4
  • Stops: 69
  • Trips: 36

Specification Compliance report

79 notices reported (0 errors, 78 warnings, 1 infos)

Notice Code Severity Total
expired_calendar WARNING 4

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 "1001"
3 "1002"
5 "1004"
6 "1005"
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 68

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 68 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.
"routes.txt" "route_short_name" "DEVRUKH SANGMESHWAR" 2
"routes.txt" "route_long_name" "DEVRUKH SANGMESHWAR" 2
"routes.txt" "route_short_name" "DEVRUKH RATNAGIRI" 3
"routes.txt" "route_long_name" "DEVRUKH RATNAGIRI" 3
"stops.txt" "stop_name" "DEVRUKH STAND" 2
"stops.txt" "stop_name" "SHIWAJI CHOWK" 3
"stops.txt" "stop_name" "PANCHAYAT SAMITI" 4
"stops.txt" "stop_name" "MAHADIK STOP" 5
"stops.txt" "stop_name" "SAHYADRI NAGAR TO SG" 6
"stops.txt" "stop_name" "P S BANE INT SCHOOL" 7
"stops.txt" "stop_name" "SAPTILINGI STOP" 8
"stops.txt" "stop_name" "SAMRUDHI NAGAR" 9
"stops.txt" "stop_name" "NAIDARWADI STOP" 10
"stops.txt" "stop_name" "SADAWLI BUS STOP" 11
"stops.txt" "stop_name" "SADAWLI ITI" 12
"stops.txt" "stop_name" "VANAZ BUS STOP" 13
"stops.txt" "stop_name" "LEISURE POINT" 14
"stops.txt" "stop_name" "MIDC STOP" 15
"stops.txt" "stop_name" "ADLER BUS STOP" 16
"stops.txt" "stop_name" "RAMWADI STOP" 17
"stops.txt" "stop_name" "KOSUMB HIGH SCHOOL" 18
"stops.txt" "stop_name" "KOSUMB BUS STOP" 19
"stops.txt" "stop_name" "DATTAMANDIR TAMHANE" 20
"stops.txt" "stop_name" "KARAMBALE SURVE STOP" 21
"stops.txt" "stop_name" "KHAKEWADI BUS STOP" 22
"stops.txt" "stop_name" "KARAMBELE PATI" 23
"stops.txt" "stop_name" "KARAMBELE PAWARWADI" 24
"stops.txt" "stop_name" "KARAMBALE MAHADIKWADI" 25
"stops.txt" "stop_name" "MAILDAGAD STOP" 26
"stops.txt" "stop_name" "PIMPALWADI STOP" 27
"stops.txt" "stop_name" "BURAMBI HIGH SCHOOL" 28
"stops.txt" "stop_name" "BURAMBI BUS STOP" 29
"stops.txt" "stop_name" "TERYE GELYEWADI" 30
"stops.txt" "stop_name" "MAYURBAUG LOVLE" 31
"stops.txt" "stop_name" "LOVLE STOP" 32
"stops.txt" "stop_name" "NAVNIRMAN COLLAGE" 33
"stops.txt" "stop_name" "SANGMESHWAR STAND" 34
"stops.txt" "stop_name" "SAHYADRI NAGAR TO RT" 35
"stops.txt" "stop_name" "MARLESHWAR PETROL PUMP" 36
"stops.txt" "stop_name" "SAVARKAR CHOWK" 37
"stops.txt" "stop_name" "FISH MARKET" 38
"stops.txt" "stop_name" "KANJI VARA" 39
"stops.txt" "stop_name" "NATE WADI" 41
"stops.txt" "stop_name" "PATGAV TITHA" 44
"stops.txt" "stop_name" "AMBAV CLG" 48
"stops.txt" "stop_name" "JK FILES" 63
"stops.txt" "stop_name" "SALVI STOP" 64
"stops.txt" "stop_name" "AAROGYA MANDIR" 65
"stops.txt" "stop_name" "MARUTI MANDIR" 66
"stops.txt" "stop_name" "RATNAGIRI BUS STAND" 70
route_long_name_contains_short_name WARNING 2

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`.
"16" 2 "DEVRUKH SANGMESHWAR" "DEVRUKH SANGMESHWAR"
"32" 3 "DEVRUKH RATNAGIRI" "DEVRUKH RATNAGIRI"
route_short_name_too_long WARNING 2

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

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`.
"16" 2 "DEVRUKH SANGMESHWAR"
"32" 3 "DEVRUKH RATNAGIRI"
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.
"20251223" "20250101" "20250630"
unknown_column INFO 1

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"stops.txt" "routes_belong" 11