Search
  1. Home
  2. United States Feeds
  3. wichita-transit2
  4. Source Data Validation Report

wichita-transit2 — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-27T16:15:34Z,
for the dataset file:///shared/wichita-transit2_ecdd6aff.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar_dates.txt
  3. routes.txt
  4. shapes.txt
  5. stop_times.txt
  6. stops.txt
  7. transfers.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 14
  • Routes: 18
  • Shapes: 35
  • Stops: 265
  • Trips: 324

Specification Compliance report

42 notices reported (0 errors, 42 warnings, 0 infos)

Notice Code Severity Total
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 2

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`. actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"7c19b8ba-121a-4bab-90a0-714d434d00d2" 1680 8155.07 131 2892 8155.07 130 0.013605960439271812
"faf10f6a-0a31-43f6-bccb-747c1120d343" 2644 8157.87 129 367 8157.87 128 0.013605960439271812
expired_calendar WARNING 4

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "a30864ae-9a56-4c04-b630-2ca946ecd033"
3 "f4a41d1f-829b-4f66-bd23-014a730db27f"
4 "20aae444-0f4b-4701-bb88-79fec769e6a0"
5 "df572acc-52bc-4755-b6e1-642aa6b4a475"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 18

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.

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_desc" "PM COMMUTER WEEKDAY" 2
"routes.txt" "route_desc" "PINK WEEKDAY" 3
"routes.txt" "route_desc" "GREY WEEKDAY" 4
"routes.txt" "route_desc" "PURPLE SATURDAY" 5
"routes.txt" "route_desc" "BROWN LAST RUN MON-SAT" 6
"routes.txt" "route_desc" "ORANGE-GREY SATURDAY" 7
"routes.txt" "route_desc" "EXPRESS MON-SAT" 8
"routes.txt" "route_desc" "PINK-BLUE SATURDAY" 9
"routes.txt" "route_desc" "BROWN SATURDAY" 10
"routes.txt" "route_desc" "PURPLE WEEKDAY" 11
"routes.txt" "route_desc" "AM COMMUTER EAST WEEKDAY" 12
"routes.txt" "route_desc" "ORANGE WEEKDAY" 13
"routes.txt" "route_desc" "BROWN WEEKDAY" 14
"routes.txt" "route_desc" "PURPLE LAST RUN MON-SAT" 15
"routes.txt" "route_desc" "GREEN SATURDAY" 16
"routes.txt" "route_desc" "AM COMMUTER WEST WEEKDAY" 17
"routes.txt" "route_desc" "GREEN WEEKDAY" 18
"routes.txt" "route_desc" "BLUE WEEKDAY" 19
same_name_and_description_for_route WARNING 16

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

Description of a route that provides useful, quality information. Do not simply duplicate the name of the route.

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. routeId (?) The id of the faulty record. routeDesc (?) The `routes.routes_desc` of the faulty record. specifiedField (?) Either `route_short_name` or `route_long_name`.
2 "a064e068-d653-40a3-9ab7-4c011ac64929" "PM COMMUTER WEEKDAY" "route_long_name"
3 "6828df4b-1c96-4c69-9f23-d58fd83dd90f" "PINK WEEKDAY" "route_long_name"
4 "eeb6c1ce-e27a-440a-9657-68eb916e528d" "GREY WEEKDAY" "route_long_name"
5 "7058d0a7-d36d-4fd6-9db9-4a4d22419246" "PURPLE SATURDAY" "route_long_name"
6 "6f2a2057-fcc1-4a0d-85a4-1e83fb92bdff" "BROWN LAST RUN MON-SAT" "route_long_name"
7 "c1babebd-2171-4009-b609-c36f4fd1fc04" "ORANGE-GREY SATURDAY" "route_long_name"
8 "5a434a59-2e94-441b-9a6f-9ed0695fddfb" "EXPRESS MON-SAT" "route_long_name"
9 "1320019c-c022-42f3-9d04-d268d4d6872e" "PINK-BLUE SATURDAY" "route_long_name"
10 "9955fe97-4b41-4aa6-b012-d6d5c915f730" "BROWN SATURDAY" "route_long_name"
11 "fe09c3a7-5f18-4462-bf53-8ce8e0aba35a" "PURPLE WEEKDAY" "route_long_name"
13 "af513baa-d319-44e1-bec2-a8bd0d77d578" "ORANGE WEEKDAY" "route_long_name"
14 "7e814dbd-d3ac-4707-8fbc-4ed0cbe2f287" "BROWN WEEKDAY" "route_long_name"
15 "ac3a1314-331b-4406-8f79-840ab049132d" "PURPLE LAST RUN MON-SAT" "route_long_name"
16 "faeef8c9-dca8-4154-a20b-9bbecfe09bcc" "GREEN SATURDAY" "route_long_name"
18 "8d031fb7-d859-4e77-a371-7248b3c938c6" "GREEN WEEKDAY" "route_long_name"
19 "2ee9070a-496e-4850-9c58-d3c2e878075f" "BLUE WEEKDAY" "route_long_name"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260327" "20240830" "20250123"