-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
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
Gtfs docs #2862
Gtfs docs #2862
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! I am being incredibly nitpicky
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Eric!
docs/warehouse/what_is_gtfs.md
Outdated
|
||
### Video Notes | ||
|
||
* Laurie mentions downloading an example feed to look at the files. This is a great idea! But when working with our data warehouse remember that you don't have to interact with raw GTFS feeds directly (lots of important work has been done for you!). Still, we reccomend taking a look at an example feed to understand what it looks like. Here's one from [Big Blue Bus](http://gtfs.bigbluebus.com/current.zip). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still see a typo warning here for reccomend
|
Description
Docs page with a link to @lauriemerrell video and a few notes for our new analysts! May expand in the future.
Type of change
How has this been tested?
Include commands/logs/screenshots as relevant.
Post-merge follow-ups
Document any actions that must be taken post-merge to deploy or otherwise implement the changes in this PR (for example, running a full refresh of some incremental model in dbt). If these actions will take more than a few hours after the merge or if they will be completed by someone other than the PR author, please create a dedicated follow-up issue and link it here to track resolution.