Why Was My GTFS Feed Rejected by Google?

Q: Why was my GTFS feed rejected by Google?

Common rejection reasons include: validation errors (missing fields, broken references), inaccurate stop locations, missing shapes.txt, expired calendar dates, and data quality issues. Validate your feed before submitting to identify and fix problems.

Google usually rejects feeds because of validation errors, inaccurate stop locations, or missing required info. Always validate before you submit.

Common Rejection Reasons

1. Validation Errors

This is the #1 reason for rejection. Google runs a strict check on every file you send. If columns are missing or dates are in the wrong format, they'll send it back.

The Fix: Run your file through GTFS Guru first. If it finds even one error, Google will too. Fix them all before hitting submit.

2. Inaccurate Stop Locations

Google's reviewers are eagle-eyed. If they see a bus stop in the middle of a lake or inside someone's living room, they'll reject the feed. Swapping your latitude and longitude is a very common mistake!

The Fix: Double-check your coordinates. Try plotting a few of them on a map to make sure they're actually on the street where they belong.

3. Missing shapes.txt

While technically optional, Google strongly prefers feeds with shapes. Without them, routes appear as straight lines between stops, which looks unprofessional and confuses users.

Fix: Add shapes.txt with the geographic paths your vehicles follow.

4. Expired Calendars

If your calendar dates have already passed, your buses will simply vanish from the map. It's the most common reason for a suddenly "broken" feed.

The Fix: Keep your calendars extending at least 3-6 months into the future. Update them before they expire!

5. Invalid Timezones

Google needs timezones in a very specific format (like "America/New_York"). If you use something like "EST," the whole schedule will break.

The Fix: Use the official IANA timezone name for your region. When in doubt, look it up!

6. Impossible Schedules

If your schedule says a bus travels 10 miles in 1 minute, the reviewer will flag it as "impossible." Same goes for arrival times that happen before the bus even departs.

The Fix: Review your stop times. Make sure the travel durations are realistic for your vehicles and traffic conditions.

7. Duplicate or Conflicting Submissions

If someone else has already submitted data for your routes (perhaps an outdated feed from a previous partnership), Google may flag the conflict.

Fix: Contact Google through the Partner Dashboard to resolve duplicates.

8. Not Authorized

Google requires that submitters have legitimate authority to publish the data. If you're submitting on behalf of an agency, you may need to prove authorization.

Fix: Ensure you have proper authorization. Use an official agency email address.

How to Avoid Rejection

1. Validate first. Always run your feed through a validator before submitting. Fix all errors and address warnings.

2. Include shapes. Take the time to create accurate route shapes.

3. Check coordinates. Plot a sample of stops on a map to verify accuracy.

4. Review the preview. Google's Partner Dashboard shows a preview. Check it carefully before requesting publication.

5. Keep it current. Update your feed regularly, especially calendar dates.

Still Getting Rejected?

If you've fixed all validation errors and still face issues:

• Check the Partner Dashboard for specific feedback

• Contact Google Transit support through the dashboard

• Review Google's GTFS best practices documentation