fare_transfer_rule_missing_transfer_count: GTFS validation rule (fares) Error
A fare_transfer_rules row has from_leg_group_id equal to to_leg_group_id but no transfer_count: required for symmetric transfers.
What the rule checks
A fare_transfer_rules row has from_leg_group_id equal to to_leg_group_id but no transfer_count: required for symmetric transfers.
Severity: error
An error marks data that breaks the GTFS specification. A journey planner or a rider app may refuse the file, or show a wrong version of it. Correct it before publishing the GTFS.
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 fare_transfer_rule_missing_transfer_count 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, fare_transfer_rule_missing_transfer_count. Its documentation describes each rule: MobilityData validator rules.
Rules of the same domain
- duplicate_fare_media
- 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_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