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.

Sign up for GitHub

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

Jump to bottom

Automatically determine historic maximum for Ridership #927

Open
devinmatte opened this issue Jan 4, 2024 · 0 comments
Open

Automatically determine historic maximum for Ridership #927

devinmatte opened this issue Jan 4, 2024 · 0 comments
Labels
backend Change to backend code frontend Change to frontend code nice-to-have Stuff that would be nice to have optimization Optimizing some exisiting functionality

Comments

@devinmatte
Copy link
Member

devinmatte commented Jan 4, 2024 •
edited
Loading

Right now we manually pin a historic maximum for the ridership charts, typically this is a pre-2020 peak ridership number.

We should instead determine this number automatically based on the full dataset.

My proposal is we pick the highest weekly ridership number between 1 year ago and beginning of data. That way we can still show 115% of historic maximum without forever pinning to 2019. We should be able to do this with dynamo data
@devinmatte devinmatte added the frontend Change to frontend code label Jan 4, 2024
@nathan-weinberg nathan-weinberg added optimization Optimizing some exisiting functionality nice-to-have Stuff that would be nice to have labels Feb 16, 2024
@devinmatte devinmatte added the backend Change to backend code label Feb 25, 2024
@devinmatte devinmatte mentioned this issue Sep 21, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend Change to backend code frontend Change to frontend code nice-to-have Stuff that would be nice to have optimization Optimizing some exisiting functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@devinmatte @nathan-weinberg