Warnings:

Future Service

• The feed_start_date in feed_info.txt in this feed is in the future, on March 17, 2025. Published feeds must always include the current date.
  
  

Invalid Value

• Invalid value FFA5A5 in field route_color
  The route_text_color and route_color should be set to contrasting colors, as they are used as the text and background color (respectively) for displaying route names. When left blank, route_text_color defaults to 000000 (black) and route_color defaults to FFFFFF (white). A common source of issues here is setting route_color to a dark color, while leaving route_text_color set to black. In this case, route_text_color should be set to a lighter color like FFFFFF to ensure a legible contrast between the two.
  in line 7 of routes.txt
  

  route_id	agency_id	route_short_name	route_long_name	route_desc	route_type	route_url	route_color	route_text_color	route_sort_order
  6	0	6	Parchment		3		FFA5A5	FFFFFF	6

  
  
• Invalid value A5FAFA in field route_color
  The route_text_color and route_color should be set to contrasting colors, as they are used as the text and background color (respectively) for displaying route names. When left blank, route_text_color defaults to 000000 (black) and route_color defaults to FFFFFF (white). A common source of issues here is setting route_color to a dark color, while leaving route_text_color set to black. In this case, route_text_color should be set to a lighter color like FFFFFF to ensure a legible contrast between the two.
  in line 10 of routes.txt
  

  route_id	agency_id	route_short_name	route_long_name	route_desc	route_type	route_url	route_color	route_text_color	route_sort_order
  9	0	9	Gull Road		3		A5FAFA	FFFFFF	9

  
  
• Invalid value A6FFA5 in field route_color
  The route_text_color and route_color should be set to contrasting colors, as they are used as the text and background color (respectively) for displaying route names. When left blank, route_text_color defaults to 000000 (black) and route_color defaults to FFFFFF (white). A common source of issues here is setting route_color to a dark color, while leaving route_text_color set to black. In this case, route_text_color should be set to a lighter color like FFFFFF to ensure a legible contrast between the two.
  in line 12 of routes.txt
  

  route_id	agency_id	route_short_name	route_long_name	route_desc	route_type	route_url	route_color	route_text_color	route_sort_order
  11	0	11	Stadium/KVCC		3		A6FFA5	FFFFFF	11

  
  

Other Problem

• In stop_times.txt, the stop with trip_id=t6B3-b515-sl3 and stop_sequence=1260 has shape_dist_traveled=39428.435744, which is larger than the max shape_dist_traveled=37032.801578 of the corresponding shape (shape_id=6884_shp)
  
  
• In stop_times.txt, the stop with trip_id=t6B3-b515-sl9 and stop_sequence=1260 has shape_dist_traveled=39428.435744, which is larger than the max shape_dist_traveled=37032.801578 of the corresponding shape (shape_id=6883_shp)
  
  
• In stop_times.txt, the stop with trip_id=t587-b515-sl9 and stop_sequence=1260 has shape_dist_traveled=39428.435744, which is larger than the max shape_dist_traveled=37032.801578 of the corresponding shape (shape_id=6879_shp)
  
  
• In stop_times.txt, the stop with trip_id=t32F-b515-sl3 and stop_sequence=1260 has shape_dist_traveled=39428.435744, which is larger than the max shape_dist_traveled=37032.801578 of the corresponding shape (shape_id=6880_shp)
  
  
• In stop_times.txt, the stop with trip_id=t32F-b515-sl9 and stop_sequence=1260 has shape_dist_traveled=39428.435744, which is larger than the max shape_dist_traveled=37032.801578 of the corresponding shape (shape_id=6879_shp)
  
  
• and 17 more of this type.

Stop Too Far From Shape With Dist Traveled

• For trip t2CB-b4B1-sl3 the stop "Airport Rd & Portage" (ID 497) is 2268 meters away from the corresponding point (shape_dist_traveled: 51381.620690) on shape 8002_shp. It should be closer than 1000 meters.
  
  
• For trip t2CB-b4B1-sl9 the stop "Airport Rd & Portage" (ID 497) is 2268 meters away from the corresponding point (shape_dist_traveled: 51381.620690) on shape 8001_shp. It should be closer than 1000 meters.
  
  
• For trip t587-b4B2-sl9 the stop "Airport Rd & Portage" (ID 497) is 2268 meters away from the corresponding point (shape_dist_traveled: 51381.620690) on shape 8001_shp. It should be closer than 1000 meters.
  
  
• For trip t587-b4B2-sl3 the stop "Airport Rd & Portage" (ID 497) is 2268 meters away from the corresponding point (shape_dist_traveled: 51381.620690) on shape 8002_shp. It should be closer than 1000 meters.
  
  
• For trip t717-b4B2-sl9 the stop "Airport Rd & Portage" (ID 497) is 2268 meters away from the corresponding point (shape_dist_traveled: 51381.620690) on shape 8001_shp. It should be closer than 1000 meters.
  
  
• and 1397 more of this type.

Stops Too Close

• The stops "Westnedge at Montrose Ave (SW Corner)" (ID 14) and "Westnedge at Montrose" (ID 44) are 0.00m apart and probably represent the same location.
  
  

Unknown File

• The file named calendar_dates_sunrise.txt was not expected.
  This may be a misspelled file name or the file may be included in a subdirectory. Please check spellings and make sure that there are no subdirectories within the feed
  in calendar_dates_sunrise.txt
  
  
• The file named GTFS_Rosetta_Stone.csv was not expected.
  This may be a misspelled file name or the file may be included in a subdirectory. Please check spellings and make sure that there are no subdirectories within the feed
  in GTFS_Rosetta_Stone.csv
  
  
• The file named stop_times_schedule.txt was not expected.
  This may be a misspelled file name or the file may be included in a subdirectory. Please check spellings and make sure that there are no subdirectories within the feed
  in stop_times_schedule.txt
  
  
• The file named validation-results.html was not expected.
  This may be a misspelled file name or the file may be included in a subdirectory. Please check spellings and make sure that there are no subdirectories within the feed
  in validation-results.html
  
  

Unrecognized Column

• Unrecognized column agency_email in file agency.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 agency.txt
  

  agency_id	agency_name	agency_url	agency_timezone	agency_lang	agency_phone	agency_fare_url	agency_email

  
  
• 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
  

  route_id	agency_id	route_short_name	route_long_name	route_desc	route_type	route_url	route_color	route_text_color	route_sort_order

  
  
• 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
  

  fare_id	price	currency_type	payment_method	transfers	agency_id	transfer_duration

  
  
• Unrecognized column feed_contact_email in file feed_info.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 feed_info.txt
  

  feed_publisher_name	feed_publisher_url	feed_lang	feed_start_date	feed_end_date	feed_version	feed_contact_email	feed_contact_url

  
  
• Unrecognized column feed_contact_url in file feed_info.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 feed_info.txt
  

  feed_publisher_name	feed_publisher_url	feed_lang	feed_start_date	feed_end_date	feed_version	feed_contact_email	feed_contact_url