-
Notifications
You must be signed in to change notification settings - Fork 17
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
Highlight unusually low headways in chart #972
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.
I love this idea, but I almost wonder if we're sending the wrong message here - the blue coloring almost suggests this is a good thing, which on the surface could appear to be the case - such a short wait for a train! - but if we're trying to highlight bunching here, I feel like we should try to more clearly communicate what it is and why it's a bad thing
I'm not married to blue as the color, I just didn't want to use a color we already use on the legend |
You thinking we shouldn't differentiate 25% late vs 50% late with different colors like we do today and instead just do red for all late trips? |
Well, I think the system that we have works well, but if we're introducing a color for bunched trips, I think it should be a "warning" color like orange or yellow. My first thought was that we'd no longer be able to use it for slightly late trips, but maybe we could keep it for both? |
So basically yes, that's the proposal. But I don't feel very strongly about it. |
Perhaps we can call out early trips (25%-) and bunched trips (50%-) with the same colors as 25%+ and 50%+? |
yes I think that makes the most sense! |
How about this @idreyn? |
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!
Motivation
Show headways which are 50% under the benchmark, often meaning that there's bunching
relates to #969
Changes
Testing Instructions