Quote:
Originally Posted by bradnixon
Vancouver does a pretty good job with its map, described here: https://humantransit.org/2012/05/van...twork-map.html
It shows the "B-Line" routes (sort of like our "Rapid") are dark, thick orange, and then other routes that are frequent are a thinner blue, but frequent segments are highlighted in orange.
|
Good example. That's probably the easiest no-cost fix OC Transpo could do now: leave the current systems and signage as is, but on the maps simply add a highlight to the portions of routes that actually offer "frequent" service.
(On that note: anyone know how to pull scheduling data to make a map like this? Specifically, to show only the segments of routes that provide service that is actually "Frequent".)
Some might say that maps like these aren't relevant now that most people use trip planners or apps. I would argue that we need to be able to visualise our system on a map to really understand how it's working - and not being able to do this leads us to designing narrowly-focused routes focused on specific trips (e.g., the Connexion routes), missing the opportunities for improving service simply with even staggering/spacing of runs amongst routes (even if they are "Local"), etc. If you could show how much/little the city is actually served with good quality transit (i.e., frequent, reliable, day and night, etc) it would be a better starting point for discussion.
Quote:
Originally Posted by CityTech
I'd also change the frequent service standard to actually mean frequent (instead of the current system where 30 minute service on weekends counts as "frequent"), specifically having this be the minimum for "frequent":
-10 minutes or better Monday-Friday 6am-7pm and Saturday-Sunday 12pm-6pm
-15 minutes or better at all other times Line 1 is operating (maybe with an exception allowing drop downs to 20-30 minutes after midnight)
|
This sounds reasonable. The main thing is that "Frequent" actually needs to be frequent enough to be at that level where you can reasonably just show up without checking the schedule; and be able to trust on transferring between two such "Frequent" routes. Branding something as "Frequent" just because it is moreso than the rest of the system doesn't really help - sure, it's better service than "Local" for parts of the weekday, but it's still not at the level that you can actually shape your travel habits any differently.
Quote:
Originally Posted by CityTech
I'd have Rapid, Connexion, Arterial, and Local be colour-coded (as they are now), but with the route number bolded if it's frequent, and the line on the map being made thicker. So by looking at the map, you could tell if a route is Rapid, Connexion, Arterial, or Local by the colour of the line on the map, and then whether its Frequent or not based on how thick the line is. On stop flags, you could tell Rapid/Connexion/Arterial/Local by the colour of the box surrounding the route, and then whether its Frequent or not by whether the number inside the box is bolded or not.
|
I like this idea, though the change to "Arterial" would probably be prohibitive at this point. For ease I'd suggest keeping things as they are. On the map, thicken the appropriate portions of lines to convey frequency (here's another article on
frequency mapping; there's actually good reason to not use as many colours as we do now, in order to
emphasise frequency). On flags, because it would be costly to replace them now, and because it's not always easy to tell the difference between bold and regular font (usually need to have both side by side to tell), you could indicate actual frequent service by adding a sticker next to the symbol, like an asterix or stopwatch icon. Montreal did this for its 10-minute network, for example.