{"id":17,"date":"2011-02-01T14:32:02","date_gmt":"2011-02-01T14:32:02","guid":{"rendered":"http:\/\/nextransit.org\/blog\/?p=17"},"modified":"2013-02-03T06:40:33","modified_gmt":"2013-02-03T06:40:33","slug":"is-transit-just-an-overlay","status":"publish","type":"post","link":"http:\/\/nextransit.org\/blog\/2011\/02\/is-transit-just-an-overlay\/","title":{"rendered":"Is Transit Just an Overlay?"},"content":{"rendered":"

We’re all familiar with road maps. \u00c2\u00a0They generally take a somewhat 1:1 mapping to a satellite image, removing obstacles like parked cars, trees, and buildings. \u00c2\u00a0It lets us cleanly see where roads go and how to get from one place to another. \u00c2\u00a0Online mapping services, from Mapquest to Google Maps, use a scaling model: when you’re zoomed out, you only see major roads (like highways). \u00c2\u00a0As you zoom in, major throughways appear, and finally small alleys.<\/p>\n

Transit maps, in contrast, have been painstakingly designed over the years to be simple and legible, promoting comprehension and clarity over physical accuracy. \u00c2\u00a0This provides a wonderful way to navigate a transit system. \u00c2\u00a0Google Maps recently added their own transit overlays<\/a>, but are forced to map them to the real-world accurate locations, not the representations.<\/p>\n

<\/p>\n

\"Transit<\/a><\/p>\n

Above, you can see the difference. \u00c2\u00a0On the left, Google Maps shows metro lines in Paris as overlays on road maps, while on the right you see the RATP<\/a>‘s rendition of the Paris Metro. \u00c2\u00a0It’s clear that following the lines on the left quickly becomes confusing, as it provides us with a level of detail that isn’t relevant, assuming we know where we’re going. \u00c2\u00a0The map on the right is clear, concise, and easy to follow, but you must know what stop you’re going to.<\/p>\n

In a transit-oriented city, businesses and individuals always give directions based on their closest transit stop. \u00c2\u00a0This makes figuring how to get somewhere simple: while there are tens of thousands of intersections in a city, there may be only hundreds of transit stops. Once you know you’re headed to Goncourt<\/a>, you know what to do to figure out how to get there, without needing to ask Google.<\/p>\n

\"\"<\/a>While rail-based transit maps are very familiar in cities around the world, many cities, particularly in America, suffer from inadequate rail coverage. \u00c2\u00a0Even in a city like Boston, which is considered one of the better American transit cities, there are only 4 rail lines, but hundreds of bus lines. \u00c2\u00a0Buses are consistently treated differently than other rail-based transit, and the maps are almost always shown as overlays on road maps. \u00c2\u00a0To the left, you see an example of how Boston draws its bus maps. \u00c2\u00a0Since buses follow roads, the logic goes, maps should accurately represent these lines by showing them on top of those roads. \u00c2\u00a0(There are of course exceptions, as one sees clearly in the bottom right, where there are too many bus lines to show 1:1 with the road below.) \u00c2\u00a0So why do buses always get the road map treatment, while trains get the transit map treatment? \u00c2\u00a0What if we mentally changed how we thought about buses to the same model that we use when thinking about rail?<\/p>\n

We’ve been thinking about this vision for a while at Nextransit, and plan to showcase our work shortly with an iPhone app<\/a> that looks at some of these basic premises and redefines how we envision transit maps.<\/p>\n","protected":false},"excerpt":{"rendered":"

We’re all familiar with road maps. \u00c2\u00a0They generally take a somewhat 1:1 mapping to a satellite image, removing obstacles like parked cars, trees, and buildings. \u00c2\u00a0It lets us cleanly see where roads go and how to get from one place to another. \u00c2\u00a0Online mapping services, from Mapquest to Google Maps, use a scaling model: when […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,3],"tags":[],"class_list":["post-17","post","type-post","status-publish","format-standard","hentry","category-maps","category-transit"],"_links":{"self":[{"href":"http:\/\/nextransit.org\/blog\/wp-json\/wp\/v2\/posts\/17","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/nextransit.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/nextransit.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/nextransit.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/nextransit.org\/blog\/wp-json\/wp\/v2\/comments?post=17"}],"version-history":[{"count":0,"href":"http:\/\/nextransit.org\/blog\/wp-json\/wp\/v2\/posts\/17\/revisions"}],"wp:attachment":[{"href":"http:\/\/nextransit.org\/blog\/wp-json\/wp\/v2\/media?parent=17"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/nextransit.org\/blog\/wp-json\/wp\/v2\/categories?post=17"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/nextransit.org\/blog\/wp-json\/wp\/v2\/tags?post=17"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}