There's no easy way to know if a feed is the official source transit authorities want consuming apps to use. This concept doesn't exist in the specification, so we have to find another way of gathering this insight.
Proposed solution
Ideas:
• Could we automate checking if the GTFS feed link is on the agency's website? We'd probably need the unique list of transit providers before doing this, with their associated URLs, and then scrape them to see if they reference the GTFS feed URL anywhere.
• In many cases, the GTFS feed is not linked on the agency's website at all, so there's still the necessity to reach out to the agency directly and clarify this. Could look like:
Taking the agency_email from the GTFS feed and asking them to verify that the GTFS URL is the one they want journey planners to use to share with riders. If they press "Yes" in the email, then we automatically generate a PR in the catalogs repo to update the official tag and timestamp
Describe the problem
There's no easy way to know if a feed is the official source transit authorities want consuming apps to use. This concept doesn't exist in the specification, so we have to find another way of gathering this insight.
Proposed solution
Ideas:
• Could we automate checking if the GTFS feed link is on the agency's website? We'd probably need the unique list of transit providers before doing this, with their associated URLs, and then scrape them to see if they reference the GTFS feed URL anywhere. • In many cases, the GTFS feed is not linked on the agency's website at all, so there's still the necessity to reach out to the agency directly and clarify this. Could look like:
Alternatives you've considered
No response
Additional context
No response