Specific calculators, planners, and explainers for jobs that usually get buried in forums.
Mercator distortion explorer
See how Mercator stretches local map scale as you move away from the equator. Pick a city, type a latitude, or drop a pin on the map to quantify why high-latitude places look so oversized.
What this page answers
A lot of pages say Mercator is distorted, but stop before quantifying it. This page answers the follow-up: how distorted is this latitude, in numbers a normal reader can actually use?
It focuses on the classic search problem behind Greenland-style map arguments: Mercator preserves local shape, but it expands local scale by the secant of latitude, so high-latitude places get drawn far too large in area.
The page now separates two questions people often mix together: what happens to a same-size real-world patch, and what happens to a 1° by 1° latitude/longitude grid cell. Those are not the same object.
It also answers the common follow-up directly: Mercator row heights are not constant on the map. Each 1° latitude band gets farther apart as you move poleward.
Good for
- Explaining why web maps make high-latitude regions feel misleadingly large
- Teaching the difference between local shape preservation and area truth
- Checking how severe Mercator exaggeration is for a city, route, or arbitrary latitude
Important limitation
This page explains Mercator's latitude-driven distortion only. It does not compare every projection family or claim that Mercator is useless; it just makes the main distortion legible.