Two bugs: route page % clinched by segment

[si404]

I agree with compdude.  There is no reason for this to track percentages for all users because someone like michih, who has a slim chance of traveling most routes in the US, gets tracked if doing all users just like all of us in the US.

And vice versa.

33 users have travelled this (one of the highest in Europe), which is over 10%, but the highest segment is 8.8%. I'm not doing the maths to work out how many that is (27 via a different route to find out).

Arguably a number would be better than a percentage for the segment totals.

[mapcat]

Arguably a number would be better than a percentage for the segment totals.

Agreed. Plus, this would be consistent with how the data appear in mapview.

[andrepoiy]

I agree. I thought that it was strange that it was only like 1% when I was the only one that travelled on a certain route.

[compdude787]

Arguably a number would be better than a percentage for the segment totals.

Agreed. Plus, this would be consistent with how the data appear in mapview.

Yeah, I actually like the idea of having a number rather than a percentage.

[vdeane]

What does having only a number give us that percent of users who traveled on a given route doesn't?  I would think the percentage would be more useful - it just needs to be put back on the metric that makes sense.  If you want a number, then maybe list both, but I know I'm more interested in the percentage.  I don't really care about the raw number.

[michih]

What does having only a number give us that percent of users who traveled on a given route doesn't?

A number is clear. No room for interpretation. With percentage you always need to know the base, i.e. what does 100% mean?

[yakra]

A number is clear. No room for interpretation. With percentage you always need to know the base, i.e. what does 100% mean?

That number is also displayed in the HB, so we can make the calculation.

[Jim]

Looking for opinions about what I have on tmstage.teresco.org (and testing of it to make sure it looks correct now).

[Markkos1992]

Looks fine, but oddly enough, you see it on the connected route page for I-95, but not on the DE I-95 page.  I am not sure how we rectify that though.

EDIT:  Never mind, it must have been straightened out already...

[yakra]

Looking for opinions about what I have on tmstage.teresco.org (and testing of it to make sure it looks correct now).

I like it. Provides both the raw # & %age, without taking up any more real estate.

[si404]

It's a like from me!

[andrepoiy]

Is it just me or are the colours still a bit off? For example, ON427 at QEW is still a yellow despite the percentage being 96%

[Jim]

Looks fine, but oddly enough, you see it on the connected route page for I-95, but not on the DE I-95 page.  I am not sure how we rectify that though.

EDIT:  Never mind, it must have been straightened out already...

Looks like I've got a race condition in there.  I wasn't happy with my solution anyway but thought it was just a little inelegant.  Turns out it's just broken.  Hope to get another look at it before too long.  Big pile of grading awaits first.

[compdude787]

Looks good to me.

[michih]

The info text could be improved.