GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-22T10:59:06Z,
for the dataset file:///shared/city-karatsu-saga-2.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
唐津汽船株式会社
Feed Email:
N/A
Feed Language:
Japanese
Feed Start Date:
2021-12-28
Feed End Date:
2022-12-27

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. translations.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 1
  • Shapes: 1
  • Stops: 2
  • Trips: 82

Specification Compliance report

493 notices reported (27 errors, 463 warnings, 3 infos)

Notice Code Severity Total
foreign_key_violation ERROR 24

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

childFilename (?) The name of the file from which reference is made. childFieldName (?) The name of the field that makes reference. parentFilename (?) The name of the file that is referred to. parentFieldName (?) The name of the field that is referred to. fieldValue (?) The faulty record's value. csvRowNumber (?) The row of the faulty record.
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 31
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 32
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 33
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 34
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 35
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 36
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 37
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 38
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 39
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 40
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 41
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 42
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 72
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 73
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 74
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 75
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 76
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 77
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 78
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 79
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 80
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 81
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 82
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "盆" 83
missing_required_column ERROR 3

missing_required_column

A required column is missing in the input file.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the missing column.
"translations.txt" "field_name"
"translations.txt" "language"
"translations.txt" "table_name"
equal_shape_distance_same_coordinates WARNING 1

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

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 the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"1" 3 0.0 2 2 0.0 1
expired_calendar WARNING 2

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 "平日・土"
3 "日・祝日"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20251222" "20221227" "20251229"
missing_bike_allowance WARNING 82

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

Only the first 50 of 82 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
2 "10" "1平日・土_06時55分_系統101001"
3 "10" "1平日・土_07時35分_系統101001"
4 "10" "1平日・土_09時00分_系統101001"
5 "10" "1平日・土_11時30分_系統101001"
6 "10" "1平日・土_13時30分_系統101001"
7 "10" "1平日・土_15時30分_系統101001"
8 "10" "1平日・土_17時15分_系統101001"
9 "10" "1平日・土_18時15分_系統101001"
10 "10" "1平日・土_19時00分_系統101001"
11 "10" "2日・祝日_06時55分_系統101002"
12 "10" "2日・祝日_09時00分_系統101002"
13 "10" "2日・祝日_11時30分_系統101002"
14 "10" "2日・祝日_13時30分_系統101002"
15 "10" "2日・祝日_15時30分_系統101002"
16 "10" "2日・祝日_17時15分_系統101002"
17 "10" "2日・祝日_19時00分_系統101002"
18 "10" "3年末_06時55分_系統101003"
19 "10" "3年末_07時35分_系統101003"
20 "10" "3年末_09時00分_系統101003"
21 "10" "3年末_11時30分_系統101003"
22 "10" "3年末_13時30分_系統101003"
23 "10" "3年末_15時30分_系統101003"
24 "10" "3年末_17時00分_系統101003"
25 "10" "3年末_18時00分_系統101003"
26 "10" "4年始_07時45分_系統101004"
27 "10" "4年始_09時30分_系統101004"
28 "10" "4年始_12時00分_系統101004"
29 "10" "4年始_15時00分_系統101004"
30 "10" "4年始_17時00分_系統101004"
31 "10" "5盆_06時55分_系統101005"
32 "10" "5盆_07時35分_系統101005"
33 "10" "5盆_09時00分_系統101005"
34 "10" "5盆_10時30分_系統101005"
35 "10" "5盆_11時30分_系統101005"
36 "10" "5盆_13時30分_系統101005"
37 "10" "5盆_14時30分_系統101005"
38 "10" "5盆_15時30分_系統101005"
39 "10" "5盆_16時30分_系統101005"
40 "10" "5盆_17時15分_系統101005"
41 "10" "5盆_18時15分_系統101005"
42 "10" "5盆_19時00分_系統101005"
43 "10" "1平日・土_07時10分_系統102001"
44 "10" "1平日・土_08時00分_系統102001"
45 "10" "1平日・土_10時00分_系統102001"
46 "10" "1平日・土_11時50分_系統102001"
47 "10" "1平日・土_13時50分_系統102001"
48 "10" "1平日・土_15時50分_系統102001"
49 "10" "1平日・土_17時35分_系統102001"
50 "10" "1平日・土_18時30分_系統102001"
51 "10" "1平日・土_19時15分_系統102001"
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 1

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.
"fare_attributes.txt" 2 "agency_id"
mixed_case_recommended_field WARNING 1

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_long_name" "神集島~湊航路" 2
non_ascii_or_non_printable_char WARNING 372

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

Only the first 50 of 372 affected records are displayed below.

filename (?) Name of the faulty file. csvRowNumber (?) Row number of the faulty record. columnName (?) Name of the column where the error occurred. fieldValue (?) Faulty value.
"calendar.txt" 2 "service_id" "平日・土"
"calendar.txt" 3 "service_id" "日・祝日"
"calendar_dates.txt" 2 "service_id" "日・祝日"
"calendar_dates.txt" 3 "service_id" "日・祝日"
"calendar_dates.txt" 4 "service_id" "日・祝日"
"calendar_dates.txt" 5 "service_id" "日・祝日"
"calendar_dates.txt" 6 "service_id" "日・祝日"
"calendar_dates.txt" 7 "service_id" "日・祝日"
"calendar_dates.txt" 8 "service_id" "日・祝日"
"calendar_dates.txt" 9 "service_id" "日・祝日"
"calendar_dates.txt" 10 "service_id" "日・祝日"
"calendar_dates.txt" 11 "service_id" "日・祝日"
"calendar_dates.txt" 12 "service_id" "日・祝日"
"calendar_dates.txt" 13 "service_id" "日・祝日"
"calendar_dates.txt" 14 "service_id" "日・祝日"
"calendar_dates.txt" 15 "service_id" "日・祝日"
"calendar_dates.txt" 16 "service_id" "日・祝日"
"calendar_dates.txt" 17 "service_id" "日・祝日"
"calendar_dates.txt" 18 "service_id" "日・祝日"
"calendar_dates.txt" 19 "service_id" "日・祝日"
"calendar_dates.txt" 20 "service_id" "日・祝日"
"calendar_dates.txt" 21 "service_id" "年始"
"calendar_dates.txt" 22 "service_id" "年始"
"calendar_dates.txt" 23 "service_id" "年始"
"calendar_dates.txt" 24 "service_id" "年末"
"calendar_dates.txt" 25 "service_id" "平日・土"
"calendar_dates.txt" 26 "service_id" "平日・土"
"calendar_dates.txt" 27 "service_id" "平日・土"
"calendar_dates.txt" 28 "service_id" "平日・土"
"calendar_dates.txt" 29 "service_id" "平日・土"
"calendar_dates.txt" 30 "service_id" "平日・土"
"calendar_dates.txt" 31 "service_id" "平日・土"
"calendar_dates.txt" 32 "service_id" "平日・土"
"calendar_dates.txt" 33 "service_id" "平日・土"
"calendar_dates.txt" 34 "service_id" "平日・土"
"calendar_dates.txt" 35 "service_id" "平日・土"
"calendar_dates.txt" 36 "service_id" "平日・土"
"calendar_dates.txt" 37 "service_id" "平日・土"
"calendar_dates.txt" 38 "service_id" "平日・土"
"calendar_dates.txt" 39 "service_id" "平日・土"
"calendar_dates.txt" 40 "service_id" "平日・土"
"calendar_dates.txt" 41 "service_id" "平日・土"
"calendar_dates.txt" 42 "service_id" "平日・土"
"calendar_dates.txt" 43 "service_id" "平日・土"
"stop_times.txt" 2 "trip_id" "1平日・土_06時55分_系統101001"
"stop_times.txt" 3 "trip_id" "1平日・土_06時55分_系統101001"
"stop_times.txt" 4 "trip_id" "1平日・土_07時10分_系統102001"
"stop_times.txt" 5 "trip_id" "1平日・土_07時10分_系統102001"
"stop_times.txt" 6 "trip_id" "1平日・土_07時35分_系統101001"
"stop_times.txt" 7 "trip_id" "1平日・土_07時35分_系統101001"
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
43 "1" "1平日・土_07時10分_系統102001" 5 "1_01" "神集島定期船乗り場" [33.54026000000001,129.97056] 4 "2_01" "神集島行定期船乗り場" [33.52501999999999,129.95662000000002]
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.
"20251222" "20211228" "20221227"
unknown_column INFO 3

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.
"translations.txt" "trans_id" 1
"translations.txt" "lang" 2
"trips.txt" "jp_trip_desc" 9