AVARC / MIGRATION FIELDNOTESLEGACY SCHEMA · SOURCE REFERENCE
ACCESS EXPORT → HISTORICAL DIRECTORY

Know the past.
Import with care.

A practical fieldbook for the legacy data model. Distinguish documented evidence from inferred links before moving a single record.
All findings below come from the supplied stage snapshot notes. No live scan has run.

3,516Places with one coordinate row
8Non-plain-decimal coordinate rows
57Empty place descriptions
0Declared foreign keys in export
REQUIRED FOR IMPORT

How to read these relationships

The export declares primary keys only. Every relationship displayed is inferred, even where an export diagram labels a column “FK”. Selected core links were checked against the documented stage data, not by this page.

Critical mapping: poh.pohType_ID → pohtype.identifier
The target is identifier, not pohtype.ID. Every place has one georeference row; 3,516 of 3,518 coordinate rows are used. All documented SRIDs are 4326.
LOCAL SYNTAX EXERCISE

Inspect a coordinate pair

Legacy latitude and longitude are text. This tool validates decimal syntax and geographic ranges, without converting ambiguous values.

No import is performed.

LOCAL MAPPING EXERCISE

Translate the language code

Payload coverage
DE appears for every place; GB appears for two. English is encoded as GB, not EN.
Category caution
3,511 maincategory values are empty. Remaining values include URLs and ToDo; pohcategory only holds ToDo.
Contributor boundary
Two contributor IDs occur in places; contributor has five rows. Import reads the link only, not personal content.