↑
These stop letters were assigned by the agency,
other lines may enumerate differently.
The stop name currently links to Google Street View;
hover over for address.
00
01
02
03
04
05
06
07
08
09
10
11
15
12
13
14
15
16
17
18
19
20
21
22
23
↑
Hours not covered are struckthrough and grayed out;
times already passed are shown in normal weight and ununderlined;
upcoming are enboldened;
next is underlined in light green,
unless it's currently the closest stop, then light red.
Georgia's varied ascenders and descenders are optimal for Arabic numeral legibility IMHO.
↑
24 hour time makes temporal arithmetic easier (e.g. 6:00 + 8 hours = 14:00),
and removes clutter and confusion.
It feels unfamiliar to Americans ("military time"), but is (AFAIK) dominant in more transit-oriented Eurasia,
and is already widely used for passenger transport
(e.g. Amtrak).
After all, the widespread adoption of 12h time seems due to striking clocks
(i.e. so as not to ring 17 times at quit'n time).
Somewhat contentious in terms of usability,
but powerful products challenge—then change—you, the user.
(You become what you behold, to paraphrase McLuhan.)
Good ones change you for the better.
This layout would seem a good teaching tool for memorizing 24h time,
with the afternoon times right below their p.m. equivalent.
↑
Implementation-wise, not quite sure of the optimal criteria to determine the current stop
(denoted in light red).
Initially should just be the next one.
↑
The hours and minutes are split apart this way from personal experience:
if I know the bus comes for the next four hours at :15,
I feel like I've more flexibility,
since it's easier to remember and consider in short term memory (brain RAM)
without need to keep checking back to a screen.
A good transit app should quickly render itself unnecessary for oft-ridden routes,
with the user quickly memorizing stop locations and times.
Echo Transit