# Keep geographical reading notes in Book Isle: distinguish shared names, older names and mapped features

Language: en
Canonical: [Keep geographical reading notes in Book Isle: distinguish shared names, older names and mapped features](<https://allluckly.cn/en/guides/nasbook-map-place-identity-notes/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-map-place-identity-notes/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-map-place-identity-notes/>)
Published: 2026-11-04T00:00:00+08:00
Modified: 2026-11-04T09:36:55+08:00
Author: Bison

Trace one place name through feature type, period, neighbours and map edition instead of assuming identical names identify one place.

English translation of the [Chinese original](<https://allluckly.cn/guides/nasbook-map-place-identity-notes/>), translated on 2026-11-04. Original publication dates, attribution, code and version notes are retained.

One name can identify a town, river or administrative area, and old map names need not map one-to-one onto today’s names. Use Book Isle to trace a passage, illustration and legend to trustworthy maps or place-name resources. This is neither navigation nor judgement on real boundaries. Establish what this occurrence means, in what period and with what uncertainty, before inserting a modern search result into historical prose.

## Start with one located occurrence

Choose one place-name occurrence in authorised geography, travel or historical material, retaining surrounding prose and illustration notes. Record title, edition, section and anchor text and bookmark it. Define the task as place identity rather than knowledge of the whole region. Choose one traceable object when a chapter contains many names. Do not accept the first name-search result before reading constraints already in the source, such as bank, direction or period. Those conditions determine which result actually corresponds.

## Identify the feature type first

Record original spelling separately from feature type: town, mountain, river, island or region. For the explicitly fictional “South River,” inspect verbs and neighbours to see whether the text crosses a river, enters a settlement or discusses an administrative area. Identical names do not merge different feature types, and a map label may designate another object. Mark unclear type unresolved and preserve spelling rather than adding a city or province suffix to appear specific. A more definite interpretation than the text creates an error.

## Separate name variants from identity

List source name, translation, older name and modern search term separately with their origins. Similar spelling is only a candidate, not a confirmed alias. Verify translator or index mappings at their source rather than pronunciation alone. Retain same-name candidates separately with distinguishing clues instead of forcing their notes together. Book Isle search finds text, not automatic geographical disambiguation. Plain paragraphs can form a small checklist without a specialised map database or automatically generated location links.

## Record period and geographical extent together

Separate the period discussed, map compilation date and your reading date. A historical name may cover a broad extent rather than one modern point. Check whether the book defines its contemporary administrative or geographic range; do not draw a definite boundary when absent. A travel stop may be constrained by a nearby river or preceding stop without becoming a whole modern region. Preserve approximate period wording. Tidy notes must not turn uncertain identity into one precise location.

## Check map title, legend and edition

Inspect map title, legend, direction marker, scale and caption date. A place may appear only on a local map whose symbols cannot automatically be interpreted through another page’s overview legend. Retain figure number and book location rather than cropping off margins that hold edition and extent. Manually enlarge scans without assuming labels are searchable. Obtain a clearer reliable original or same-edition image when unreadable instead of guessing a name into your identity note. Clear display and correct interpretation are separate tasks.

## Test candidates through neighbouring relationships

Compare candidates against neighbouring features, preceding/following route stops, direction and route sequence, seeking at least two independent visible clues. Retain conflict rather than force a similar name into place. A clearly labelled invented east-bank same-name town versus west-bank bridge can test whether notes preserve both type and relation, but is not real geographical evidence. Actual passages and maps must be checked together. A larger candidate list is not stronger proof; identify which candidates satisfy the text’s conditions.

## Keep scale and coordinates with their definitions

Before comparing distance, establish whether the scale belongs to the original map or resized copy; a centimetre on a phone screen cannot directly become ground distance. Retain visible coordinate format, coordinate system and datum information before external comparison, rather than equating numbers from different systems. Mark missing definitions unconfirmed instead of using extra decimal places to imply precision. This is reading verification, not travel guidance. USGS supplies technical background, but the particular place and contemporary map sheet still need individual checking.

## Separate external identity evidence from its access route

Prefer mapping agencies, library catalogues or sourced gazetteers, recording title, edition, complete URL and access date. A found page title is not an inspected internal map; track catalogue metadata and image review separately. A current map can suggest candidates without replacing a historical map. Label a second-hand account as such rather than original evidence. When access is unavailable, retain a next step instead of supplying coordinates from memory. Book Isle notes connect evidence; they are not described as an automatic online geographical fact-checker.

## Conclude with identity and uncertainty

Write supported feature type, original name, period and positional relationships first, then unresolved naming, edition or extent issues separately. Plain provisional wording with passage or figure anchors is enough; new fields are unnecessary. Date a later correction instead of silently replacing a mistaken match as if it had always been right. Keep chapter-specific occurrences of the same name anchored separately rather than automatically inheriting the first chapter’s identification. Recheck identity in each new context.

## Retell the passage rather than only finding a point

Return to the bookmark and explain feature type, why this candidate was chosen and which cue remains insufficient, then compare the legend. “The names match” alone is an incomplete chain. Choose the next consequential name instead of assigning modern coordinates to every occurrence. Verify older names, period and figure references after important note exports, retaining map files separately from reading data. Success means an identity that explains the passage, not a superficially precise list mixing periods and extents. The reading task determines how deeply to check.

## Related tutorials and sources

[Map figure anchors](<https://allluckly.cn/en/guides/nasbook-figure-number-notes/>), [Names in context](<https://allluckly.cn/en/guides/nasbook-cross-chapter-glossary/>).

Map references: [USGS: Map Scales](<https://www.usgs.gov/publications/map-scales>) and [USGS on map and GPS elevation differences](<https://www.usgs.gov/faqs/why-dont-elevations-your-maps-agree-those-provided-my-gps-system-which-are-correct>). This is manual identity checking; invented names are not evidence about real places.

Checked on November 4, 2026 against the [official Book Isle listing](<https://apps.apple.com/cn/app/id6766198898>) and [Apple’s version lookup](<https://itunes.apple.com/lookup?id=6766198898&country=cn>): version 1.1.3, requiring iOS / iPadOS 15.6 or later. This manual checking workflow uses local reading, search, bookmarks and notes. Readers verify calculations, place identities and dates against original sources; no automatic interpretation is promised. Readers supply files and check installed controls. No step-by-step physical-device testing is claimed.

