Warnings:

Invalid Value

• Invalid value rietavas-medingėnai 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 "1600_247196" and "1600_247197".
  
  
• Invalid value medingėnai-rietavas 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 "1601_247202" and "1601_247201".
  
  

No Service Exceptions

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

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