Skip to content
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

[Data] Update schedule configuration #36

Open
lauriemerrell opened this issue Oct 24, 2022 · 1 comment
Open

[Data] Update schedule configuration #36

lauriemerrell opened this issue Oct 24, 2022 · 1 comment

Comments

@lauriemerrell
Copy link
Member

The way we have to load the schedule data is a little arcane, because we have to handle the concept of "when was this online".

I think we need to do the following:

  • Create a schedule_config.yml file to store information about schedule versions (replacing the dictionary here)
  • Write up information about how we use schedule data in our data analysis README and/or our actual website methodology section

Here's an explanation I sent to @dcjohnson24 offline about how the schedule config dictionary is constructed:

The version uploaded on June 3 takes effect on June 4 because I don't know what time of day it should become effective
And then that June 3 version ends on June 7 because there's a new version uploaded June 8
It's just non-overlapping ranges showing when that version was online, no reference to actual feed content

Sidebar I think we may have some slight weirdness about these dates because I think that the dates on TransitFeeds are in UTC time and our work is all in Central Time.

@dcjohnson24
Copy link
Collaborator

Thanks for this. I've made an attempt at scraping the schedule versions from TransitFeeds here. I can work on adding the explanation of the schedule dictionary construction to the README and website copy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants