Why maps look different between apps

Not one universal map

Every map is built to answer a chosen set of questions.

An outdoor map may emphasise relief, paths and access. A road map may prioritise street hierarchy, addresses and driving restrictions. A land-management map may foreground boundaries and parcels. When screen space is limited, those priorities determine what appears first and what is omitted.

Two apps can therefore describe the same place honestly while presenting different evidence. One may use national mapping, another a collaborative dataset, and another a mixture of terrain, imagery and specialised layers. The app name does not identify the complete provenance.

What sits underneath

Source coverage and update cycles can diverge.

A map can combine transport, water, place names, elevation, land cover and boundaries from separate datasets. Each layer may have its own survey date, maintenance process, licence and geographic coverage. A seamless visual style can conceal those joins.

Apps also refresh on different schedules. A newly created path may reach one source before another. A building may remain after demolition because the relevant layer is older. Offline tiles may show an earlier snapshot than a live view. Read credits, layer information and dates where they are available.

Absence is ambiguous. A feature might not exist in the source, might be outside the product's remit, might be omitted at the current zoom or might be temporarily hidden by a display rule.

Keep it legible

Zoom changes which detail can survive.

Cartographic generalisation reduces complexity while preserving the features considered important at a particular scale. It is a deliberate part of map-making, not merely a technical failure.

• SelectionSome features are shown while others are left out.
• SimplificationA winding line may use fewer points while retaining its broad course.
• AggregationSeveral small features may become one larger area or symbol.
• ExaggerationA narrow but important feature may be drawn wider than true scale so it remains visible.
• DisplacementA symbol can move slightly to avoid an unreadable collision with neighbouring detail.

Different apps use different thresholds and algorithms for these operations. A detailed path at one zoom can become a simple line or disappear at another. Pinch-zooming a cached raster cannot introduce source detail that was never rendered into that tile.

The visual grammar

Colour, line weight and label order change what attracts attention.

Cartographic styling assigns symbols to data. A path can be solid, dashed or coloured according to attributes and product conventions. Woodland can appear as a tint, pattern or not at all. Contours can be prominent for planning or quiet beneath an active navigation line.

Labels compete for space. Software decides which name has priority, where it can be placed and when it should appear. Layer order decides whether a boundary sits over a land-cover fill or beneath a route overlay. Hill shading and aerial imagery can further change contrast without changing the feature data.

Use disagreement well

Compare evidence instead of voting by appearance.

1. Feature

   Name the exact disagreement.

   Is it geometry, access, surface, name, height, closure or simply the chosen symbol?

2. Source

   Read the layer credits and date.

   A current authoritative source for the question carries more weight than visual polish.

3. Scale

   Compare at an appropriate level of detail.

   One display may be generalised more heavily at the chosen zoom.

4. Ground

   Use current notices and observed conditions.

   No base map settles a live closure or guarantees that a route remains passable.

Keep the saved overlay separate from the base map. A route line and a map path can disagree because they have different origins, and the beacen Library lets you inspect both in context.

Resolve the named disagreement with a source suited to that question; visual polish does not make one map universally authoritative.