mp-kranj — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-09-02T16:29:03Z,
for the dataset file:///shared/mp-kranj_46879b07.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


    Feed Info


    Publisher Name:
    MOK
    Publisher URL:
    https://www.kranj.si/
    Feed Email:
    N/A
    Feed Language:
    English
    Feed Start Date:
    2026-08-31
    Feed End Date:
    2026-09-30

    Files included


    1. agency.txt
    2. areas.txt
    3. calendar.txt
    4. feed_info.txt
    5. networks.txt
    6. route_networks.txt
    7. routes.txt
    8. shapes.txt
    9. stop_areas.txt
    10. stop_times.txt
    11. stops.txt
    12. trips.txt

    Counts


    • Agencies: 0
    • Blocks: 30
    • Routes: 23
    • Shapes: 54
    • Stops: 142
    • Trips: 446

    Specification Compliance report

    11 notices reported (4 errors, 4 warnings, 3 infos)

    Notice Code Severity Total
    block_trips_with_overlapping_stop_times ERROR 3

    block_trips_with_overlapping_stop_times

    Trips with the same block id have overlapping stop times.

    You can see more about this notice here.

    csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip. tripIdA (?) The id of first faulty trip. serviceIdA (?) The service id of the first faulty trip. csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip. tripIdB (?) The id of the other faulty trip. serviceIdB (?) The service id of the other faulty trip. blockId (?) The `trips.block_id` of the overlapping trip. intersection (?) The overlapping period.
    13 "Mp5mxR2F5D_154676" "1" 88 "Mp5mxR2F5D_oph0b1n" "1" "4505" "20260831"
    12 "Mp5mxR2F5D_155201" "1" 99 "Mp5mxR2F5D_155220" "1" "4506" "20260831"
    99 "Mp5mxR2F5D_155220" "1" 82 "Mp5mxR2F5D_155202" "1" "4506" "20260831"
    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" "MP_Kranj"
    duplicate_route_name WARNING 1

    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`.
    5 "4015" 6 "4016" "1" "Prebačevo - Kranj kolodvor" 3 "MP_Kranj"
    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"
    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 "20260902" "20260930" "20261002"
    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
    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.
    "trips.txt" "duty" 11
    "trips.txt" "duty_sequence_number" 12
    "trips.txt" "run_sequence_number" 13