Describe the problem

As highlighted by Trillium on the spec repository, right now stop_without_zone_id's logic is that if fare_rules.txt contains records, then presence of zone_id is required for all stops in the dataset.

However, zone_id should not be required for route_based fares.

Proposed solution

Update logic so notice is triggered IF 1 stop without a zone_id has a trip_id in stop_times.txt whose route_id defines origin_id, destination_id OR contains_id in fare_rules.txt.

Alternatives you've considered

No response

Additional context

No response