Difference between revisions of "Frequent bus network map"
| Line 5: | Line 5: | ||
== Layers of Service == | == Layers of Service == | ||
| − | A standard system map can be misleading when it includes every route on the system | + | A standard system map can be misleading when it includes every route on the system without meaningful visual distinctions. Including limited service routes alongside those that run a regular frequency all day misleadingly represents coverage that might not exist or imply route connections that are impossible to make. |
| − | The "frequent network" is made up only of bus routes which run regularly throughout the entire service day. Walker also defines this network as routes running every 15 minutes or more frequently<ref>Walker, Jarrett. Human Transit (blog) "The Case for Frequency Mapping" http://www.humantransit.org/2010/08/basics-the-case-for-frequency-mapping.html. 6 August 2010</ref>. However, even small agencies with twenty, thirty, or sixty-minute headways system-wide can take advantage of the principle of differentiating maps by "all day service" and others. Even small agencies can have routes which operate only at specific times or on specific days, such as a Wednesday "Shopper Shuttle". Including these services on the map might be well-intentioned, but will mislead customers to assume it runs like the rest of the system. | + | The "frequent network" is made up only of bus routes which run regularly throughout the entire service day. Walker also defines this network as routes running every 15 minutes or more frequently<ref>Walker, Jarrett. Human Transit (blog) "The Case for Frequency Mapping" http://www.humantransit.org/2010/08/basics-the-case-for-frequency-mapping.html. 6 August 2010</ref>. However, even small agencies with twenty, thirty, or sixty-minute headways system-wide can take advantage of the principle of differentiating maps by "all day service" and others. Even small agencies can have routes which operate only at specific times or on specific days, such as a Wednesday "Shopper Shuttle". Including these services on the map might be well-intentioned, but will mislead customers to assume it runs like the rest of the system. Instead of relying on map notes for distinction, the route could be differentiated using a thinner or fainter line, or excluded from the system map. |
In 2012, King County metro released a new system map which does include all services (including light rail alongside bus and ferry routes), but differentiates routes between frequent, peak period only, and all-day infrequent. The "rapid" routes stand out in bold, eye-catching red lines. The all-day frequent routes are in strong black lines and numbers, while peak-only service is in a faded blue. The visual distinction makes the difference between service level and geographic coverage very clear and understandable for the customer. | In 2012, King County metro released a new system map which does include all services (including light rail alongside bus and ferry routes), but differentiates routes between frequent, peak period only, and all-day infrequent. The "rapid" routes stand out in bold, eye-catching red lines. The all-day frequent routes are in strong black lines and numbers, while peak-only service is in a faded blue. The visual distinction makes the difference between service level and geographic coverage very clear and understandable for the customer. | ||
| Line 15: | Line 15: | ||
<references /> | <references /> | ||
| + | [[Category:Market Response]] | ||
Revision as of 02:01, 11 April 2014
THIS ARTICLE IS IN DEVELOPMENT
Introduction
Most agencies likely publish a system or network map of their bus service. A system map can be helpful in familiarizing the customer with area coverage, but can also paint a misleading picture of actual availability when not all lines run comparable schedules. Many agencies have routes which only operate at certain times of day, such as peak period or overnight, which might appear on the system map alongside routes which run all day. A "frequent network map" includes only routes which run on a consistent and high frequency, visualizing both actual connections and the highest level of mobility on the system.
Layers of Service
A standard system map can be misleading when it includes every route on the system without meaningful visual distinctions. Including limited service routes alongside those that run a regular frequency all day misleadingly represents coverage that might not exist or imply route connections that are impossible to make.
The "frequent network" is made up only of bus routes which run regularly throughout the entire service day. Walker also defines this network as routes running every 15 minutes or more frequently[1]. However, even small agencies with twenty, thirty, or sixty-minute headways system-wide can take advantage of the principle of differentiating maps by "all day service" and others. Even small agencies can have routes which operate only at specific times or on specific days, such as a Wednesday "Shopper Shuttle". Including these services on the map might be well-intentioned, but will mislead customers to assume it runs like the rest of the system. Instead of relying on map notes for distinction, the route could be differentiated using a thinner or fainter line, or excluded from the system map.
In 2012, King County metro released a new system map which does include all services (including light rail alongside bus and ferry routes), but differentiates routes between frequent, peak period only, and all-day infrequent. The "rapid" routes stand out in bold, eye-catching red lines. The all-day frequent routes are in strong black lines and numbers, while peak-only service is in a faded blue. The visual distinction makes the difference between service level and geographic coverage very clear and understandable for the customer.
Further Reading
Walker, Jarrett. "Human Transit: How Clearer Thinking about Public Transit Can Enrich Our Communities and Our Lives." Chapter 7. 2012.
- ↑ Walker, Jarrett. Human Transit (blog) "The Case for Frequency Mapping" http://www.humantransit.org/2010/08/basics-the-case-for-frequency-mapping.html. 6 August 2010