You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rider_type and rider_type description could be synced with GTFS+ concepts (or another such approach to fare categories, as generally, it seems likely that rider types should map onto fare categories). Alternately they could map to something else like census designated categories.
The text was updated successfully, but these errors were encountered:
Yes, I believe such links would be helpful as a way to standardize the depiction of categories used across several realms, but perhaps further down the road. I wouldn't want a potential user of GTFS-ride to feel required to understand or use GTFS+ as a prerequisite for using the GTFS-ride standard. Is GTFS+ growing in adoption to where it would make sense to link to their designations? We definitely want to standardize as much as possible while balancing the need for flexibility which will enable the largest numbers of initial adopters of GTFS-ride.
rider_type and rider_type description could be synced with GTFS+ concepts (or another such approach to fare categories, as generally, it seems likely that rider types should map onto fare categories). Alternately they could map to something else like census designated categories.
The text was updated successfully, but these errors were encountered: