Home
India Feeds
chennai-mtc-cmrl
Source Data Validation Report

chennai-mtc-cmrl — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-01T15:45:01Z,
for the dataset file:///shared/chennai-mtc-cmrl_e0cb54e5.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Metropolitan Transport Corporation
- website: https://mtcbus.tn.gov.in/
- phone number:
- email: Not provided
Chennai Metro Rail Limited
- website: https://chennaimetrorail.org/
- phone number:
- email: Not provided

Feed Info

Publisher Name:
Ithu Ungal Soththu: Publisher URL:
https://ithuungalsoththu.vercel.app/: Feed Email:
N/A: Feed Language:
Tamil: Feed Start Date:
2025-03-01: Feed End Date:
2025-12-31

Files included

agency.txt
calendar.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 2
Blocks: 0
Routes: 0
Shapes: 4
Stops: 0
Trips: 0

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

ShapesFeed Information

Specification Compliance report

1645 notices reported (149 errors, 1490 warnings, 6 infos)

Notice Code Severity Total

invalid_integer ERROR 3

invalid_integer

A field cannot be parsed as an integer.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) Faulty record's field name.	fieldValue (?) Faulty value.
"routes.txt"	4613	"route_type"	"Blue Line — Wimco Nagar Depot ↔ Airport"
"routes.txt"	4614	"route_type"	"Green Line — MGR Central ↔ St. Thomas Mount"
"routes.txt"	4615	"route_type"	"Inter-Corridor — MGR Central ↔ Airport"

invalid_row_length ERROR 146

invalid_row_length

Invalid csv row length.

A row in the input file has a different number of values than specified by the CSV header.

You can see more about this notice here.

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

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	rowLength (?) The length of the faulty record.	headerCount (?) The number of column in the faulty file.
"stops.txt"	5583	5	4
"stops.txt"	5584	5	4
"stops.txt"	5585	5	4
"stops.txt"	5586	5	4
"stops.txt"	5587	5	4
"stops.txt"	5588	5	4
"stops.txt"	5589	5	4
"stops.txt"	5590	5	4
"stops.txt"	5591	5	4
"stops.txt"	5592	5	4
"stops.txt"	5593	5	4
"stops.txt"	5594	5	4
"stops.txt"	5595	5	4
"stops.txt"	5596	5	4
"stops.txt"	5597	5	4
"stops.txt"	5598	5	4
"stops.txt"	5599	5	4
"stops.txt"	5600	5	4
"stops.txt"	5601	5	4
"stops.txt"	5602	5	4
"stops.txt"	5603	5	4
"stops.txt"	5604	5	4
"stops.txt"	5605	5	4
"stops.txt"	5606	5	4
"stops.txt"	5607	5	4
"stops.txt"	5608	5	4
"stops.txt"	5609	5	4
"stops.txt"	5610	5	4
"stops.txt"	5611	5	4
"stops.txt"	5612	5	4
"stops.txt"	5613	5	4
"stops.txt"	5614	5	4
"stops.txt"	5615	5	4
"stops.txt"	5616	5	4
"stops.txt"	5617	5	4
"stops.txt"	5618	5	4
"stops.txt"	5619	5	4
"stops.txt"	5620	5	4
"stops.txt"	5621	5	4
"stops.txt"	5622	5	4
"stops.txt"	5623	5	4
"stops.txt"	5624	5	4
"stops.txt"	5625	5	4
"stops.txt"	5626	5	4
"trips.txt"	47049	5	4
"trips.txt"	47050	5	4
"trips.txt"	47051	5	4
"trips.txt"	47052	5	4
"trips.txt"	47053	5	4
"trips.txt"	47054	5	4

feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	currentDate (?) Current date (YYYYMMDD format).	feedEndDate (?) Feed end date (YYYYMMDD format).	suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2	"20260801"	"20251231"	"20260808"

missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2

mixed_case_recommended_field WARNING 1488

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 1488 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"	"22 CT"	5
"routes.txt"	"route_short_name"	"15 CT8"	6
"routes.txt"	"route_short_name"	"29A CT"	8
"routes.txt"	"route_short_name"	"40A CT"	10
"routes.txt"	"route_short_name"	"21 CT1"	14
"routes.txt"	"route_short_name"	"29B CT"	46
"routes.txt"	"route_short_name"	"29B CT"	47
"routes.txt"	"route_short_name"	"29C CT"	48
"routes.txt"	"route_short_name"	"19 CT4"	52
"routes.txt"	"route_short_name"	"45B CT"	70
"routes.txt"	"route_short_name"	"45B CT1"	73
"routes.txt"	"route_short_name"	"45B CT2"	75
"routes.txt"	"route_short_name"	"102K CT2"	76
"routes.txt"	"route_short_name"	"12B CT1"	80
"routes.txt"	"route_short_name"	"21G CT2"	81
"routes.txt"	"route_short_name"	"102K CT3"	83
"routes.txt"	"route_short_name"	"102K CT4"	84
"routes.txt"	"route_short_name"	"41D CT"	85
"routes.txt"	"route_short_name"	"2B CT"	93
"routes.txt"	"route_short_name"	"21G CT3"	94
"routes.txt"	"route_short_name"	"102K CT10"	96
"routes.txt"	"route_short_name"	"72 CT8"	97
"routes.txt"	"route_short_name"	"2B CT1"	99
"routes.txt"	"route_short_name"	"21G CT2"	100
"routes.txt"	"route_short_name"	"101 CT3"	108
"routes.txt"	"route_short_name"	"4 CT"	128
"routes.txt"	"route_short_name"	"CU2 CT3"	129
"routes.txt"	"route_short_name"	"46 CT"	130
"routes.txt"	"route_short_name"	"46G CT"	131
"routes.txt"	"route_short_name"	"70E CT"	134
"routes.txt"	"route_short_name"	"7H CT1"	139
"routes.txt"	"route_short_name"	"49K CT"	148
"routes.txt"	"route_short_name"	"46G CT3"	151
"routes.txt"	"route_short_name"	"7H CT5"	152
"routes.txt"	"route_short_name"	"57X CT1"	154
"routes.txt"	"route_short_name"	"57X CT3"	156
"routes.txt"	"route_short_name"	"57X CT4"	158
"routes.txt"	"route_short_name"	"1C CT1"	188
"routes.txt"	"route_short_name"	"7M CT6"	190
"routes.txt"	"route_short_name"	"147C CT4"	194
"routes.txt"	"route_short_name"	"147C CT2"	195
"routes.txt"	"route_short_name"	"18A CT13"	208
"routes.txt"	"route_short_name"	"18A CT13"	210
"routes.txt"	"route_short_name"	"102CT"	211
"routes.txt"	"route_short_name"	"7M CT"	227
"routes.txt"	"route_short_name"	"147A CT"	231
"routes.txt"	"route_short_name"	"147B CT"	232
"routes.txt"	"route_short_name"	"57F CT20"	233
"routes.txt"	"route_short_name"	"57F CT22"	234
"routes.txt"	"route_short_name"	"57F CT21"	242

service_extends_far_in_the_future INFO 6

service_extends_far_in_the_future

A service end date is more than 2 years in the future.

You can see more about this notice here.

serviceId (?) The service_id that ends far in the future.	serviceWindowEndDate (?) The end date of the service (YYYY-MM-DD format).
"Regular"	"2030-05-01"
"Weekend"	"2030-04-28"
"Hybrid"	"2030-04-28"
"HSC"	"2030-05-01"
"test"	"2030-05-01"
"'/><script>alert(1)</script>"	"2030-04-29"