duplicate_fare_media: GTFS validation rule (fares) Warning
Two distinct fare_media rows share the same (fare_media_name, fare_media_type) tuple: downstream consumers cannot tell them apart.
What the rule checks
Two distinct fare_media rows share the same (fare_media_name, fare_media_type) tuple: downstream consumers cannot tell them apart.
Severity: warning
A warning marks data the specification allows but that looks doubtful, or recommended information that is missing. The GTFS can still be published, but riders may see the effect, so each case deserves a look.
Where it applies
The rule applies to the fare files: fare_attributes.txt and fare_rules.txt, or the Fares v2 ones such as fare_products.txt, fare_leg_rules.txt and fare_media.txt.
Finding and correcting it
Open the GTFS in GTFS Express. Reading is free, and the validation, by the MobilityData validator and the rules of GTFS Express itself, lists the occurrences of duplicate_fare_media with the file and rows involved. The correction is made in a draft, by hand or from a brief, with the licence: the corrected GTFS is validated again before it is delivered, and the change can be undone.
In the MobilityData validator
The MobilityData GTFS validator uses the same code, duplicate_fare_media. Its documentation describes each rule: MobilityData validator rules.
Rules of the same domain
- fare_product_with_multiple_default_rider_categories
- fare_transfer_rule_duration_limit_type_without_duration_limit
- fare_transfer_rule_duration_limit_without_type
- fare_transfer_rule_invalid_transfer_count
- fare_transfer_rule_missing_transfer_count
- fare_transfer_rule_with_forbidden_transfer_count
- forbidden_geography_id
- forbidden_prior_day_booking_field_value
- forbidden_prior_notice_start_day
- forbidden_prior_notice_start_time
- forbidden_real_time_booking_field_value
- forbidden_same_day_booking_field_value
- All the validation rules