Till senaste kommentaren

Bug report: duplicate dated_vehicle_journey_gid in varm_extra.zip

Hi,I found a data quality issue in the VARM extra GTFS file:https://opendata.samtrafiken.se/gtfs/varm/varm_extra.zip**1. Non-unique dated_vehicle_journey_gid (main issue)**In trips_dated_vehicle_journey.txt, 8,243 dated_vehicle_journey_gid values are shared across multiple trip_ids and operating dates. Per the GTFS Nordic / NeTEx spec, each GID should uniquely identify a single vehicle journey on a specific operating day.Example — GID 9015017000100685 is assigned to four different trip_ids:- trip 175500000282937834 on 2026-06-13- trip 175500000283143425 on 2026-06-19- trip 175500000282215004 on 2026-07-11- trip 175500000281491462 on 2026-08-22GIDs appear to be reused across seasonal service periods rather than being generated uniquely per dated journey. The composite key (gid + operating_day_date) is unique, which confirms GIDs alone are not sufficient as identifiers.**2. GTFS Schedule Validation (MobilityData canonical validator v8.0.1)**I also ran the file through the canonical GTFS validator (country code: SE), which reported 8 notices: 6 errors, 1 warning, 1 info.- missing_calendar_and_calendar_date_files — ERROR (1 occurrence)- missing_required_file — ERROR (5 occurrences)- missing_recommended_file — WARNING (1 occurrence)- unknown_file — INFO (1 occurrence)Note: several of these errors are expected since the _extra zip contains only trips_dated_vehicle_journey.txt and not the full GTFS feed. However, the unknown_file notice confirms that trips_dated_vehicle_journey.txt is not a recognized standard GTFS file, and the missing required files (agency.txt, routes.txt, trips.txt, stop_times.txt, stops.txt) indicate the extra file is not self-contained or independently valid.**Impact**Systems using dated_vehicle_journey_gid as a primary node identifier (e.g. multimodal graph databases, journey planners) will experience node collisions and incorrect merging of trips across service periods.Could you confirm whether the GID reuse is intentional, and if not, issue a corrected export?Thanks!
Steven Angel

Kommentarer

  • Please write support issues manually and be critical of any AI output. This wall of text only contains the question "can duplicate GIDs be present in trips_dated_vehicle_journey.txt", along with a bunch of meaningless and/or completely incorrect hallucinations. AI cannot help you in areas where you cannot verify its output yourself. Reading our documentation would have shown you that using the GTFS validator on extra files is meaningless as the extra files are not part of the GTFS standard at all.

    "Per the GTFS Nordic / NeTEx spec, each GID should uniquely identify a single vehicle journey on a specific operating day." GTFS nordic does not exist, and neither GTFS nor NeTEx have a concept of GIDs. Please respect our time by submitting well though out questions. Why should we spend time on answering your question if you cannot put in the time yourself to review and understand it yourself? 

    Yes, gids can be reused on different date, as they according to the Noptis standard only are unique on a given date. Even then, duplicate gids can appear in specific cases, when reinforcement trips are scheduled so multiple vehicles can run the exact same trip for increased capacity.

    Regards,
    Bert


    Bert på Trafiklab

Kommentera eller skriv ett nytt inlägg

Ditt namn och inlägg kan ses av alla. Din e-post visas aldrig publikt.