GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-13T11:38:07Z,
for the dataset file:///shared/nishitokyobus-ntbus.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:
2025-09-29
Feed End Date:
2025-12-31

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. office_jp.txt
  8. pattern_jp.txt
  9. routes.txt
  10. shapes.txt
  11. stop_times.txt
  12. stops.txt
  13. translations.txt
  14. trips.txt

Counts

  • Agencies: 5
  • Blocks: 0
  • Routes: 180
  • Shapes: 0
  • Stops: 2910
  • Trips: 8991

Specification Compliance report

9269 notices reported (0 errors, 9261 warnings, 8 infos)

Notice Code Severity Total
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.
12 "O_0004_2"
15 "O_0005_2"
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

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 "20251213" "20251231" "20260112"
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
mixed_case_recommended_field WARNING 9255

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.

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

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"agency.txt" "agency_name" "八王子市（はちバス）" 3
"agency.txt" "agency_name" "羽村市（はむらん）" 4
"agency.txt" "agency_name" "あきる野市（るのバス）" 5
"agency.txt" "agency_name" "日の出町（ぐるりーんひのでちゃん）" 6
"stops.txt" "stop_name" "千人町１丁目" 49
"stops.txt" "stop_name" "霊園前・八王子城跡入口" 56
"stops.txt" "stop_name" "元八２丁目" 61
"stops.txt" "stop_name" "元八２丁目北" 62
"stops.txt" "stop_name" "元八１丁目" 73
"stops.txt" "stop_name" "丹木１丁目" 102
"stops.txt" "stop_name" "丹木２丁目" 103
"stops.txt" "stop_name" "宮下・杏林大学入口" 110
"stops.txt" "stop_name" "栄町５丁目" 154
"stops.txt" "stop_name" "栄町５丁目北" 156
"stops.txt" "stop_name" "栄町４丁目" 178
"stops.txt" "stop_name" "小沢（檜原森のおもちゃ美術館）" 208
"stops.txt" "stop_name" "夏地（ひのはらファクトリー）" 210
"stops.txt" "stop_name" "大和田７丁目" 287
"stops.txt" "stop_name" "横山町３丁目" 343
"stops.txt" "stop_name" "秋川３丁目" 352
"stops.txt" "stop_name" "八日町１丁目" 354
"stops.txt" "stop_name" "多摩聖地霊園前（萓窪）" 362
"stops.txt" "stop_name" "八日町４丁目" 365
"stops.txt" "stop_name" "栄町２丁目" 401
"stops.txt" "stop_name" "末広町１丁目" 405
"stops.txt" "stop_name" "今井３丁目" 416
"stops.txt" "stop_name" "新町４丁目" 429
"stops.txt" "stop_name" "野上町３丁目" 449
"stops.txt" "stop_name" "東青梅４丁目" 458
"stops.txt" "stop_name" "長渕１丁目" 468
"stops.txt" "stop_name" "元本郷１丁目" 472
"stops.txt" "stop_name" "長渕４丁目" 474
"stops.txt" "stop_name" "千ヶ瀬２丁目" 475
"stops.txt" "stop_name" "小河内神社・麦山浮橋" 574
"stops.txt" "stop_name" "秋川４丁目" 627
"stops.txt" "stop_name" "暁町１丁目" 644
"stops.txt" "stop_name" "中野上町郵便局（高尾ポテト前）" 646
"stops.txt" "stop_name" "西中野２丁目" 648
"stops.txt" "stop_name" "西中野３丁目" 649
"stops.txt" "stop_name" "中央公民館・秋川体育館" 672
"stops.txt" "stop_name" "小川東１丁目" 681
"stops.txt" "stop_name" "元横山２丁目" 692
"stops.txt" "stop_name" "中野上町５丁目" 713
"stops.txt" "stop_name" "清川１号公園" 730
"stops.txt" "stop_name" "都営長沼１２号棟前" 754
"stops.txt" "stop_name" "都営長沼１４号棟前" 755
"stops.txt" "stop_name" "初沢会館・大光寺" 787
"stops.txt" "stop_name" "栄町１丁目" 838
"stops.txt" "stop_name" "図書館・ゆとろぎ" 859
"stops.txt" "stop_name" "日吉町１丁目会館" 867
route_long_name_contains_short_name WARNING 1

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"10086" 88 "市街地循環" "市街地循環"
route_short_name_too_long WARNING 1

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`.
"10094" 96 "急行（秋川駅-ｻﾏｰﾗﾝﾄﾞ)"
unknown_column INFO 6

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
"trips.txt" "jp_pattern_id" 14
"shapes.txt" "shape_dist_traveleded" 5
unknown_file INFO 2

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"pattern_jp.txt"
"office_jp.txt"