What the lines mean.

The central principle

Visual precision must never imply more historical certainty than the evidence supports.

How records and sources are chosen

Each published expedition is built from multiple credible references where available. Preference is given to archives, museums, government heritage collections, primary expedition records, scholarly publications, and established reference works.

Sources support chronology, participants, vehicles, places, route interpretation, and historical significance. Atlas does not rely on generated geometry as historical evidence.

Representative routes, not recorded tracks

Editors place historically meaningful waypoints and additional shape points to guide plausible movement. Open-water segments may use geodesic interpolation. Coastal, river, land, mountain, and polar routes use curated points to avoid implausible shortcuts through terrain.

Not every documented stop is encoded. Control points communicate the major shape and phases of a journey without creating false precision.

Dates are only as precise as the record

Atlas preserves whether a date is exact, approximate, inferred, disputed, or unknown. A year-only date is not silently presented as January 1. Where historians disagree about a route or landfall, the catalogue records uncertainty rather than selecting an unsupported exact answer.

Distance and duration

Approximate distances follow the representative generated route. They should not be read as measurements from a complete historical log. Elapsed leg times may include stops, waiting, repairs, seasonal pauses, or periods away from active travel.

Editorial principles

• Write neutrally for a curious general audience.
• Preserve disagreement and uncertainty.
• Avoid false discovery framing for places already inhabited.
• Name contributors when the record supports them.
• Distinguish historical evidence from generated visualization.

How publication is checked

Source records are validated for schema conformance, stable IDs, relationships, chronology, and route geometry. Generated files are deterministic and reviewed alongside their editorial source. Automated validation can catch structural errors, but geographic plausibility and historical interpretation still require human review.

Corrections and feedback

If you find an error, disputed claim, missing source, or implausible route, email urlingsluc@gmail.com. Please identify the relevant record and include a supporting source where possible. Corrections are reviewed before the curated dataset is changed.