1/ How do we make transit maps of complex networks that are user-friendly?
I did an experiment to try to imagine some features of a "map+schedule" centered around users' experience and adapted to a network based on a clockface/timed transfer service pattern.
I'll explain.
I did an experiment to try to imagine some features of a "map+schedule" centered around users' experience and adapted to a network based on a clockface/timed transfer service pattern.
I'll explain.
2/ Traditional transit maps show lines and/or service as individual lines. Transfer nodes are highlighted so users now where they can transfer from one service to another. Sometimes, in low frequency bus-based networks, the frequency pattern is highlighted with colors.
3/ But that is not enough when we want to present a wide, mashed regional rail network, based on clockface relatively infrequent service (30-60 min) but with timed transfert on multiple nodes. Because the viability of a trip depends on the journey length, including transfert
4/ So we need a map that shows both service patterns and a simplified timetable not only for the station where the user boards, but also at connecting nodes for all the possible journey combinations. The idea is to have a map centered around what matters for the user's experience
5/ So, I tried to figure out how a graphic tool combining route&time-planning features might look like.
I called it "cartorario", merging the words map and timetable in Italian, and applied the idea to the case of a particular station in my home region's rail network.
I called it "cartorario", merging the words map and timetable in Italian, and applied the idea to the case of a particular station in my home region's rail network.
6/ How does it work. The map is tailored for a particular starting station. It shows the different services and the minute where they leave the station in different directions. That works in perfectly clockface/takt/memorario" systems.
7/ Of course that can be shown with a traditional timetable, the yellow board normally exposed at every station. But that does tell only that a train leaves at a certain time. They are hard to read and to remember. An "at a glance" version would be better, but still limited.
8/ Maps should be reliable trip planning tool. Especially in a network that is supposed to work at its best by offering timed connections, thus expanding the reach of possible trip combinations in a meshed network that minimize waiting times.
9/ So, here is how such a map-schedule "Maporario" might work:
if I want to go from Imola to Pianoro, I know that I can take the S4 trains leaving at :08 and :38, transfert at S. Vitale to S1 and wait 5'. In less than 1 hour, I'm at destination
if I want to go from Imola to Pianoro, I know that I can take the S4 trains leaving at :08 and :38, transfert at S. Vitale to S1 and wait 5'. In less than 1 hour, I'm at destination
10/ But there are alternatives, slightly longer but still doable: Take the R leaving at :34 or the RV leaving at :00, change to S1 at Bologna Centrale with a slightly longer connection, and arriving at destination a few minutes later.
11/ Of course this kind of trip planning can now be done with a trip planner.
But the utility of a map is to make the users departing from Imola all the places they can reach, how and in how much time in a single glance, as a transit map should do. It's a map of possibilities
But the utility of a map is to make the users departing from Imola all the places they can reach, how and in how much time in a single glance, as a transit map should do. It's a map of possibilities
12/ The goal is to make visible what matters for a transit network, both from the perspective of users and planners (that should be the same perspective!): the degree of freedom of movement it provides: how far I can go, how fast, how often.
13/ People don't care who owns the tracks, who runs the trains, how is the infrastructure (electrified or not, single or double track). Yet, the map on the official Regional website looks like that.
Plenty of useless informations from a user's perspective.
Plenty of useless informations from a user's perspective.
15/People don't board a "line", they board a train/bus. Transit is not like roads and should not be represented as a road network, but as a collection of services. For a transit user, time matters more than distance. Waiting time for connections is as important as travelling time
16/ That map is an uncomplete, rough an unrefined draft of an idea. But it is intended as an exercice to imagine different ways to communicate to the users the possibilities of a well structured service pattern in a much clearer, easy-to-read way.
17/ When very high frequency is not viable, reliability and predictability are the key elements to make a transit service attractive and competitive with other modes.
Maps, as user's interface, should convey these characteristics and thus incorporate time and not only space.
Maps, as user's interface, should convey these characteristics and thus incorporate time and not only space.
18/ Finally, I think that planners should be much more involved in thinking and imagining the user's interface with the transit system, because that is the only criteria that matters when planning a user-oriented system. Everything else (infra, organization etc.) is a consequence
Loading suggestions...