GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T15:15:14Z,
for the dataset file:///shared/atsuma-bus.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
ジョルダン株式会社
Publisher URL:
https://www.jorudan.co.jp
Feed Email:
N/A
Feed Language:
Japanese
Feed Start Date:
2025-11-01
Feed End Date:
2026-04-30

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 8
  • Shapes: 0
  • Stops: 254
  • Trips: 48

Specification Compliance report

1582 notices reported (0 errors, 1572 warnings, 10 infos)

Notice Code Severity Total
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 107

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.

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

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"
"fare_attributes.txt" 3 "agency_id"
"fare_attributes.txt" 4 "agency_id"
"fare_attributes.txt" 5 "agency_id"
"fare_attributes.txt" 6 "agency_id"
"fare_attributes.txt" 7 "agency_id"
"fare_attributes.txt" 8 "agency_id"
"fare_attributes.txt" 9 "agency_id"
"fare_attributes.txt" 10 "agency_id"
"fare_attributes.txt" 11 "agency_id"
"fare_attributes.txt" 12 "agency_id"
"fare_attributes.txt" 13 "agency_id"
"fare_attributes.txt" 14 "agency_id"
"fare_attributes.txt" 15 "agency_id"
"fare_attributes.txt" 16 "agency_id"
"fare_attributes.txt" 17 "agency_id"
"fare_attributes.txt" 18 "agency_id"
"fare_attributes.txt" 19 "agency_id"
"fare_attributes.txt" 20 "agency_id"
"fare_attributes.txt" 21 "agency_id"
"fare_attributes.txt" 22 "agency_id"
"fare_attributes.txt" 23 "agency_id"
"fare_attributes.txt" 24 "agency_id"
"fare_attributes.txt" 25 "agency_id"
"fare_attributes.txt" 26 "agency_id"
"fare_attributes.txt" 27 "agency_id"
"fare_attributes.txt" 28 "agency_id"
"fare_attributes.txt" 29 "agency_id"
"fare_attributes.txt" 30 "agency_id"
"fare_attributes.txt" 31 "agency_id"
"fare_attributes.txt" 32 "agency_id"
"fare_attributes.txt" 33 "agency_id"
"fare_attributes.txt" 34 "agency_id"
"fare_attributes.txt" 35 "agency_id"
"fare_attributes.txt" 36 "agency_id"
"fare_attributes.txt" 37 "agency_id"
"fare_attributes.txt" 38 "agency_id"
"fare_attributes.txt" 39 "agency_id"
"fare_attributes.txt" 40 "agency_id"
"fare_attributes.txt" 41 "agency_id"
"fare_attributes.txt" 42 "agency_id"
"fare_attributes.txt" 43 "agency_id"
"fare_attributes.txt" 44 "agency_id"
"fare_attributes.txt" 45 "agency_id"
"fare_attributes.txt" 46 "agency_id"
"fare_attributes.txt" 47 "agency_id"
"fare_attributes.txt" 48 "agency_id"
"fare_attributes.txt" 49 "agency_id"
"fare_attributes.txt" 50 "agency_id"
"fare_attributes.txt" 51 "agency_id"
missing_timepoint_value WARNING 1449

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's `stop_times.trip_id`. stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2 "T0114000001" 0
3 "T0114000001" 1
4 "T0114000001" 2
5 "T0114000001" 3
6 "T0114000001" 4
7 "T0114000001" 5
8 "T0114000002" 0
9 "T0114000002" 1
10 "T0114000002" 2
11 "T0114000002" 3
12 "T0114000002" 4
13 "T0114000002" 5
14 "T0114000003" 0
15 "T0114000003" 1
16 "T0114000003" 2
17 "T0114000003" 3
18 "T0114000003" 4
19 "T0114000003" 5
20 "T0114000004" 0
21 "T0114000004" 1
22 "T0114000004" 2
23 "T0114000004" 3
24 "T0114000004" 4
25 "T0114000004" 5
26 "T0114000005" 0
27 "T0114000005" 1
28 "T0114000005" 2
29 "T0114000005" 3
30 "T0114000005" 4
31 "T0114000005" 5
32 "T0114000005" 6
33 "T0114000005" 7
34 "T0114000005" 8
35 "T0114000005" 9
36 "T0114000005" 10
37 "T0114000005" 11
38 "T0114000005" 12
39 "T0114000005" 13
40 "T0114000005" 14
41 "T0114000005" 15
42 "T0114000005" 16
43 "T0114000005" 17
44 "T0114000005" 18
45 "T0114000005" 19
46 "T0114000005" 20
47 "T0114000005" 21
48 "T0114000005" 22
49 "T0114000005" 23
50 "T0114000006" 0
51 "T0114000006" 1
mixed_case_recommended_field WARNING 15

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" "千歳線（あつま）" 4
"stops.txt" "stop_name" "朝日町７丁目" 79
"stops.txt" "stop_name" "朝日町７丁目" 80
"stops.txt" "stop_name" "朝日町４丁目" 81
"stops.txt" "stop_name" "朝日町４丁目" 82
"stops.txt" "stop_name" "新開４丁目" 137
"stops.txt" "stop_name" "新開４丁目" 138
"stops.txt" "stop_name" "木場町１丁目" 152
"stops.txt" "stop_name" "木場町１丁目" 153
"stops.txt" "stop_name" "明野元町１丁目" 186
"stops.txt" "stop_name" "明野元町１丁目" 187
"stops.txt" "stop_name" "北栄２丁目" 250
"stops.txt" "stop_name" "北栄２丁目" 251
"stops.txt" "stop_name" "ウトナイ南５丁目" 252
"stops.txt" "stop_name" "ウトナイ南５丁目" 253
platform_without_parent_station INFO 3

platform_without_parent_station

A platform has no parent_station field set.

This is different from location_without_parent_station since it is less severe.

You can see more about this notice here.

csvRowNumber (?) Row number of the faulty record. stopId (?) The id of the faulty record. stopName (?) The stop name of the faulty record.
74 "S011400004400100" "新千歳空港国内線２８番"
75 "S011400004500100" "新千歳空港国際線８５番"
76 "S011400004600100" "新千歳空港国内線１番"
unknown_column INFO 4

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" "jp_parent_route_id" 10
"trips.txt" "jp_trip_desc" 11
"trips.txt" "jp_trip_desc_symbol" 12
"trips.txt" "jp_office_id" 13
unknown_file INFO 3

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"agency_jp.txt"
"pass_attributes.txt"
"pass_rules.txt"