Describe the problem

As GTFS components evolve, we want to provide clear public documentation on how we're defining the "presence" of a GTFS component. This will help us make decisions in the future if we want more granular calculations (e.g tracking the actual usage of a component in the feed). The code is here..

Proposed solution

• A 2 column table where each component has its associated logic.

Alternatives you've considered

• Programmatically generating this (may be too time consuming for the value at the moment)

Additional context

No response