Identify the source record.
Keep a stable way to connect a map feature to its asset, site or business record. Name the owner of corrections and note when the information was updated.
Resources / Location data
What does this point or boundary represent?
Review a safe representative sample before importing the full dataset.
Explain the location.
Record the coordinate system or source format, known precision and meaning of the location. A map point may represent an entrance, an estimated address position or a larger site.
Test the intended interpretation.
In a fictional service-area tool, a physical office marker does not describe every location the team serves. Define the coverage rule separately and check representative boundary cases.
Review missing and ambiguous records.
Decide how the application reports incomplete locations or uncertain matches. Avoid silently placing them on a map as though the result had been confirmed.
Keep updates connected.
Test a correction from the source through to the displayed feature. Retain the original relationship so later imports do not create unrelated duplicates.
Prepare the application checklist or discuss the data review.