What problem is your feature request trying to solve?
There are cases (like https://otd.delhi.gov.in/data/static/) where there is no formal authentication process for a GTFS feed (like registering for an API account), but there's no way to retrieve the feed without individually consenting to the Terms and Conditions.
Describe the solution you'd like
Include an auth type=4 that means "other" in the GTFS Schedule and Realtime schemas to capture cases like this.
Update schema in the README
Update python operations
Update API schema
Updating tests
Update batch processing to omit dataset storing for auth_type=3
Database changes for enum
Auth type 4 would not triggering the storing datasets workflow in the Mobility Database.
What problem is your feature request trying to solve? There are cases (like https://otd.delhi.gov.in/data/static/) where there is no formal authentication process for a GTFS feed (like registering for an API account), but there's no way to retrieve the feed without individually consenting to the Terms and Conditions.
Another: https://data.grandlyon.com/portail/fr/accueil requires users login before accessing the feed.
Another: https://data.mobilitaetsverbuende.at/en/data-sets
Is there any way for us to automate this?
Describe the solution you'd like Include an
auth type=4
that means "other" in the GTFS Schedule and Realtime schemas to capture cases like this. Update schema in the README Update python operations Update API schema Updating tests Update batch processing to omit dataset storing for auth_type=3 Database changes for enumAuth type 4 would not triggering the storing datasets workflow in the Mobility Database.
Example Feeds that Need a Login to Be Used: