Historic AtlasTHE RECORD ROOM / DATA NOTES
A FIELD GUIDE TO LOCATION RECORDS

A place is more
than a pin.

Identity, language, evidence and uncertainty. Explore the pieces that make a historical location useful—and keep them distinct.

WGS 84 / 48.208, 16.373

The riverside watch.

FICTIONAL SPECIMEN

A deliberately invented river crossing used to demonstrate the record model. Its medieval period label is interpretive, not an exact date.

ID / 550e8400-e29b-41d4-a716-446655440000
KIND / point · stable across import and export
AUDIT / sample-only · not a real contributor

References keep their order and may carry an HTTP(S) URL plus citations by language. No historical claim is made by this specimen.

TWO SCALES, TWO QUESTIONS

Confidence isn't one number.

3 / 5

Identification and position as judged by contributors.

3 / 5

Confidence in this wording, independent of the location.

The right language, or an honest fallback.

The sample has en and de keys; its example content is rendered in English here. Fallback: requested → English → lowest available language code. Citations follow the same rule; tag keys are the final tag-label fallback.

THE CONTRACT

Built to preserve
what we know.

Local demonstrations above; the system described below is the intended backend contract, not a running API.

Identity that travels.

A system-assigned UUID is immutable and never reused. Internal numeric keys stay internal. Created/updated subjects and UTC timestamps belong to the system, not user-supplied payloads.

Bounds, not certainty.

Optional period bounds are UTC timestamps and can precede the common era. Start must not exceed end. A free-text period label expresses imprecision. Confidence is not a radius.

Extension without ambiguity.

Initial position kind is point: latitude −90…90, longitude −180…180. New kinds add their own fields. Consumers explicitly reject or ignore unknown kinds, rather than misreading them.

Roles at the API.

Viewer reads locations/tags. Editor creates, replaces or deletes locations. Admin replaces tag labels. No session gives 401, missing role 403. Validation problems give 400 with a description.

Read the API and legacy-import notes

GET /api/locations is zero-based, newest first, default size 20, maximum 100. POST returns 201 and a Location header; PUT replaces content and returns 200; DELETE returns 204. Missing records return 404. Content needs at least one translation, nonempty name/description, valid independent confidence levels and a supported point. References require citations and, if supplied, absolute HTTP(S) URLs.

Legacy DE maps to de and GB to en. German fallback uses the old place name/description; an empty legacy description is retained, unlike normal API input. Missing all names is reported. Legacy confidence is 3, periods stay empty, and source references are ordered by legacy ID. Import uses the fixed legacy-import subject, never contributor personal data. Unchanged rows preserve audit timestamps; invalid coordinates and skipped places are reported. This page does not run that SQL importer.

Original offline illustration and fictional records. No authentication, persistence, real translations or geographic service is connected. Controls reset on refresh.