We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We’ve been hard at work gathering feedback and working to make GTFS.org the only place you need to visit for everything GTFS.
Whether you’re new to the transit specification or a seasoned GTFS veteran, GTFS.org has everything you need.
Here are some of the changes you can expect to see during your first visit:
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
FYI looks like at least one link indexed by search engines is broken now -- https://gtfs.org/schedule/best-practices now forwards to https://gtfs.org/documentation/schedule/GTFS%2520schedule%2520best%2520Practices/ (404). Possibly a faulty redirect rule?
@ungoldman Thanks for bringing it up. We just made the changes to make sure it redirects properly to https://gtfs.org/documentation/schedule/schedule_best_practices/, it should work now.
Make sure to delete your cookies and try again via your search engine.
Thanks @eliasmbd, redirect looks fixed to me.
Changing dashes to underscores in URLs... seems like not a best practice? 😈
Nice redesign! 👍
No branches or pull requests
🤩GTFS.org had a facelift 🤩
We’ve been hard at work gathering feedback and working to make GTFS.org the only place you need to visit for everything GTFS.
Whether you’re new to the transit specification or a seasoned GTFS veteran, GTFS.org has everything you need.
Here are some of the changes you can expect to see during your first visit:
The text was updated successfully, but these errors were encountered: