Quick Geography Cheat Sheet

What This Actually Is

A Quick Geography Cheat Sheet is basically a condensed reference document you keep on hand when you're working with location data, mapping, or spatial analysis. Think of it as the thing you tape to your monitor during a project instead of flipping through a textbook. It covers coordinate systems, datums, scale conversions, projection quirks, and the kind of constants you end up looking up every time anyway. I started making my own version around 2014 when I was dealing with a surveying contract that required jumping between NAD83, WGS84, and a bunch of state plane zones. Every time I switched projections I was pulling the same three numbers from memory and wasting twenty minutes. I compiled everything into a single page and it cut my setup time down to roughly five minutes per session.

Quick Geography Cheat Sheet — Core Contents

Coordinate Systems

You need to know the difference between geographic (lat/lon) and projected (meters/feet on a flat plane) coordinates. The cheat sheet should list the major ones: WGS84, NAD83, ED50, and the State Plane zones if you're working in North America. Also include EPSG codes because nobody wants to search for "what code is Web Mercator" mid-deadline.

Map Projections

This is where most people get burned. A Quick Geography Cheat Sheet should summarize the common projections — Mercator, Transverse Mercator, Albers Equal Area, Robinson — and note what each distorts. Direction, area, distance, or shape. Mercator preserves direction but makes Greenland look bigger than Africa. That's basic, but I still see people use it for thematic maps and wonder why the results are misleading.

Scale and Distance

Convert between different units cleanly. Kilometers to miles, meters to feet, degrees to nautical miles. Include the formula for approximate great-circle distance using the haversine method. You don't need the full derivation on the sheet, just the equation and a note that it assumes a spherical Earth. For anything requiring centimeter-level accuracy, you'd use a geodesic calculator instead, but for rough estimates the haversine works fine across most contexts.

Datums and Geoids

A datum defines the shape of the Earth for measurement purposes. WGS84 uses a specific ellipsoid. NAD83 is similar but has subtle differences that show up when you're working at high precision. The cheat sheet should note the typical offset ranges — usually within a couple of meters between WGS84 and NAD83 in most regions, but sometimes more near tectonic boundaries.

How to Build One That Actually Works

Start with blank paper or a blank document. Don't download someone else's. The process of writing it out is what makes it stick. I found that when I was prepping for fieldwork I could pull the sheet out and verify my calculations in under a minute. Copying someone else's version meant I'd memorize nothing. Group related items together. Put projections next to their distortions. Put coordinate systems next to their EPSG codes. A Quick Geography Cheat Sheet that's alphabetized by topic is harder to scan than one organized by use case. I layout mine in four quadrants: coordinate basics, projections, conversions, and common pitfalls. Include at least one worked example per section. When I was learning GIS I kept forgetting whether to input latitude or longitude first in WGS84 format. Writing out "WGS84: 40.7128° N, 74.0060° W (latitude first)" on the sheet made that clear permanently.

A Problem I Ran Into and How I Fixed It

Around 2018 I was working on a coastal mapping project and the team handed me shapefiles in an unknown projection. The metadata was empty. I spent an hour trying to match the coordinates to known state plane zones before realizing the data was in NAD27, not NAD83, and had been digitized from paper surveys without a proper transformation applied. My workaround was straightforward. I added a section to the cheat sheet specifically for "diagnosing unknown projections." It included a checklist: check the coordinate range against known zones, look for rounding patterns that suggest imperial units, compare known control points against published datasets, and when all else fails, test a few transformations and see which one aligns best. It took me maybe twelve minutes now instead of an hour. The key insight is that projection problems are usually solvable if you know what questions to ask the data first.

Common Mistakes Beginners Make

Using Web Mercator for area measurements. It's everywhere because Google Maps and OpenStreetMap use it, but the distortion grows rapidly as you move away from the equator. At 60 degrees latitude the scale error is around forty percent. If you need actual area calculations, use an equal-area projection like Albers or a local State Plane zone. Assuming GPS coordinates are always WGS84. Most consumer devices report WGS84, but some industrial GNSS receivers let you choose the output datum. I've seen data come in on NAD83(HARN) and people treated it as WGS84 without checking. The positional difference can be significant depending on your state and when the survey was captured. Forgetting about vertical datums. If your work involves elevation — flood modeling, construction, aviation — horizontal accuracy means nothing if your vertical datum is off. NAVD88 and EGM96 are the common ones in the US. The sheet should note the typical offset between them.

What to Download and Where

There are a few community-maintained versions floating around geography and GIS forums. The one I find most useful covers both academic and field applications. It includes the haversine approximation, a full State Plane zone reference, and common EPSG codes. You can find it on GitHub under open-source GIS resources or on the GIS Stack Exchange wiki. The file is usually a PDF, around two pages when printed double-sided. If you can't find one that matches your workflow, building your own from the structure I outlined above will serve you better long-term. The ones I've downloaded from others tend to become outdated as new EPSG codes get added or deprecated. A personal version stays current because you update it as you learn.

When a Cheat Sheet Won't Help

If you're doing multi-crustal geodetic surveying or working with ITRF2020 frames, a one-page summary isn't going to cover the transforms you need. In those cases you're better off using specialized tools like PROJ, GDAL, or the NOAA NGS online coordinate conversion utilities. The cheat sheet is a field reference, not a replacement for proper geodetic software. Similarly, if you're working in regions with unusual datums — parts of Russia, China, or India where local datums dominate — the standard WGS84/NAD83 entries won't be sufficient. You'll need to supplement the sheet with local datum parameters or build a region-specific version.