Making Maps: a Visual Guide to Map Design for GIS, Second Edition

Making Maps: a Visual Guide to Map Design for GIS, Second Edition

This is a chapter excerpt from Guilford Publications. Making Maps: A Visual Guide to Map Design for GIS, Second Edition. By John Krygier and Denis Wood. Copyright © 2011. Purchase this book now: www.guilford.com/p/krygier In December 1986 an experimental aircraft named Voyager became the first piloted aircraft to circle the earth without refueling. DAY 9 DAY 8 DAY 7 DAY 6 DAY 5 Hours 216 200 192 184 176 168 160 152 144 136 128 120 112 104 96 Aloft hours hours hours hours hours hours Fuel on landing: 18 gallons 100° W 60° W 20° W 0° 20° E 60° E United States 40° N Triumphant landing at Edwards AFB WNW WorriedPress about flying Atlantic Ocean Passing between through restricted two mountains, airspace, Rutan and NNW Rutan and Yeager 20° N ENE Oil warning Yeager mistake the 20 18 weep with relief morning star for Engine stalled; ESE light goes on Coolant 14 at having survived a hostile aircraft unable to restart Nicaragua Africa’s storms seal leak Rutan disabled Ethiopia W for five harrowing Costa Rica E NW by exhaustion E 10-20 Somalia minutes 10-15 34 Cameroon Uganda 0° Transition E Gabon Squall line from tailwinds 20 Congo Kenya Zaire Tanzania to headwinds E ThunderstormGuilford 37 forces Voyager Discovery Flying among of backwards into 90° bank fuel flow Pacific Ocean ‘the redwoods’: 20° S life and death struggle to avoid TheAtlantic Ocean towering thunderstorms 40° S 120° W 80° W 40° W 0° 40° E Visibility 2011 20,000 15,000 © 10,000 (feet) 5,000 Altitude sea level Distance 26,678 miles traveled 5,000 miles to go 10,000 miles to go 12,532 miles previous record Flight data courtesy of Len Snellman and Larry Burch, Voyager meteorologists Mapped by David DiBiase and John Krygier, Department of Geography, University of Wisconsin-Madison, 1987 Copyright DAY 4 DAY 3 DAY 2 DAY 1 96 8088 72 64 56 48 40 32 24 16 8 Take­ Hours hours hours hours hours off Aloft Fuel on takeoff: 1,168 gallons 60° E 100° E 140° E 180° 140° W United States Dramatic takeoff; wingtips scraped off 40° N Edwards Voyager flies AFB between feeder band Press NNE and main storm to 28 maximize tailwinds NW India NE 15 33 Rendezvous team Autopilot 20° N Coolant not permitted failure ENE to take off Thailand Philippines ENE 20 seal leak SE 15 W Vietnam 12 Impromptu rendezvous Sri Lanka Typhoon E with chase plane 15 Marge Pacific Ocean Squall line E 22 SE Voyager squeezes 0° 24 between restricted Vietnamese airspace Guilford and thunderstorms Indian Ocean THE FLIGHT OF VOYAGER December 14-23, 1986 20° S Wind speed, NE Mercator map projection Thedirection, 10 Scale at equator is & cloud cover 1:43,000,000 80° E 120° E 160° E 160° W 120° W 2011 40° S Visibility 20,000 Altitude © 15,000 (feet) 10,000 5,000 sea level 15,000 miles to go 20,000 miles to go Take- off Distance Voyager pilots: Dick Rutan and Jeana Yeager Voyager designer: Burt Rutan Copyright What do you need to know to make this map? Whom was this map made for? Who is its audience? Why is the latitude/longitude Where is the rest of the world? grid only on the water? Where did the flight path and meteorological data for the Why are some, but not all, map come from? country names on the map? DAY 9 DAY 8 DAY 7 DAY 6 DAY 5 Hours 216 200 192 184 176 168 160 152 144 136 128 120 112 104 96 Aloft hours hours hours hours hours hours Fuel on landing: 18 gallons 100° W 60° W 20° W 0° 20° E 60° E United States 40° N Triumphant landing at Edwards AFB WNW WorriedPress about flying Atlantic Ocean Passing between through restricted two mountains, airspace, Rutan and NNW Rutan and Yeager 20° N ENE Oil warning Yeager mistake the 20 18 weep with relief morning star for Engine stalled; ESE light goes on Coolant 14 at having survived a hostile aircraft unable to restart Nicaragua Africa’s storms seal leak Rutan disabled Ethiopia W for five harrowing Costa Rica E NW by exhaustion E 10-20 Somalia minutes 10-15 34 Cameroon Uganda 0° Transition E Gabon Squall line from tailwinds 20 Congo Kenya Zaire Tanzania to headwinds E ThunderstormGuilford 37 forces Voyager Discovery Flying among of backwards into 90° bank fuel flow Pacific Ocean ‘the redwoods’: 20° S life and death struggle to avoid TheAtlantic Ocean towering thunderstorms 40° S 120° W 80° W 40° W 0° 40° E 2011 Visibility 20,000 15,000 © 10,000 (feet) 5,000 Altitude sea level Distance 26,678 miles traveled 5,000 miles to go 10,000 miles to go 12,532 miles previous record Flight data courtesy of Len Snellman and Larry Burch, Voyager meteorologists Mapped by David DiBiase and John Krygier, Department of Geography, University of Wisconsin-Madison, 1987 How were these symbols Why is the ocean type chosen? What typeCopyright font is this, and italicized? why was it chosen? How was this map created? Was this map created to be On the computer? What kind shown in a book? On the of software was used? web? On a sheet of paper? Why isn’t there color on the map? Would color make the Isn’t every map supposed to map better? Why are the days running have a north arrow? backwards on the map? Where did data for the storms and typhoons come from? Why is this line darker than other lines on the map? DAY 4 DAY 3 DAY 2 DAY 1 96 8088 72 64 56 48 40 32 24 16 8 Take­ Hours hours hours hours hours off Aloft Fuel on takeoff: 1,168 gallons 60° E 100° E 140° E 180° 140° W United States Dramatic takeoff; wingtips scraped off 40° N Edwards Voyager flies AFB between feeder band PressNNE and main storm to 28 maximize tailwinds NW India NE 15 33 Rendezvous team Autopilot 20° N Coolant not permitted failure ENE to take off Thailand Philippines ENE 20 seal leak SE 15 W Vietnam 12 Impromptu rendezvous Sri Lanka Typhoon E with chase plane 15 Marge Pacific Ocean Squall line E 22 SE Voyager squeezes 0° 24 between restricted Vietnamese airspace Guilford and thunderstorms Indian Ocean THE FLIGHT OF VOYAGER December 14-23, 1986 20° S Wind speed, NE Mercator map projection Thedirection, 10 Scale at equator is & cloud cover 1:43,000,000 80° E 120° E 160° E 160° W 120° W 2011 40° S Visibility 20,000 Altitude © 15,000 (feet) 10,000 5,000 sea level 15,000 miles to go 20,000 miles to go Take- off Distance Voyager pilots: Dick Rutan and Jeana Yeager Voyager designer: Burt Rutan Copyright CHAPTER How to Make a Map Start1 by looking; what do you see? Looking at maps is easy. Not really. You can glance at the Mona Lisa in a second. But to get the Mona Lisa you have to look more carefully. What do you see on the Voyager map? Words, lines, continents, a grid. A story, some information with the story. What do you notice first? Black lines, gray lines, white lines ... why are they different? Making maps requires that you answer such questions, and many more. Throughout this book, in nearly every chapter, we annotate The Flight of Voyager. By the end of the book, you will understand how to really see – and make – a map. 5 Making Maps is Hard Whether looking at or making maps, there is a lot to see, think about, and do. Throughout this book, myriad subjects are considered in general and in relation to The Flight of Voyager map. A systematic critique of an existing map or the successful making of your own map is accomplished by considering the following issues. When making maps, think about everything before starting; then, when your map is complete, reconsider them all once again. The Whole Map The Map’s Data Write out exactly what the map is supposed to Do the data serve the goals of the map? accomplish: does the map meet its goals? Is the relationship between the data and the Are you sure a map is necessary? phenomena they are based on Pressclear? Is the map suitable for the intended audience? Does the map symbolization reflect the character Will the audience be confused, bored, interested, of the phenomena or the character of the data? or informed? Does the origin of the data – primary, secondary, Look at the map in its final medium: does it tertiary – have any implications? work? Has the potential of a black-and-white Are the data too generalized or too complex, or color design been reached? given the map’s goals ? Is the map, its authors, its data, and any other Guilford Is the map maker’s interpretation of the data relevant information documented and accessible sound? to the map reader? Are qualitative and quantitative characteristics Look at the map and assess what you see; is it: Theof the data effectively symbolized? confusing or clear Have the data been properly derived? interesting or boring lopsided or balanced Has the temporal character of the data been amorphous or structured 2011 properly understood and symbolized? light or dark Is the scale of the map (and inset) adequate, neat or sloppy given the goals of the map? fragmented or coherent © constrained or lavish What about the accuracy of the data? Are the crude or elegant facts complete? Are things where they should random or ordered be? Does detail vary? When were the data modern or traditional collected? Are they from a trustworthy source? hard or soft Have you consulted metadata (data about data)? crowded or empty bold or timid Does the map maker document copyright issues tentativeCopyright or finished related to the data? free or bounded Is the map copyright or copyleft licensed? subtle or blatant flexible or rigid The Map’s Framework high or low contrast authoritative or unauthoratative What are the characteristics of the map’s complex or simple projection, and is it appropriate for the data appropriate or inappropriate and map goals? What is distorted? Given the goals of the map, are any of these Is the coordinate system appropriate and noted impressions inappropriate?

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    12 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us