-
Notifications
You must be signed in to change notification settings - Fork 113
Closed
Description
Describe the problem
We adopted rider categories. The PR will be merged soon.
Describe the new validation rule
| Related spec language | Rationale for rule | Notice name to update or add | Pseudologic | Notice table columns | Severity | Notice description |
|---|---|---|---|---|---|---|
| rider_categories.rider_category_id, fare_products.rider_category_id, is_default_fare_category | When multiple rider categories are eligible for a single fare product specified by a fare_product_id, there must be exactly one of these eligible rider categories indicated as the default rider category |
fare_product_with_multiple_default_rider_categories | if rider_categories.txt does not exist: Do not trigger a notice and ignore subsequent checks For each fare_product_id: If multiple rider_category_id are associated: If more than one of these rider_category_id has is_default_fare_category ==1: Trigger Notice |
FareProductId, CsvRowNumber1,CsvRowNumber2 (for the fare product), RiderCategoryId1,RiderCategoryId2 | ERROR | A fare product in fare_products.txt has more than one eligible default rider category from rider_categories.txt. |
Sample GTFS datasets
http://developer.trimet.org/schedule/gtfs.zip
Severity
ERROR
Additional context
gtfs.org documentation: google/transit#511
Metadata
Metadata
Assignees
Labels
new ruleNew rule to be addedNew rule to be added