Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Cartographic design isn't just about making maps look pretty—it's about effective spatial communication. Every design choice you make influences how users interpret geographic data, from the colors you select to how you classify your data. In Geospatial Engineering, you're being tested on your ability to translate complex spatial information into clear, accurate, and usable visual products. This means understanding visual hierarchy, projection properties, data classification methods, and thematic mapping techniques as interconnected systems, not isolated skills.
The principles covered here form the foundation of every map you'll create or critique. Whether you're designing a web map for public consumption or an analytical product for decision-makers, these concepts determine whether your map communicates truth or introduces confusion. Don't just memorize what each principle does—know when to apply each technique and why certain combinations work better than others for specific purposes.
These principles govern how the human eye and brain process map information. Effective cartography leverages perceptual psychology to guide attention and reduce cognitive load.
Compare: Visual hierarchy vs. balance and composition—both control how users experience the map, but hierarchy focuses on what gets attention while composition addresses where elements sit spatially. FRQ tip: If asked about improving map readability, address both.
Color and symbols are your primary visual vocabulary for representing geographic phenomena. These choices carry inherent meaning and must align with user expectations and data characteristics.
Compare: Legend design vs. scale bar placement—both are marginal elements that support interpretation, but legends decode qualitative symbology while scale bars provide quantitative spatial reference. A map can sometimes omit a north arrow but rarely a legend.
These principles address the fundamental challenge of representing a 3D world on 2D surfaces. Every projection involves tradeoffs, and understanding these tradeoffs is essential for appropriate map selection.
Compare: Projection distortion vs. generalization—both involve acceptable information loss for practical gain. Projections sacrifice geometric accuracy to flatten the Earth; generalization sacrifices detail to improve readability. Know which tradeoffs serve your map's purpose.
How you classify and display data fundamentally shapes what patterns users perceive. Classification choices can reveal or obscure geographic patterns—this is where cartographic ethics meets technical skill.
Compare: Choropleth vs. proportional symbol mapping—both visualize quantitative data, but choropleths work for area-based phenomena (population density) while proportional symbols suit point-based counts (city populations). Using choropleth for raw counts creates the "big polygon" problem where larger areas appear more significant regardless of actual values.
| Concept | Best Examples |
|---|---|
| Perceptual organization | Visual hierarchy, balance and composition |
| Symbol systems | Color theory, legend design, typography |
| Geometric transformation | Map projections, scale and generalization |
| Quantitative display | Data classification, thematic mapping techniques |
| Map furniture | North arrow, scale bar, legend placement |
| Shape preservation | Conformal projections (Mercator, Lambert Conformal Conic) |
| Area preservation | Equal-area projections (Albers, Mollweide) |
| Discrete data visualization | Proportional symbols, dot density |
| Continuous data visualization | Choropleth, isarithmic mapping |
Which two principles both address how users process visual information, and how do their specific functions differ?
You're mapping median household income by county. Which data classification method would you choose if your goal is to show natural groupings in the data, and why might quantiles give a misleading impression?
Compare choropleth and proportional symbol mapping: for what type of data is each most appropriate, and what error occurs when choropleth is used for raw count data?
A map projection preserves shape but dramatically distorts area at high latitudes. What property does this projection have, and what type of mapping task would justify accepting this distortion?
How do visual hierarchy and legend design work together to ensure effective map communication? Describe a scenario where poor legend design undermines an otherwise strong visual hierarchy.