FeedValidator: lt.hb.vintra.integr.common.GtfsValidatorTasklet_unzip

GTFS validation results for feed:

c:\app_server\vintra_integr_base\temp\lt.hb.vintra.integr.common.GtfsValidatorTasklet_unzip_15383414976776699464869372259325

FeedValidator extension used: None

Agencies:	Radviliškio r. sav.
Routes:	26
Stops:	197
Trips:	80
Shapes:	58
Effective:	January 01, 2015 to October 13, 2019

During the upcoming service dates Mon Oct 01 to Thu Nov 29:

Average trips per date:	48
Most trips on a date:	74, on 9 service dates (Thu Oct 04, Thu Oct 11, Thu Oct 18, ...)
Least trips on a date:	2, on 8 service dates (Sun Oct 07, Sun Oct 14, Sun Oct 21, ...)

Found these problems:

42 warnings

3	Invalid Values
2	Stops Too Closes
18	Too Fast Travels
9	Too Many Days Without Services
10	Unrecognized Columns

Warnings:

Invalid Value

Invalid value radviliškis - šiluva per šiaulėnus, ropkepius in field route_long_name
The same combination of route_short_name and route_long_name shouldn't be used for more than one route, as it is for the for the two routes with IDs "2658_55975" and "2658_55971".
Invalid value baisogala - radviliškis per pakiršinį in field route_long_name
The same combination of route_short_name and route_long_name shouldn't be used for more than one route, as it is for the for the two routes with IDs "2648" and "2648_55976".
Invalid value radviliškis - miežaičiai per ilguočius in field route_long_name
The same combination of route_short_name and route_long_name shouldn't be used for more than one route, as it is for the for the two routes with IDs "2421_754930" and "2421".

Stops Too Close

The stops "Baisogala" (ID 7749) and "Baisogala" (ID 9632) are 0.00m apart and probably represent the same location.
The stops "RSO-2" (ID 11818) and "RSO-2" (ID 14925) are 0.00m apart and probably represent the same location.

Too Fast Travel

High speed travel detected in trip 2778803: Kurkliai to Šeduvos a.st.. 5012 meters in 180 seconds. (100 km/h).
High speed travel detected in trip 56292: Januškoniai to Baisogala. 3941 meters in 120 seconds. (118 km/h).
High speed travel detected in trip 1042523: Žinėnai to Daugėlaičiai. 3904 meters in 120 seconds. (117 km/h).
High speed travel detected in trip 1042524: Daugėlaičiai to Žinėnai. 3904 meters in 120 seconds. (117 km/h).
High speed travel detected in trip 56021: Rudžiai to Dotiškiai. 3730 meters in 120 seconds. (112 km/h).
High speed travel detected in trip 55772: Girvalakiai to Jadvimpolis. 3285 meters in 60 seconds. (197 km/h).
High speed travel detected in trip 55958: Kutiškiai to Durpynas. 2954 meters in 60 seconds. (177 km/h).
High speed travel detected in trip 55958: Susivienijimas to Ilguočiai. 2652 meters in 60 seconds. (159 km/h).
High speed travel detected in trip 56143: Durpynas to Kutiškiai. 2566 meters in 60 seconds. (154 km/h).
High speed travel detected in trip 965701: Acokavai to Liepiškiai. 2483 meters in 60 seconds. (149 km/h).
High speed travel detected in trip 55750: Baltoji to Žilioniai. 2331 meters in 60 seconds. (140 km/h).
High speed travel detected in trip 56013: Dauderiai to Kubiliūnai. 2323 meters in 60 seconds. (139 km/h).
High speed travel detected in trip 782729: Šeduvos PŪ to Mokykla. 2099 meters in 60 seconds. (126 km/h).
High speed travel detected in trip 55958: Durpynas to Centras. 2051 meters in 60 seconds. (123 km/h).
High speed travel detected in trip 55750: RSO-2 to Baltoji. 2018 meters in 60 seconds. (121 km/h).
High speed travel detected in trip 55976: Karčemos to Susivienijimas. 1980 meters in 60 seconds. (119 km/h).
High speed travel detected in trip 55893: Karčemos to Susivienijimas. 1980 meters in 60 seconds. (119 km/h).
High speed travel detected in trip 754931: Karčiamų k to Ilguočiai. 1929 meters in 60 seconds. (116 km/h).

Too Many Days Without Service

There are 30 consecutive days, from 2019-01-14 to 2019-02-12, without any scheduled service. Please ensure this is intentional.
There are 27 consecutive days, from 2019-02-14 to 2019-03-12, without any scheduled service. Please ensure this is intentional.
There are 30 consecutive days, from 2019-03-14 to 2019-04-12, without any scheduled service. Please ensure this is intentional.
There are 29 consecutive days, from 2019-04-14 to 2019-05-12, without any scheduled service. Please ensure this is intentional.
There are 30 consecutive days, from 2019-05-14 to 2019-06-12, without any scheduled service. Please ensure this is intentional.
There are 29 consecutive days, from 2019-06-14 to 2019-07-12, without any scheduled service. Please ensure this is intentional.
There are 30 consecutive days, from 2019-07-14 to 2019-08-12, without any scheduled service. Please ensure this is intentional.
There are 30 consecutive days, from 2019-08-14 to 2019-09-12, without any scheduled service. Please ensure this is intentional.
There are 17 consecutive days, from 2019-09-14 to 2019-09-30, without any scheduled service. Please ensure this is intentional.

Unrecognized Column

Unrecognized column stop_direction in file stops.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 stops.txt

stop_id stop_name stop_lat stop_lon stop_code stop_desc zone_id stop_url location_type parent_station wheelchair_boarding stop_direction stop_timezone vehicle_type platform_code
Unrecognized column vehicle_type in file stops.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 stops.txt

stop_id stop_name stop_lat stop_lon stop_code stop_desc zone_id stop_url location_type parent_station wheelchair_boarding stop_direction stop_timezone vehicle_type platform_code
Unrecognized column platform_code in file stops.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 stops.txt

stop_id stop_name stop_lat stop_lon stop_code stop_desc zone_id stop_url location_type parent_station wheelchair_boarding stop_direction stop_timezone vehicle_type platform_code
Unrecognized column route_bikes_allowed 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

agency_id route_id route_short_name route_long_name route_type route_desc route_url route_color route_text_color route_bikes_allowed bikes_allowed route_sort_order
Unrecognized column route_sort_order 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

agency_id route_id route_short_name route_long_name route_type route_desc route_url route_color route_text_color route_bikes_allowed bikes_allowed route_sort_order
Unrecognized column route_short_name in file trips.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 trips.txt

route_id trip_id service_id trip_short_name trip_headsign route_short_name direction_id block_id shape_id wheelchair_accessible trip_bikes_allowed bikes_allowed
Unrecognized column trip_bikes_allowed in file trips.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 trips.txt

route_id trip_id service_id trip_short_name trip_headsign route_short_name direction_id block_id shape_id wheelchair_accessible trip_bikes_allowed bikes_allowed
Unrecognized column journey_duration in file fare_attributes.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 fare_attributes.txt

agency_id fare_id price currency_type payment_method transfers transfer_duration journey_duration
Unrecognized column agency_id in file fare_attributes.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 fare_attributes.txt

agency_id fare_id price currency_type payment_method transfers transfer_duration journey_duration
Unrecognized column route_short_name in file stop_times.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 stop_times.txt

trip_id stop_id arrival_time departure_time timepoint stop_sequence stop_headsign route_short_name pickup_type drop_off_type shape_dist_traveled