daiichi-marine-service — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-17T09:04:07Z,
for the dataset file:///shared/daiichi-marine-service_8c7a0817.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
特定非営利活動法人OTTOP
Publisher URL:
https://ottop.org
Feed Email:
transit@ottop.org
Feed Language:
Japanese
Feed Start Date:
2026-03-19
Feed End Date:
2027-03-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. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 4
  • Shapes: 4
  • Stops: 3
  • Trips: 4

Specification Compliance report

216 notices reported (0 errors, 211 warnings, 5 infos)

Notice Code Severity Total
expired_calendar WARNING 1

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 "夏期1"
missing_bike_allowance WARNING 4

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.

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
2 "495" "5a0513973ae2acbb52ee21c398e9460d"
3 "496" "23aa34a518ae2ed6df803be688bca5fb"
4 "640" "84b3ef2c87532ed8ba3c236fb6da7d3d"
5 "641" "b194c8e6ef5191fa3b25a3bbfd6e24fb"
missing_recommended_field WARNING 9

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_version"
"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"
mixed_case_recommended_field WARNING 10

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_short_name" "ジンベエ・マリン" 2
"routes.txt" "route_long_name" "那覇・泊ふ頭→本部・渡久地港" 2
"routes.txt" "route_short_name" "ジンベエ・マリン" 3
"routes.txt" "route_long_name" "本部・渡久地港→那覇・泊ふ頭" 3
"routes.txt" "route_short_name" "ジンベエ・マリン" 4
"routes.txt" "route_long_name" "那覇・泊ふ頭→名護・名護漁港→本部・渡久地港" 4
"routes.txt" "route_short_name" "ジンベエ・マリン" 5
"routes.txt" "route_long_name" "本部・渡久地港→名護・名護漁港→那覇・泊ふ頭" 5
"stops.txt" "stop_name" "タクマ3乗船券販売所" 2
"stops.txt" "stop_name" "名護市観光情報センター(タクマ3乗船券販売所)" 4
non_ascii_or_non_printable_char WARNING 186

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 186 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_dates.txt" 2 "service_id" "夏期1"
"calendar_dates.txt" 3 "service_id" "夏期1"
"calendar_dates.txt" 4 "service_id" "夏期1"
"calendar_dates.txt" 5 "service_id" "夏期1"
"calendar_dates.txt" 6 "service_id" "夏期1"
"calendar_dates.txt" 7 "service_id" "夏期1"
"calendar_dates.txt" 8 "service_id" "夏期1"
"calendar_dates.txt" 9 "service_id" "夏期1"
"calendar_dates.txt" 10 "service_id" "夏期1"
"calendar_dates.txt" 11 "service_id" "夏期1"
"calendar_dates.txt" 12 "service_id" "夏期1"
"calendar_dates.txt" 13 "service_id" "夏期1"
"calendar_dates.txt" 14 "service_id" "夏期1"
"calendar_dates.txt" 15 "service_id" "夏期1"
"calendar_dates.txt" 16 "service_id" "夏期1"
"calendar_dates.txt" 17 "service_id" "夏期1"
"calendar_dates.txt" 18 "service_id" "夏期1"
"calendar_dates.txt" 19 "service_id" "夏期1"
"calendar_dates.txt" 20 "service_id" "夏期1"
"calendar_dates.txt" 21 "service_id" "夏期1"
"calendar_dates.txt" 22 "service_id" "夏期1"
"calendar_dates.txt" 23 "service_id" "夏期1"
"calendar_dates.txt" 24 "service_id" "夏期1"
"calendar_dates.txt" 25 "service_id" "夏期1"
"calendar_dates.txt" 26 "service_id" "夏期1"
"calendar_dates.txt" 27 "service_id" "夏期1"
"calendar_dates.txt" 28 "service_id" "夏期1"
"calendar_dates.txt" 29 "service_id" "夏期1"
"calendar_dates.txt" 30 "service_id" "夏期1"
"calendar_dates.txt" 31 "service_id" "夏期1"
"calendar_dates.txt" 32 "service_id" "夏期1"
"calendar_dates.txt" 33 "service_id" "夏期1"
"calendar_dates.txt" 34 "service_id" "夏期1"
"calendar_dates.txt" 35 "service_id" "夏期1"
"calendar_dates.txt" 36 "service_id" "夏期1"
"calendar_dates.txt" 37 "service_id" "夏期1"
"calendar_dates.txt" 38 "service_id" "夏期1"
"calendar_dates.txt" 39 "service_id" "夏期1"
"calendar_dates.txt" 40 "service_id" "夏期1"
"calendar_dates.txt" 41 "service_id" "夏期1"
"calendar_dates.txt" 42 "service_id" "夏期1"
"calendar_dates.txt" 43 "service_id" "夏期1"
"calendar_dates.txt" 44 "service_id" "夏期1"
"calendar_dates.txt" 45 "service_id" "夏期1"
"calendar_dates.txt" 46 "service_id" "夏期1"
"calendar_dates.txt" 47 "service_id" "夏期1"
"calendar_dates.txt" 48 "service_id" "夏期1"
"calendar_dates.txt" 49 "service_id" "夏期1"
"calendar_dates.txt" 50 "service_id" "夏期1"
"calendar_dates.txt" 51 "service_id" "夏期1"
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.
"20260717" "20220701" "20260215"
big_gap_in_service INFO 3

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.
"夏期1" "2023-03-14" "2023-04-14" 30
"夏期1" "2024-03-12" "2024-05-01" 49
"夏期1" "2025-03-10" "2025-04-26" 46
feed_valid_beyond_total_service_window INFO 1

feed_valid_beyond_total_service_window

The feed is valid 14 days beyond its total service window.

You can see more about this notice here.

feedStartDate (?) The feed start date from feed_info.txt. feedEndDate (?) The feed end date from feed_info.txt. serviceWindowStartDate (?) The earliest active service date across all services. serviceWindowEndDate (?) The latest active service date across all services.
"2026-03-19" "2027-03-31" "2022-07-01" "2026-02-15"
service_window_outside_feed_period INFO 1

service_window_outside_feed_period

A service window is not covered by the feed's validity period.

You can see more about this notice here.

serviceId (?) The service_id whose active window extends outside the feed validity period. serviceWindowStartDate (?) The first active date of the service window. serviceWindowEndDate (?) The last active date of the service window. daysBeforeFeedStart (?) Number of days the service window extends before feed_start_date (0 if none). daysAfterFeedEnd (?) Number of days the service window extends after feed_end_date (0 if none).
"夏期1" "2022-07-01" "2026-02-15" 1357 0