Map Sources

Each publication below supports a specific subset of the records. Open the reference attached to a location to inspect its context. These map sources are not game telemetry, a coordinate feed or evidence that the publisher endorses the atlas. We retain stable record identifiers so a correction can refer to the same entry after its note changes.

A reference is not a surveyed position

The map sources provide names and short descriptions. Our drawing provides a readable workspace for the checklist. Those are separate layers of information: a correctly named landmark can still have an illustrative position on this diagram. Do not infer real distance, elevation or a traversable connection from the placement of two markers.

The area labels are organizational descriptions chosen for this preview. They are not a complete or official set of in-game subregions. Similarly, the completion bar measures only this collection. Finishing every included record says nothing about collectibles that have not been added to the atlas.

Conflicting references need context

Compare the relevant paragraph, game version, visit and access requirement before treating different notes as a contradiction. A guide may describe a later return while another describes a first visit. The map sources should be read in their original context; a short card cannot carry every progression assumption.

We do not silently average incompatible totals or invent a precise location when evidence is missing. The appropriate next step is a correction report with the affected record and a reference another person can inspect. An unresolved discrepancy should remain an uncertainty until it can be checked.

Trace one entry through the source ledger

Start with a location in the list and open its detail card. Record the stable identifier from its share link, then follow the source attached to that same card. This keeps the comparison tied to one entry instead of a similarly named place. Read the relevant section in context and separate its name, directions and access conditions before proposing any edit.

Next, compare the brief note with the linked passage. If the note omits a condition, describe that omission precisely. If you cannot identify the relevant passage, record that uncertainty instead of assuming the entry is confirmed. This process reviews attribution and wording only: it does not verify the diagram’s geometry. A checklist mark records your own progress and never changes the evidence label for other visitors.

What a future verification record needs

Before an entry can be described as independently verified, its name, access condition and position need supporting observations from the game. A meaningful record would identify the version, the point of reference and the evidence used to place the marker. A publication date alone cannot establish that a coordinate was measured.

A replacement base map also needs a clear usage basis and a coordinate system compatible with the recorded positions. The existing map sources do not grant a license to copy entire images or databases. Our original SVG is a schematic and must continue to be labelled that way until a properly checked replacement is available.