Category Archives: Uncategorized
Once upon a time, there was a website called MapBlast. This was during the wild frontier days of online road maps about ten years ago, when MapQuest was king and Google Maps was but a gleam in the eye of a couple of Danish guys in Australia. MapBlast never seemed to me to be more than a minor player during these days, but it had one special feature that made it my website of choice for route planning: LineDrive directions.
Then, as now, all the other online mapping services gave you route maps that looked like this, a highlighted route drawn onto a standard road map:
MapBlast, though, could give you what they called LineDrive directions, a linear cartogram of your trip that looked like this:
LineDrive was developed by Maneesh Agrawala, Chris Stolte, and Christian Chabot at Stanford University, and they describe their system in a 2001 paper if you’re interested in the details. What is most interesting to me is the creators’ inspiration for LineDrive: hand-drawn route maps. While most online mapping services were, and still are, patterned after paper road atlases, LineDrive was designed to look like what you might quickly sketch on a napkin.
This starting point leads to something quite remarkable. Hand-drawn route maps are custom products — they’re for just a few people, and are about going between one specific place and another. A road atlas, on the other hand, is the same for everyone. It doesn’t change based on the situation. It’s multipurpose, which is quite valuable, but it’s not as effective for a given route as something customized.
When the Web came along, the mapping services that came online simply translated the idea of a paper road atlas into its digital equivalent. They added a few enhancements — you could zoom in and out or draw routes on them, but it was fundamentally the same thing. It was still multipurpose, not customized. When mapping services today talk about customization, they mean that you get to draw a blue line on top of their map or add a picture of a pushpin. But the map is always the same for everyone. LineDrive’s most remarkable feature was that it gave everyone their own map, fully customized to their specific situation. It should have been revolutionary, but it turns out that nothing ever came of it, at least in the realm of online driving directions.
I did not apprehend the significance of this development at the time. Instead, I merely loved the design. It was brilliant. Clean, simple, effective. It tells you everything you need to know about how to get from A to B, and it tells you nothing else. There is no clutter. It does not take up my time or printer ink with roads I won’t be using, or cities hundreds of miles from those I’ll be passing through. I can look at this map quickly while driving. I don’t have to hunt around the page to find the little blue line that contains the path information I need — everything on this page is there because it’s essential.
The LineDrive map shows every detail of the whole route at once by distorting scale. It makes the short legs of the trip look longer, and the long legs shorter, so that everything is visible on the same page at once. With a more traditional road map, either in an atlas or printed off of Google/Bing/etc., I would actually need several maps at different scales to cover each part of the route — zooming in to Madison to show how I get to the highway, then zooming out to show the highway portion of the trip, etc. LineDrive fits everything on the same page, and it does so legibly. Again, it’s customized, which is what gives it value.
Since the scale changes, the length of each leg drawn on the map doesn’t correspond to the same distance. Therefore each line is marked with its distance, so you don’t lose that valuable information. In fact, distance is presented more clearly than on a standard road map. If I wanted to figure out how long each leg of my trip was on Google’s map, I’d have to go compare each one to the scale bar in the corner, measuring it out bit by bit. Or, I’d have to check the written directions. It’s not usually presented clearly on the map itself. For me, LineDrive eliminates the need for a verbal listing of directions accompanying the map. They can be clearly read out from the map itself, distances and turn directions and all.
This map doesn’t do everything, to be sure. It’s only good for getting from one place to another. It’s very purpose-specific, and there are plenty of things that more standard traditional print and online road maps can do that this can’t. It won’t tell you where the city you’re driving to actually is, or what’s nearby. You can’t deviate from the path, so you can’t react to road closures or changes of plan by switching roads. You don’t know the names of the towns you’ll be passing through. Within its particular niche, though, LineDrive was very, very effective, just like the hand-drawn maps it was inspired by.
I have never understood why it did not catch on. Perhaps most people don’t usually use the map to drive the route — the verbal directions tell them where to go more clearly. Perhaps they only have the map to plan routes, not to follow them. The map may be used for reviewing the route before you begin, or re-routing in case of emergency. I’m not sure if any of this is true; it’s just idle speculation. If it is true, though, then LineDrive doesn’t offer any advantages — it doesn’t explain the route any more clearly than verbal directions, and it doesn’t let you do any route planning.
Alas, it died too soon. Microsoft bought MapBlast in 2002 and closed them down. They took the LineDrive technology and kept it going on their own map service, MSN Maps & Directions, until 2005. The site stopped updating in 2005, however, and Microsoft’s subsequent mapping endeavors don’t appear to offer LineDrive as an option.
You can still access the old 2005 site, however, at http://mapblast.com/DirectionsFind.aspx. (EDIT 10/19/11: Microsoft appears to have finally taken MapBlast offline. Maybe traffic from this post reminded them that they’d left it up.) In generating a sample image for this post, I noticed that the database has quite a few holes and errors in it, so I wouldn’t trust the directions it gives. It’s merely a relic of a different era. If you try it, be sure to check out the standard map directions, too, in addition to the LineDrive ones — it’s a nice reminder of just how far online road map design has come in the past few years.
LineDrive was something truly different. MapBlast’s competitors offered a slightly enhanced version of the paper road atlas. MapBlast offered this, too, but they would also give you your own version of a hand-drawn route map for anywhere you wanted to go, at a moment’s notice. I feel like LineDrive made much more effective use of the power computers can bring to cartography than other online mapping services have. It was a more creative re-thinking of what the digital revolution could do for map-making.
I never used to draw route maps by hand; I would simply write verbal directions and bring an atlas. Discovering LineDrive changed that, though. Every long and unfamiliar trip since then has started with me taking pen to paper and sketching out a simple linear cartogram to get me where I want to go.
Let me tell you about how I was saved by maps.
I used to be a chemist some years ago. I worked at a mom & pop pharmaceutical laboratory in my home town of Kalamazoo, Michigan. From the time I was ten or eleven, I had planned on this job. I blame Mr. Wizard — I loved watching all the seemingly magic things he could do with brightly-colored liquids in test tubes. Now that I had my childhood dream job, however, I was disillusioned. There was no magic, there was only routine humdrum. The work was hard, it was stressful, and it was frequently dull. I started the slide into depression. I came home every day feeling far too tired for the number of hours I was working. Time off seemed fleeting, and I spent the whole weekend worried about the fact that Monday was approaching, and wondering sometimes if I could face another week. I felt constantly pursued, and unable to relax even when given respite.
I decided to get out.
I had planned on going to graduate school right after college. I liked being in school and I succeeded there. It seemed natural to continue. But inertia kept me in the workforce for about three years before I finally managed to get enough forward momentum to return to school. My other love in school besides chemistry had been history. I can’t blame Mr. Wizard for this one, but I’ll blame my high school teacher, Mr. Cahow, instead. My bachelor’s degree at Kalamazoo College was in both subjects. At first I tried, and failed, to get in to graduate school to study classical history. The next year, though, I switched focus and applied to History of Science departments. Given my background, it seemed a pretty sensible fit, and the University of Wisconsin agreed. They let me in, and I was off to Madison in the summer of 2007.
Coming along with me was my girlfriend of three years, an amazing and brilliant woman whom I had met in college, and with whom I was very much in love. We got a small apartment together about a mile from campus, she found a job, and we settled in to an unfamiliar city. It was about here that my life started completely unravelling.
I did not fit in to my new graduate department at all. I was wholly out of my depth; my background was insufficient to match the demands of the program. I had gone to graduate school because I liked school, not because I was deeply passionate about the history of science in particular. It just seemed interesting. My peers, on the other hand, seemingly had been pursuing this track for far longer than I, and had put in enough extracurricular effort through their college years that by the time we all started at Madison they were talking over my head. I fell swiftly behind and lost heart. I realize now that while I might have had the relevant skills, I lacked the critical element of passion. I did not feel like spending all week trying to get through 400+ pages of reading, because the end goal was simply not enticing enough, nor was the journey greatly intriguing.
This had been my grand escape plan. My job had depressed me, and I was going to return to school, something I was good at, and I was going to enjoy getting an advanced degree and then spend the rest of my life in academia. My depression returned, much stronger, as this escape plan crumbled away.
My girlfriend, meanwhile, made a bunch of new friends in town, and started spending more and more time with them. Sometimes she wouldn’t come home, or even communicate with me, for days. Eventually, she told me that it was because she didn’t like being around me when I was depressed. She kept getting more distant, and moved into her own separate room. She would have parties at our apartment and introduce me as her “roommate,” and then close me off into one room so that I couldn’t hear what was going on, and so that no one could see me. Then she’d leave for a few days and I’d have to clean up the mess. I did not generally have the wherewithal to stand up for myself in the face of her steadily worsening treatment of me. Her behavior eventually reached the point where I started reading online to determine if I was in an emotionally abusive relationship. None of this helped my depression.
If you’ve never been depressed, I’ll just say that it’s much worse than it sounds, and I imagine everyone manifests it a bit differently. I would stay in bed for hours. I would avoid doing any of my school work. It took a significant effort to scrape together the energy needed to do any sort of housework or cooking. I was constantly bored, but could not muster myself to do anything to make me less bored, and I did not have the courage to face the growing pile of assignments that I was falling behind on. I felt trapped and powerless.
I made a lot of maps during that period; it was one of the only activities that gave me any sort of positive emotion. I had actually started a cartographic hobby a few months earlier, before I moved to Madison. As far back as I can recall, I liked reading maps. I used to be the navigator when my family would take trips. I like paging through atlases for fun. So it was natural enough that I eventually determined to learn a bit about how to make them. One of my first efforts was for Wikipedia, a map of the Kalamazoo River:
I was terribly proud of that map. I still am, despite the many, many flaws I can see in it today.
I kept up my new mapmaking hobby when I moved to Madison. It gave me something creative to do, and I have since learned that, for me, being creative is critical to keeping a positive emotional state. Making maps was the light of my day, in a time when my days were very, very dark. I probably talked more to my colleagues in History of Science about the maps I made than anything actually having to do with my graduate work. I did not construct anything particularly interesting or attractive. Mostly I just put together choropleths of census data to answer idle curiosities. But I was making something, and it felt good. And it involved learning geography, which was fun and new. It was avoidance behavior, to be sure — there were important things I really needed to be doing, and spending eight hours on a map was just a way of procrastinating, but I needed the escape. I could not always face my life outside of my cartographic refuge.
I was still trapped in my ill-fitting graduate program. I was adrift, and didn’t know what to do. I did not thrive as a chemist; I did not thrive as a historian of science. What now? I had no other obvious options, and I considered dropping out of school. But one day a friend of mine in the History of Science department pointed out that, being as I liked maps so much, perhaps I could go to school to learn about them. And, it so happened that there was a first-rate cartography program at Wisconsin. I spent my second semester in graduate school taking a cartography and a GIS class while applying for a transfer to the cartography program. I found that I liked these new classes, and that it was no longer a massive chore to get up every day and try and get to campus and accomplish something. I had more energy. I felt like I had a future. Somehow, despite no background or training, despite a weak performance in History of Science, and despite an application letter that didn’t say much more than “I really like maps,” the University of Wisconsin-Madison Department of Geography accepted me, and I began a Master’s program in Cartography & GIS. They took a chance on me, and I cannot hope to repay them for that.
I threw away everything I had ever thought I wanted to do with my life and leapt blindly into the unknown. I abandoned the safe, clear path I had been plotting since I was a child. As simple as it sounds, that was probably the most courageous thing I’ve ever done in my life.
I thrived immediately in my new program. I found that I was part of something I had lacked before: a community. I was surrounded by supportive friends and colleagues from whom I learned much, and whose input can be seen in everything that I design. I had a place to belong, and a future that I was passionate about. I came out of my depression. I worked up the fortitude to bring about an end to my relationship with my girlfriend, who by now was living on her own yet was unwilling to formally let go. I began to move on from my old life, to the new one I have now. I am a cartographer, and a teacher (another chance that the Geography department took on me). I love what I do. I draw strength from it. It feels like I should have been doing this all along, like I was made for it.
I write this story because I want people to understand what maps mean to me. Cartography is not just a hobby, or a job. It has taken me through the darkest times of my life. It has helped me overcome depression. It has given me a renaissance and a calling. It has given me a community which has enriched me personally and professionally. It has saved me from a life I would prefer not to contemplate, one which I cannot believe would be as fulfilling.
I am very glad that I made that terrible map for Wikipedia, one winter in 2007.
Being as my friends and colleagues over at Axis Maps have met with some success in selling their excellent typographic maps, I thought I would try my had at this whole game of making money on the Internet. So I’ve put up a few of my river maps up for sale. For more info and some images, click here. We’ll see what the future brings. I’m also donating a share of my profits to watershed conservation groups.
A far-off future desire is to expand something like this to encompass the work of others besides myself. I remember I had a student ask me once, “where can I buy cool maps?” I couldn’t really tell her where. There are stores that sell reference maps, of course, but there’s not really a go-to hub for thematic maps, for cartographic art that you’d want to put on your walls. At least, not one I’m aware of. I have friends and colleagues who have put together great designs, and perhaps someday we can unite together to show everyone that maps are more than for getting from A to B, and give them a place to obtain such things. There’s a demand out there for these things, but its fulfillment seems a bit scattered, to me.
Here’s a detail image of one of the maps. To see more images, I’ve set up a page linked here.
Update: I’ve started selling these maps now. For more information (and images), click here.
Lately I’ve been working on a series of river maps, done in the style of Harry Beck‘s famous London Underground design. Not sure why, but it seems like this style of cartogram has become trendy lately. Many people, for example, have tried to apply the technique to the US Interstate system (here, here, here, and here). I thought I would try my hand at it with a different subject.
I don’t think people are used to seeing and thinking about rivers this way — realizing their interconnectedness, their importance in the establishment of settlements, or the fact that they were humanity’s original transit networks. It’s not something I’m ignorant of, but I don’t think about rivers like this regularly. I’ve lived in cities that are on rivers without ever noticing. Rivers are to me are often just those thin blue lines lost in the background of a lot of reference maps.
Putting a map like this together is one long string of semi-arbitrary judgment calls, it turns out, and it’s probably a good experience for any cartographer who is not yet fully comfortable with the whole “generalization and abstraction” thing that is the basis of our art. We have to simplify the world down all the time, and that sort of necessary elimination of detail has always been a bit of a challenge for me.
I’ve made four of these maps so far, and I thought people might be interested in hearing about my process and the decisions I had to make:
I set up a quick base map in ArcMap with rivers, state boundaries, and settlements. I use this as a reference point for my drawing/tracing. Rivers I usually grabbed from either Natural Earth or the National Atlas, depending on the scale I was working at. From there, I usually had to thin the rivers out to something manageable, and my choices there depended on how big an area I was covering and how many I could fit in before things got too busy. This leads to a question, though, of what to call things and how to choose which rivers to include. The longest river in the US is not the Mississippi, but the Lower Mississippi/Missouri/Jefferson/Red Rock, as explained here. The same name doesn’t always get applied to the main branch of a river. I usually looked for the longest stretch of river I could piece together, regardless of how many times it changed names, and went with that (though not always) for my map. If I were making a map of the US with one river, I would have shown the combined longest chain of Mississippi/Missouri/Jefferson/Red Rock, eliminating the part of the Mississippi that goes up into the Midwest, since it’s shorter.
I (usually) called my rivers by all the names they are given along the course. This is why you see ampersands in the example above for river names. Sometimes if a river changes name for just a short stretch (as in the Missouri-Jefferson-Red Rock), I cut off those short stretches to keep things simple (keeping things as just Missouri). I also left of the “river” part of the names, partially because not everything is called a river. Sometimes they’re called creeks, streams, licks, kills, etc. In trying to keep it simply, I just went with the main name of the flowing water feature, not its “type,” which is usually pretty arbitrarily. I also kind of like the way the names come out — “Kanawha & New” sounds like the name of a transit line.
Once I had my rivers picked out, I started by creating the river lines. The hard part here is that I’m constrained to 45 degree angles if I want to keep Beck’s original style — and I do. I like the schematic appearance it has, the conscious geometric relationships established. I have to approximate the river courses as best I can.
If I tried to draw those over again on a different day, I’d probably do them differently. It’s a pretty approximate process, but it’s also rather fun.
Next I put populated places as stops on the river lines. This is probably the hardest part, as far as making judgments goes. What is a populated place? There are cities along rivers, to be sure, and I use a data set of cities and other incorporated places to help me. But there are also a lot of places people live that are less well-defined, places that don’t have a legal name and legal boundary. Places like Republic, Michigan. Those are a lot harder to judge. The Census Bureau helps by defining limits to some unincorporated communities, but that doesn’t cover everywhere.
If I see a settlement along a river, I look at two things: business names and post offices. Does the settlement have a postmark that gives it a name people are used to writing on their mail? Do people name their businesses after what people think the settlement is called? Both of these help me get at the reality on the ground — no matter the legal status of a place, I want to show what people who live there call it, what they think of it as being. I also cross-reference my name choices with Google/Bing Maps, Wikipedia, and the BGN. Sometimes I run in to a settlement where all the businesses, and the post office, name themselves after a larger, nearby town. The people there appear to have less of a separate place identity, so I don’t include them for lack of a name.
I don’t live in all of these places, so it’s a challenge to try and understand how people who live there think about these hundreds of settlements. I may have gotten some wrong, though, if I did, a lot of other cartographers likely did, too, and the people who live there are probably used to it. New England was particularly tricky because most everyone lives in the boundaries of a named, incorporated town, but they also usually live in an unofficially named village within that town.
If you notice in the image above, the tick marks switch which side of the river they’re on. That’s to indicate which side of the river the settlement is on, primarily. Sometimes that’s really clear, but sometimes settlements span both sides of the river. Here again I used Google Maps, to look at satellite photos and street densities and to try and determine where downtown is. Usually the commercial center and civic is clearly on one side of the river or another. If I’m in doubt, I go with the location of the city hall or public library or some other major service building.
The last big choice is: when is a place on a river? Sometimes it’s not clear. Sometimes formal city limits extend to the river banks, but those limits encompass empty land — the actual population center isn’t on the river. Other times cities are separated from the river by their dependent farmlands. I generally included places within a mile or so of the river, counting the population center only, ignoring where the city limits technically went. I tried to imagine what would happen if you stopped your boat along the river’s edge and asked someone where you were. Even if you’re not technically in Greenfield, California, you’re probably close enough that it’s what people will say.
I was more forgiving of settlements being not exactly on the river when there were fewer people around. This is partially because I wanted the put something on empty stretches of river lines, but also because there are fewer answers to “where am I?” when the nearest settlement, three miles away from the river, is the only humanity for twenty miles around. So, sometimes I went out a little farther, up to five miles on rare occasions (Simmesport, LA is not at the confluence of the Red River & the Mississippi exactly, but it’s about the only thing for miles around). But in more densely settled areas, you had to be closer the river to merit inclusion.
Distort the Rivers
Even though the rivers are already a gross oversimplification of the real stream network, more distortions are needed. It’s not possible, usually, to label everything clearly and have all the network connections be unambiguous while keeping the river lines and settlement locations in approximately the right place.
So, I stretch out or shrink certain parts of the river, and move settlements around, to keep everything clear and easy to read. I also move whole river systems around to space them out more clearly. Understanding the connections and relationships is the goal in this design. Spatial accuracy is great, and I try to keep it where I can, but it’s secondary. Also, this part is, again, fun to do.
Lastly, I draw in the boundaries of states and lakes and other area features. I draw them according to where the rivers are, which means that sometimes they get pretty distorted on account of how I had to adjust the rivers (see states in the Mississippi River map above). I also run into interesting situations like this:
The White River weaves across the Missouri-Arkansas border, but when simplifying the rivers down, I kept it straight in that area. In order to make sure that the river and the state borders show the correct relationship, I had to add that little notch to the state border, so that the White travels out of Arkansas, into Missouri, and back into Arkansas again.
I didn’t deal with navigability of the rivers — you can’t actually sail from the source of a river to the mouth, it’s just too shallow in some areas. That would have taken probably way too much research, and I don’t know as it’s the best criterion, anyway. There are plenty of cities on rivers that draw drinking and irrigation water, even if they can’t ship goods down the river, and I think those are important relationships to show.
I went with a blue color scheme, to emphasize water. But then everyone said I should not use so much blue, so I switched the background to more of a blue-green, which you can see in the detail images of the final product linked here. Most everyone seems to agree this is an improvement (though I am still fond of the blue scheme seen in the examples on this page). Several people have also told me they’d prefer that I do these with a wider color range of bright reds and greens and such, like a traditional metro map. I may consider making a variant in the future, but for now I prefer the subtlety.
The type is set in Twentieth Century, a geometric sans designed in the 1930s by Sol Hess. This is a bit of a departure for me. I set most of my work in Century Gothic, which is a 1990s face that draws inspiration from Twentieth Century. This time I decided to try out the source. I think it helps contribute to the feeling of the design being out of the interwar/WWII period. The typeface is of the same era as the original style I’m making an homage to, and they feel like they belong together. Twentieth Century’s design emphasizes geometry — straight lines and simple curved shapes, just like the river lines. I am also overly enamored of the lowercase j and the capital M.
That’s the basics of what I did, and now you know how the sausage is made. It’s been a fun challenge, and I’ve become more comfortable with changing the course of rivers, or eliminating someone’s hometown, with the sweep of a mouse. Getting rid of most of the world’s detail is a necessary part of cartography, but it’s never been one I’m comfortable with. This has helped quite a bit, though.
Any good map is a collaborative effort. My colleagues in the UW Cartography Lab have been most kind in giving me lots and lots of feedback to help me move from one draft to the next. Special thanks go to Isaac Dorsch, who suggested the concentric circles which you can see used above where the river meets the sea (or, in the case of the above, Lake Michigan).