FeedValidator:

GTFS validation results for feed:
hydMMTSv3/
FeedValidator extension used: None

Agencies:	Hyderabad Multi-Modal Transport System
Routes:	38
Stops:	82
Trips:	173
Shapes:	0
Effective:	January 01, 2019 to January 01, 2020

During the upcoming service dates Sun Apr 21 to Wed Jun 19:

Average trips per date:	163
Most trips on a date:	173, on 27 service dates (Mon Apr 22, Tue Apr 23, Wed Apr 24, ...)
Least trips on a date:	147, on 9 service dates (Sun Apr 21, Sun Apr 28, Sun May 05, ...)

Found these problems:

17 warnings

1	No Service Exceptions
1	Stops Too Close
1	Too Fast Travel
14	Unrecognized Columns

Warnings:

No Service Exceptions

All services are defined on a weekly basis from 2019-01-01 to 2020-01-01 with no single day variations. If there are exceptions such as holiday service dates please ensure they are listed in calendar_dates.txt

Stops Too Close

The stops "SITAFALMANDI B" (ID STDB) and "SITAFAL MANDI" (ID STPD) are 0.00m apart and probably represent the same location.

Too Fast Travel

High speed travel detected in trip TR_77681: G POCHAMPALLI to GOWDAVALLI. 5121 meters in 60 seconds. (307 km/h).

Unrecognized Column

Unrecognized column IN_2S in file routes.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of routes.txt

route_id route_short_name route_long_name route_type IN_numstops IN_CC IN_2A IN_SL IN_3A IN_3E IN_FC IN_2S IN_1A IN_duration IN_distance IN_LL_Dist IN_speed
Unrecognized column IN_numstops in file routes.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of routes.txt

route_id route_short_name route_long_name route_type IN_numstops IN_CC IN_2A IN_SL IN_3A IN_3E IN_FC IN_2S IN_1A IN_duration IN_distance IN_LL_Dist IN_speed
Unrecognized column IN_distance in file routes.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of routes.txt

route_id route_short_name route_long_name route_type IN_numstops IN_CC IN_2A IN_SL IN_3A IN_3E IN_FC IN_2S IN_1A IN_duration IN_distance IN_LL_Dist IN_speed
Unrecognized column IN_LL_Dist in file routes.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of routes.txt

route_id route_short_name route_long_name route_type IN_numstops IN_CC IN_2A IN_SL IN_3A IN_3E IN_FC IN_2S IN_1A IN_duration IN_distance IN_LL_Dist IN_speed
Unrecognized column IN_CC in file routes.txt. This might be a misspelled column name (capitalization matters!). Or it could be extra information (such as a proposed feed extension) that the validator doesn't know about yet. Extra information is fine; this warning is here to catch misspelled optional column names.
in line 1 of routes.txt

route_id route_short_name route_long_name route_type IN_numstops IN_CC IN_2A IN_SL IN_3A IN_3E IN_FC IN_2S IN_1A IN_duration IN_distance IN_LL_Dist IN_speed
and 9 more of this type.