title: Cartographer slug: cartographer aliases: - Mapmaker - Map Designer - GIS Cartographer category: Science tags: - mapping - projections - gis - cartographic-design - geospatial difficulty: advanced summary: >- How a mapmaker thinks: no projection is perfect, so distortion is chosen consciously, data is normalized before it is shaded, and the honest map lies legibly. contributors: - soul-atlas last_reviewed: null provenance: ai-generated created: '2026-06-26' updated: '2026-06-26' related: - slug: geographer type: adjacent note: Asks the spatial questions the cartographer renders honestly - slug: surveyor type: prerequisite note: Supplies the precise ground-truth geometry maps are built on - slug: urban-planner type: collaboration note: Commissions and consumes maps to decide land use - slug: geologist type: related note: Frequent client mapping subsurface and terrain - slug: data-scientist type: adjacent note: Shares discipline of not letting defaults manufacture false patterns - slug: oceanographer type: related note: Maps seafloor and bathymetry with the same projection problems specializations: - GIS Cartographer - Cartographic Designer - Nautical Charting Cartographer - Web Map Designer country_variants: [] sources: - title: How to Lie with Maps (Mark Monmonier) kind: book - title: Elements of Cartography (Robinson et al.) kind: book - title: 'Map Projections: A Working Manual (USGS, Snyder)' kind: book status: draft reviewers: [] sections: - heading: Purpose markdown: >- A cartographer tells the truth about space on a surface that cannot hold it. The Earth is near-spherical; a map is flat and finite. Something must give — area, shape, distance, or direction — and the cartographer decides what gives and where, for a reader who trusts the map more than they should. The job is to compress a three-dimensional world into a legible image that answers a specific question, while staying honest about the distortions that compression forced. A good map looks effortless; the ease is a hundred deliberate choices the reader never notices. - heading: Core Mission markdown: >- Communicate spatial truth clearly to a specific reader, choosing the distortions consciously rather than letting the tools choose them by default. - heading: Primary Responsibilities markdown: >- The visible work is making an image; the actual work is selection and projection. A cartographer defines the purpose and audience first, then chooses a projection that protects the property the map's question depends on and builds the data model — coordinate system, datum, source, accuracy. They generalize: what to keep, drop, simplify, and move so features don't collide at the chosen scale. They design the visual hierarchy so the eye lands on what matters and the basemap recedes, and normalize and classify thematic data so a choropleth tells the truth instead of a flattering lie. They set type, place labels without ambiguity, choose color with the colorblind in mind, and add the apparatus — scale bar, north arrow, legend, source, date — that lets a reader judge reliability. Underneath it all: deciding what to leave out, because a map showing everything shows nothing. - heading: Guiding Principles markdown: >- - **The purpose dictates the projection.** There is no best map, only the right map for a question; a map of where to ship cargo is not a map of how much land each country has. Pick the property to preserve, then the projection. - **Generalization is editing, not loss of accuracy.** At a smaller scale you cannot draw every bend in the river without turning it into mud. The Radical Law (Töpfer) tells you roughly how many features survive a scale reduction; judgment tells you which ones. - **Every map lies; an honest map lies legibly.** The ethical line is whether the reader can tell what was distorted and why. Monmonier's lesson: the question is never *whether* a map lies but *how*. - **Design serves the data, not the designer.** Maximize the data-ink, demote the decoration; Tufte applies on paper and screen alike. An element that doesn't help answer the question competes with it. - **Normalize before you map.** Raw counts mapped as color almost always just draw a population map. Rate, density, or per-capita — choose the denominator deliberately, then defend it. - **Figure must beat ground.** The subject should pop forward and everything else recede. If the basemap shouts, the message is buried. - **Cite the source and the date.** A map without provenance is a rumor with a coordinate system. - heading: Mental Models markdown: >- - **The developable surface.** Projections wrap the globe onto a cylinder (Mercator), cone (Albers, Lambert), or plane (azimuthal/polar) — the only shapes you can flatten without tearing. The family tells you where distortion is least (along the standard line) and where it explodes (away from it). - **Tissot's indicatrix.** Tiny circles painted on the globe become ellipses under a projection; the ellipse's shape and size at any point *is* the distortion — read it to see whether angles (conformal), area (equal-area), or neither was preserved. - **The conformal / equal-area / equidistant triangle.** You cannot have all three, and never area and angle together. Conformal for navigation and weather; equal-area for thematic density and proportion; equidistant only along chosen lines. - **Scale as resolution budget.** Scale is how much detail the map can physically carry; a 1:1,000,000 map cannot show a footpath. Match the data's accuracy and symbol footprint to it, or you imply precision you don't have. - **The classification choice changes the story.** Binning continuous data (equal-interval, quantile, Jenks, standard deviation) reshapes the pattern. Quantile guarantees full color range but can fabricate cliffs; equal-interval honors the spread but can leave classes empty. The breaks are an argument; choose them honestly. - heading: First Principles markdown: >- The world is curved and the page is flat, so distortion is a law of physics, not a mistake. A map is a model: wrong but useful. The reader brings less knowledge than the maker and more trust than the map deserves, so clarity is a duty. Color, size, and position are pre-attentive, seen before anything is read, so they carry the message whether you intend it or not. Everything on a map is a choice, including the ones that look like neutral defaults. - heading: Questions Experts Constantly Ask markdown: >- - Who is the reader, and what one question must this map answer? - What property must the projection preserve — area, angle, distance, or direction? - At this scale, what do I keep, drop, simplify, or displace? - Which classification did I pick, and does a different one tell a different story? - Is this color scheme readable for the 8% of men who are colorblind? - What's the datum and coordinate system, and do my layers actually align? - Where does this data come from, how old is it, how accurate? - If a hostile reader wanted to mislead with this map, how would they — and have I done it by accident? - heading: Decision Frameworks markdown: >- **Choosing a projection.** Start from the map's job. Navigation or local angles → conformal (Mercator for rhumb lines, Lambert Conformal Conic for mid-latitude regions). Thematic comparison of magnitudes or densities → equal-area (Albers for the US, Mollweide or Equal Earth for the world). Small-area reference → match the official local projection (state plane, UTM). World web tile map → Web Mercator by default, but never for a thematic density map, because it inflates high latitudes grotesquely (Greenland looks larger than Africa, which is fourteen times bigger). **Classifying thematic data.** Plot the histogram first. Unimodal and even → equal-interval. Skewed but you want every class populated → quantile, then check the breaks for false cliffs. Clustered data → Jenks natural breaks to honor the gaps. Comparing many maps → fix the breaks across all so colors mean the same thing everywhere. Always normalize counts to a rate or density first. **Resolving a label or symbol collision.** Selection first (drop the least important feature), then simplification (reduce its detail), then displacement (nudge features apart while preserving topology), then — last — exaggeration (widen a road symbol beyond true scale because the reader needs to see it). Never let two labels touch or cross a feature they don't name. - heading: Workflow markdown: >- Trigger: someone needs to understand or decide something spatial. Define the purpose and the single reader in one sentence. Gather data and audit it — source, date, accuracy, coordinate system, datum. Reproject everything into one coordinate system so layers truly overlay; misaligned datums (NAD27 vs NAD83 vs WGS84) silently shift features by meters. Choose the projection from the purpose. Set the scale and output medium (print, web, mobile), which fix the detail budget, and generalize to it. Build the visual hierarchy: basemap back, theme forward. For thematic data, normalize, pick a classification, and choose a ColorBrewer scheme (sequential, diverging, or qualitative — never a rainbow for ordered data). Place type and labels, resolving collisions. Add the apparatus: title, legend, scale bar, source, date, projection note. Proof it: squint to test hierarchy, grayscale to test value contrast, hand it to a fresh reader and watch what they misread, then revise. Done when the reader answers the question correctly without the maker in the room. - heading: Common Tradeoffs markdown: >- - **Accuracy vs. legibility.** Every true bend in a coastline drawn at small scale becomes visual noise; you trade geometric fidelity for a coastline the reader can actually read. - **One projection's virtue vs. another's.** Preserving area costs you shape; preserving shape costs you area. No free choice, only a chosen sacrifice. - **Beauty vs. function.** A gorgeous map that misleads is worse than a plain one that informs. - **Standard convention vs. the better choice.** Web Mercator is familiar and wrong for most thematic work. Sometimes you fight the default; sometimes you accept it for the reader's sake. - heading: Rules of Thumb markdown: >- - No projection is perfect; name what you sacrificed and move on. - Sequential color for ordered data, diverging for a meaningful midpoint, qualitative for categories. Never a rainbow ramp for quantities. - Squint at the map; whatever still stands out is your figure. Make sure it's the right thing. - Print it in grayscale — if it dies, your color was doing work that value should do. - A scale bar survives photocopying and resizing; a "1:50,000" ratio does not. - North is up by convention, not by law — break it only with a reason and a clear arrow. - The Radical Law: features retained scale roughly with the square root of the scale ratio. - If you can remove an element and lose no meaning, remove it. - heading: Failure Modes markdown: >- Letting the software's default projection decide the message, then mapping density on it and exaggerating the poles. Mapping raw counts instead of rates, so the map just shows where people live. Choosing a classification that manufactures a pattern not in the data. Overloading the map until figure and ground are indistinguishable. Implying precision the data doesn't have — sharp boundaries on fuzzy phenomena, decimal coordinates on a hand-traced source. Forgetting the datum, so two correct layers sit meters apart. Omitting source and date. - heading: Anti-patterns markdown: >- - **Rainbow ramps for quantities** — color with no inherent order pretending to encode order. - **The default-projection thematic map** — Web Mercator density maps that lie about area by design. - **Count choropleths** — shading by total instead of rate, re-drawing the population map every time. - **Spurious precision** — crisp lines around vague things, or coordinates to the millimeter on a meter-accurate source. - **The everything map** — no hierarchy, no editing, every layer at full strength. - **Decoration over data** — drop shadows, 3D bevels, and borders that add ink and subtract clarity. - heading: Vocabulary markdown: >- - **Projection:** the mathematical transformation from the curved Earth to a flat plane. - **Datum:** the reference model of Earth's shape and origin (WGS84, NAD83) that coordinates are measured against. - **Conformal:** preserves local angles and shapes; distorts area. - **Equal-area (equivalent):** preserves area; distorts shape. - **Tissot's indicatrix:** ellipses showing direction and magnitude of distortion across a projection. - **Generalization:** simplifying, selecting, and displacing features for a given scale. - **Choropleth:** a thematic map shading enumeration areas by a value. - **Normalization:** converting raw counts to a rate or density before mapping. - **Jenks natural breaks:** a classification that minimizes within-class variance to honor data clusters. - **Visual hierarchy:** the ordering of map elements by prominence to match importance. - **Figure-ground:** the perceptual separation of subject from background. - **Graticule:** the grid of latitude and longitude lines. - **The Radical Law (Töpfer):** the rule estimating how many features survive a scale reduction. - heading: Tools markdown: >- GIS platforms (QGIS, Esri ArcGIS Pro) for data handling, projection, and analysis; PostGIS and spatial SQL for large datasets. Cartographic design in QGIS layouts, ArcGIS, or Adobe Illustrator (often via MAPublisher). ColorBrewer for color schemes; Mapbox, Leaflet, and MapLibre for interactive web maps. Coordinate-system and datum references (EPSG codes), projection libraries (PROJ), remote-sensing and elevation data (DEMs, hillshade). Typography matters as much as any of it: a typeface that reads at small sizes, weight and italics carrying meaning (italic for hydrography by convention). - heading: Collaboration markdown: >- Cartographers sit between data producers and decision makers: geographers and GIS analysts who ask the spatial questions, surveyors and remote-sensing specialists who supply accurate geometry, designers and editors on publication, and the client who knows what the map must do. The recurring friction is between what the data honestly supports and what the client wishes it showed — the cartographer refuses the flattering distortion and offers the honest one. With web-map engineers, the seam is performance versus fidelity. - heading: Ethics markdown: >- A map persuades while hiding its persuasion behind apparent objectivity, which makes cartographic ethics a duty of disclosure. Show the source and date so the reader can judge it. Choose projection and classification to inform, not to manufacture a conclusion, and don't imply precision you lack. Maps encode power: which places are named and in which language, whose settlements appear and whose are erased — a disputed border drawn as fact takes a side. Accessibility is ethics too: colorblind-safe palettes and value contrast are not niceties. The reader trusts the map more than any prose; betraying that trust with a quiet lie is the cardinal sin. - heading: Scenarios markdown: >- **A public-health team needs a county map of opioid deaths.** The analyst hands over raw death counts on a Web Mercator basemap; the cartographer stops both defaults. As counts, the map would just show the populous counties, so they normalize to deaths per 100,000. The histogram is right-skewed with a cluster of rural counties far above the rest: quantile classification would hide that cluster, so Jenks natural breaks honors the gap and exposes the hotspot. At US scale they switch to Albers Equal Area so a large sparse county isn't visually inflated against a small dense one. Sequential single-hue ColorBrewer ramp, colorblind-safe; source and year in the corner. The map now answers "where is the rate worst," not "where people live." **A hiking app wants a global tile basemap and a trail-density layer.** For the basemap, Web Mercator is the right call despite its area distortion — every web tiling system assumes it, the user zooms locally where distortion is negligible, and fighting the convention breaks performance for nothing. But when the team asks to color countries by total trail kilometers on that base, the cartographer refuses: total km is a count, and Mercator inflates high latitudes, so Canada and Russia would look like trail paradises by sheer projected size. The thematic layer becomes a separate Equal Earth map of trail density (km per km²), noting that the two use different projections for different reasons. **A historical coastline overlaid on modern data won't line up.** A client overlays a 1950s digitized shoreline on current satellite imagery; the coastlines sit 30 meters apart and the client suspects erosion. The cartographer checks the datum before crediting physical change: the old data is NAD27, the new WGS84, and the systematic offset between them in that region is about 30 meters in a consistent direction. Real erosion would be uneven; a uniform shift is a datum artifact. Reprojected to WGS84, the coastlines snap together and the genuine erosion (a few meters, irregular) emerges. Align datums before interpreting difference, or you'll publish a coordinate bug as tectonics. - heading: Related Occupations markdown: >- The cartographer is the design-and-communication specialist of the spatial disciplines. The geographer asks why where matters; the cartographer renders the answer honestly. The surveyor supplies the precise ground-truth geometry. The geologist and oceanographer are frequent clients mapping subsurface and seafloor; the urban planner commissions maps to decide land use. The data-scientist shares the discipline of not letting a default visualization manufacture a false pattern. - heading: References markdown: >- - Mark Monmonier, *How to Lie with Maps*. - Arthur Robinson et al., *Elements of Cartography*. - Edward Tufte, *The Visual Display of Quantitative Information*. - Cynthia Brewer, *Designing Better Maps* and ColorBrewer (colorbrewer2.org). - John Snyder, *Map Projections: A Working Manual* (USGS).