Describe the problem
There are many cases where there's an official GTFS feed, but due to either issues parsing the information or quality problems, others have produced an "improved" version of the feed that is publicly available: MobilityData/mobility-database-catalogs#1518 (comment)
It would be helpful to add this concept to our schema so it's possible to label certain feeds as modified versions of a pre-existing one.
Proposed solution
I'm imagining something similar to our redirect/deprecated relationship. A feed can be tagged as "modified" and then its source ID can be tied to it.
Alternatives you've considered
No response
Additional context
No response
Describe the problem
There are many cases where there's an official GTFS feed, but due to either issues parsing the information or quality problems, others have produced an "improved" version of the feed that is publicly available: MobilityData/mobility-database-catalogs#1518 (comment)
It would be helpful to add this concept to our schema so it's possible to label certain feeds as modified versions of a pre-existing one.
Proposed solution
I'm imagining something similar to our redirect/deprecated relationship. A feed can be tagged as "modified" and then its source ID can be tied to it.
Alternatives you've considered
No response
Additional context
No response