Fix: the feed lists no contact
Published: . Last reviewed: .
Code: missing_feed_contact_email_and_url (MobilityData validator)
What this means
feed_info.txt has neither feed_contact_email nor feed_contact_url, so there
is no way to reach whoever maintains the feed. Both are optional in the spec, but
the validator recommends having at least one.
Why it matters
App makers, trip planners, and state data programs sometimes spot a problem in a feed before the agency does. With no contact, they have nobody to tell, so the problem sits unreported and the feed stays broken longer than it needed to. One field turns a silent failure into a quick heads-up.
How to fix it
Add a contact to feed_info.txt:
feed_contact_email: a monitored address, ideally a role inbox such asgtfs@youragency.orgrather than one person's address, so it survives staff changes.- or
feed_contact_url: a page or form where issues can be reported.
Either one satisfies the check. Most scheduling tools expose this in the same
export settings that write the rest of feed_info.txt.
How long it usually takes
One field, set once.
Authoritative rule
missing_feed_contact_email_and_url is a canonical MobilityData GTFS Validator notice used in validator reports across the GTFS ecosystem. Read the authoritative rule for missing_feed_contact_email_and_url in the GTFS Validator rules. (opens on an external site)
After you republish
Once the changed feed is live at your published URL, the next scorecard run checks it again. When the same complete producer contract no longer reports this finding, it can be recorded as a dated finding clearance. That confirms the later feed state, not who changed the feed or why.