korail — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-10T12:40:26Z,
for the dataset file:///shared/korail_39d0723c.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Mikołaj Kuranowski
Feed Email:
N/A
Feed Language:
Korean

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. translations.txt
  10. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 10
  • Shapes: 643
  • Stops: 267
  • Trips: 888

Specification Compliance report

24 notices reported (0 errors, 22 warnings, 2 infos)

Notice Code Severity Total
fast_travel_between_consecutive_stops WARNING 4

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type Description Threshold, km/h
0 Light rail 100
1 Subway 150
2 Rail 500
3 Bus 150
4 Ferry 80
5 Cable tram 30
6 Aerial lift 50
7 Funicular 50
11 Trolleybus 150
12 Monorail 150
- Unknown 200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
130 "1242" "itx-maum" 1962.3432871605187 16.352860726337656 1825 2 "yesan" "예산" "06:16:30" 1826 3 "hongseong" "홍성" "06:17:00"
130 "1242" "itx-maum" 596.9841096718644 14.924602741796612 1830 7 "onyang_oncheon" "온양온천" "06:37:00" 1831 8 "sillyewon" "신례원" "06:38:30"
130 "1242" "itx-maum" 528.0235808970142 13.200589522425355 1833 10 "cheonan" "천안" "06:52:30" 1834 11 "onyang_oncheon" "온양온천" "06:54:00"
130 "1242" "itx-maum" 791.5156850166547 13.191928083610913 1837 14 "pyeongtaek" "평택" "07:28:00" 1838 15 "anjung" "안중" "07:28:00"
fast_travel_between_far_stops WARNING 1

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
130 "1242" "itx-maum" 1962.3432871605187 16.352860726337656 1825 2 "yesan" "예산" "06:16:30" 1826 3 "hongseong" "홍성" "06:17:00"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_recommended_field WARNING 3

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"feed_info.txt" 2 "feed_start_date"
"feed_info.txt" 2 "feed_end_date"
"feed_info.txt" 2 "feed_version"
mixed_case_recommended_field WARNING 13

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.
"stops.txt" "stop_name" "김천 (구미)" 71
"stops.txt" "stop_name" "진부 (오대산)" 139
"stops.txt" "stop_name" "판교 (경기)" 181
"routes.txt" "route_short_name" "ITX-청춘" 2
"routes.txt" "route_short_name" "ITX-마음" 3
"routes.txt" "route_short_name" "ITX-새마을" 4
"routes.txt" "route_short_name" "KTX-청룡" 6
"routes.txt" "route_short_name" "KTX-이음" 7
"routes.txt" "route_short_name" "KTX-산천" 8
"trips.txt" "trip_headsign" "판교 (경기)" 782
"trips.txt" "trip_headsign" "판교 (경기)" 784
"trips.txt" "trip_headsign" "판교 (경기)" 786
"trips.txt" "trip_headsign" "판교 (경기)" 788
big_gap_in_service INFO 1

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"16" "2026-12-18" "2027-01-08" 20
unknown_column INFO 1

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"routes.txt" "route_type_extended" 6