Real-work map · 11

Mapping and change detection

Control pose, coverage, sensor settings, registration and review before interpreting differences between visits.

Evidence statusField mission framework · task, terrain and site validation requiredLast reviewed: 15 August 2026
11

FUURAA thesis

Repeated scanning detects change only when acquisition and registration uncertainty remain below the decision threshold.

Engineering map

Turn the title into engineering objects that can be observed, measured and reviewed.

Each layer states the boundary to establish and the evidence needed for the next decision.

01

Acquire

Version route, viewpoint, speed, lighting, sensor and occlusion conditions.

02

Register

Preserve coordinate frames, anchors, loop closures and rejected regions.

03

Interpret

Separate physical change from pose, calibration, weather and processing drift.

Verification questions

Write the questions first, then decide whether a demo, test, pilot or operating record can answer them.

Each question needs an object, conditions, denominator, threshold and accountable decision owner.

  1. 01

    What minimum change matters?

  2. 02

    How complete is repeat coverage?

  3. 03

    Which algorithm version produced the difference?

  4. 04

    Who confirms a physical change?

Evidence to preserve

Enable the next reader to reconstruct conditions, results, failures and the decision.

A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.

  1. 01

    Evidence package 1

    Survey design and reference frame

  2. 02

    Evidence package 2

    Coverage and registration uncertainty

  3. 03

    Evidence package 3

    Reviewed change record

Scope boundary

State what this evidence still cannot be generalised to.

Sources and evidence status

Read standards scope, measurement evidence and application conclusions separately.

Source dates and review status remain visible; external sources open in a new tab.