Readers can rarely tell one projection from another by eye, so the caption has to say which

What it is

The projection determines the credibility structure of every area, distance, and shape on the map, yet readers can barely identify the projection from the map face—distinguishing an equal-area world map from a Mercator one requires geographic knowledge. So the projection must travel with the map as explicit information (caption, footnote, or hover info): an entry point for readers capable of verification, and the chart maker's honesty marker declaring "I know where the distortion is." An unlabeled projection hides the choice in the dark, leaving readers unable to assess the distortion's impact on their question.

Why it happens

Labeling works like data provenance (the same family's source labeling): the projection is the map's "coordinate-system scope," the conversion note that lets readers translate on-map impressions back into true geographic relations. The minimally sufficient label is the projection name plus a fitness note—"Projection: Albers equal-area conic (standard parallels 25°/47°)" or "Web Mercator (areas inflated at high latitudes)"; more important than the name is the distortion hint: area-bearing comparisons on non-equal-area projections must state the distortion direction, and equal-area maps should note shape distortion. Labeling's second function is reproducibility: with the projection and parameters known, others can reproduce the map, verify area computations, or reproject data into the same system for comparison—spatial data without projection information is like numbers without units. In engineering terms, the label can be auto-generated (projection parameters are known in the render configuration) at negligible cost; missing labels usually reflect "the projection was never consciously chosen" rather than "labeling is hard"—which is precisely the label's value as a quality signal.

Where it stops holding

Label depth grades with the map's evidentiary stakes: interactive basemaps (for browsing) may state the projection only in an "about" panel; static maps carrying analytical conclusions must label in the caption. Technical naming (EPSG codes) is precise for experts but opaque to the public—public-facing maps should pair plain-language statements ("areas shown true to scale") with the professional name. A label does not eliminate distortion—it must not become a liability shield where "we labeled it, so we're fine"; the projection choice itself still needs to follow the same group's channel-matching principle. Labeling makes the choice transparent, and transparency becomes a verifiable fact.

Applying it

• Build a projection-label field into map templates, auto-filled at render time with the projection name and key parameters.
• When a non-equal-area projection hosts area comparisons, append a distortion note to the caption ("Mercator projection; areas inflated at high latitudes").
• Carry the projection label through exports and screenshots so out-of-context circulation remains verifiable.
• Verification: sample outward-published maps and check whether the caption answers "which projection, and where is the distortion?"; if not, labeling is missing.

Related

• Same group: U12.01.1 No planar projection can preserve area, angles, and distances simultaneously · U12.01.2 Area-type maps must use an equal-area projection · U12.01.3 The Mercator projection severely inflates areas at high latitudes · U12.01.4 Projection choice must change with the map's coverage
• Nearby: U8.07.2 Data source and update time must accompany the chart · U12.01.4 Projection choice must change with the map's coverage
• Search terms: projection caption · EPSG · map metadata