aganoshi — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-09-11T19:10:52Z,
for the dataset file:///shared/aganoshi_36da3970.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:
    2020-09-01
    Feed End Date:
    2021-02-28

    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. routes.txt
    9. routes_jp.txt
    10. stop_times.txt
    11. stops.txt
    12. translations.txt
    13. trips.txt

    Counts


    • Agencies: 0
    • Blocks: 0
    • Routes: 59
    • Shapes: 0
    • Stops: 649
    • Trips: 109

    Specification Compliance report

    199 notices reported (1 errors, 182 warnings, 16 infos)

    Notice Code Severity Total
    invalid_url ERROR 1

    invalid_url

    A field contains a malformed URL.

    Definitions for valid URLs are quite vague. We perform strict validation using the Apache Commons UrlValidator.

    You can see more about this notice here.

    filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
    "agency.txt" 2 "agency_url" "阿賀野市"
    duplicate_route_name WARNING 23

    duplicate_route_name

    Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

    All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

    Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

    Example of bad data:

    route_id route_short_name route_long_name
    route1 U1 Southern
    route2 U1 Southern

    You can see more about this notice here.

    csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
    11 "R10" 12 "R11" "" "駒林線:京和荘~市野山" 3 "9000020152234"
    14 "R13" 15 "R14" "" "五頭温泉郷線:温泉~市役所" 3 "9000020152234"
    14 "R13" 16 "R15" "" "五頭温泉郷線:温泉~市役所" 3 "9000020152234"
    17 "R16" 18 "R17" "" "五頭温泉郷線:笹岡小学校経由" 3 "9000020152234"
    19 "R18" 20 "R19" "" "五頭温泉郷線:水原駅経由" 3 "9000020152234"
    21 "R20" 22 "R21" "" "江端線" 3 "9000020152234"
    21 "R20" 23 "R22" "" "江端線" 3 "9000020152234"
    21 "R20" 24 "R23" "" "江端線" 3 "9000020152234"
    25 "R24" 26 "R25" "" "寺社線:サントピアワールド経由" 3 "9000020152234"
    27 "R26" 28 "R27" "" "寺社線:牧島経由" 3 "9000020152234"
    27 "R26" 29 "R28" "" "寺社線:牧島経由" 3 "9000020152234"
    34 "R33" 35 "R34" "" "神山線:天神堂経由" 3 "9000020152234"
    36 "R35" 37 "R36" "" "神山線:豆田経由" 3 "9000020152234"
    39 "R38" 40 "R39" "" "折居大日線:笹神支所~市役所" 3 "9000020152234"
    43 "R42" 44 "R43" "" "千唐仁線:すぎはら医院経由" 3 "9000020152234"
    45 "R44" 46 "R45" "" "千唐仁線:宝珠温泉~市役所" 3 "9000020152234"
    48 "R47" 49 "R48" "" "前山線:中潟センター前経由" 3 "9000020152234"
    50 "R49" 51 "R50" "" "大室線:新保~市役所" 3 "9000020152234"
    52 "R51" 53 "R52" "" "大室線:宝珠温泉~市役所" 3 "9000020152234"
    55 "R54" 56 "R55" "" "分田線:市民病院経由" 3 "9000020152234"
    55 "R54" 57 "R56" "" "分田線:市民病院経由" 3 "9000020152234"
    55 "R54" 58 "R57" "" "分田線:市民病院経由" 3 "9000020152234"
    59 "R58" 60 "R59" "" "分田線:市役所~安田支所" 3 "9000020152234"
    expired_calendar WARNING 9

    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 "S1"
    3 "S2"
    4 "S3"
    5 "S4"
    6 "S5"
    7 "S6"
    8 "S7"
    9 "S8"
    10 "S9"
    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 "20260911" "20210228" "20260918"
    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.
    "feed_info.txt" 2 "feed_version"
    mixed_case_recommended_field WARNING 146

    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 146 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.
    "stops.txt" "stop_name" "福永[消防車庫前]" 26
    "stops.txt" "stop_name" "福永[消防車庫前]" 27
    "stops.txt" "stop_name" "福永[福永橋寄り]" 28
    "stops.txt" "stop_name" "福永[福永橋寄り]" 29
    "stops.txt" "stop_name" "庵地[五十嵐瓦工業前]" 34
    "stops.txt" "stop_name" "庵地[五十嵐瓦工業前]" 35
    "stops.txt" "stop_name" "庵地[加藤園芸前]" 36
    "stops.txt" "stop_name" "庵地[加藤園芸前]" 37
    "stops.txt" "stop_name" "中山[THK前]" 44
    "stops.txt" "stop_name" "中山[THK前]" 45
    "stops.txt" "stop_name" "小松[諏訪公園前]" 68
    "stops.txt" "stop_name" "小松[諏訪公園前]" 69
    "stops.txt" "stop_name" "小松[諏訪公園前]" 70
    "stops.txt" "stop_name" "六野瀬[消防車庫前]" 77
    "stops.txt" "stop_name" "六野瀬[消防車庫前]" 78
    "stops.txt" "stop_name" "久保[消防車庫前]" 81
    "stops.txt" "stop_name" "久保[消防車庫前]" 82
    "stops.txt" "stop_name" "久保[西潟板金店前]" 85
    "stops.txt" "stop_name" "久保[西潟板金店前]" 86
    "stops.txt" "stop_name" "羽黒[公民館前]" 236
    "stops.txt" "stop_name" "羽黒[公民館前]" 237
    "stops.txt" "stop_name" "蒔田[旧バス停]" 249
    "stops.txt" "stop_name" "蒔田[旧バス停]" 250
    "stops.txt" "stop_name" "リズム・ハウス瓢湖前" 261
    "stops.txt" "stop_name" "リズム・ハウス瓢湖前" 262
    "stops.txt" "stop_name" "小浮本村上[鈴木商店前]" 285
    "stops.txt" "stop_name" "小浮本村上[鈴木商店前]" 286
    "stops.txt" "stop_name" "小浮本村下[五十嵐理容店前]" 287
    "stops.txt" "stop_name" "小浮本村下[五十嵐理容店前]" 288
    "stops.txt" "stop_name" "分田七[塚野酒店前]" 293
    "stops.txt" "stop_name" "分田七[塚野酒店前]" 294
    "stops.txt" "stop_name" "分田五[JA分田支店前]" 295
    "stops.txt" "stop_name" "分田五[JA分田支店前]" 296
    "stops.txt" "stop_name" "上江端二[神明社前]" 305
    "stops.txt" "stop_name" "上江端二[神明社前]" 306
    "stops.txt" "stop_name" "庵地[猿田彦神社前]" 345
    "stops.txt" "stop_name" "庵地[猿田彦神社前]" 346
    "stops.txt" "stop_name" "庵地小路[めんつうテクノ前]" 349
    "stops.txt" "stop_name" "庵地小路[めんつうテクノ前]" 350
    "stops.txt" "stop_name" "庵地小路[丸三安田瓦工業前]" 351
    "stops.txt" "stop_name" "庵地小路[丸三安田瓦工業前]" 352
    "stops.txt" "stop_name" "寺社二[国道東側]" 359
    "stops.txt" "stop_name" "寺社二[国道東側]" 360
    "stops.txt" "stop_name" "天神堂[涌井商店前]" 406
    "stops.txt" "stop_name" "天神堂[涌井商店前]" 407
    "stops.txt" "stop_name" "千原[旧バス停]" 408
    "stops.txt" "stop_name" "千原[旧バス停]" 409
    "stops.txt" "stop_name" "下一分[公園前]" 429
    "stops.txt" "stop_name" "下一分[公園前]" 430
    "stops.txt" "stop_name" "笹岡[渡辺スタンド前]" 435
    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.
    "20260911" "20200901" "20210226"
    big_gap_in_service INFO 2

    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.
    "S1" "2020-12-23" "2021-01-08" 15
    "S3" "2020-12-23" "2021-01-08" 15
    trip_headsign_matches_intermediate_stop INFO 11

    trip_headsign_matches_intermediate_stop

    Trip headsign matches the name of an intermediate stop, not the last stop.

    The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

    You can see more about this notice here.

    csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
    40 "R39+0+S2+1" "笹神支所" "S115_2" 23 "S115_1"
    41 "R39+0+S2+2" "笹神支所" "S115_2" 23 "S115_1"
    50 "R31+0+S2+1" "阿賀野市役所" "S83_1" 1 "S83_2"
    103 "R7+0+S2+1" "安田支所" "S8_1" 1 "S8_3"
    103 "R7+0+S2+1" "安田支所" "S8_2" 32 "S8_3"
    106 "R5+0+S2+2" "安田支所" "S8_1" 1 "S8_3"
    106 "R5+0+S2+2" "安田支所" "S8_2" 33 "S8_3"
    108 "R3+0+S2+1" "安田支所" "S8_1" 1 "S8_3"
    108 "R3+0+S2+1" "安田支所" "S8_2" 33 "S8_3"
    109 "R2+0+S2+1" "安田支所" "S8_1" 1 "S8_3"
    109 "R2+0+S2+1" "安田支所" "S8_2" 35 "S8_3"
    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" "jp_parent_route_id" 8
    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.
    "routes_jp.txt"
    "office_jp.txt"