Validate & Report
Assembly
Merge geospatial terrain with static and dynamic assets.
Verification
Project evidence onto geometry and validate dimensions.
Confidence
Visualize uncertainty with a clear color-coding system.
Report
Communicate the reconstruction with honest limitations and boundary awareness.
Synthesis is where all data streams merge. Validation is the feedback loop that ensures accuracy. This phase is about assembling the scene, verifying alignment, and quantifying confidence in the reconstruction.
This is Stage 5 of the Research Gate: two halves — validate the assembled scene (below), then report it defensibly (Part B).
Scene Assembly​
- Base Layer: Import Geospatial Terrain (Phase 4) as the foundation.
- Population: Instance Static Assets and Dynamic Agents (Phase 2) into the environment.
The reconstruction-specific assembly methods live in the Geometric Reconstruction playbook (scene decomposition and environmental ground truth), with object-level scale on the Scale Estimation page. This page covers the general validation and reporting that applies to any reconstruction.
Spatial Verification​
Projection mapping: Project original 2D "Evidence" onto the 3D geometry to verify alignment ("Place 2D image over 3D object").
Refinement: Adjust camera tracks or object positions until the 2D/3D overlay is perfect.
Temporal alignment placement: Ensure that the movement of objects in 3D space matches the timing of the video evidence.
Geometric Validation​
- Scale verification: Measure known objects (door heights, road widths) in your 3D scene vs. real-world specs.
- Angular verification: Check that angles between perpendicular walls = 90°.
- Distance verification: Measure object-to-object distances against ground truth.
Feedback Loop Process​
- Failure Analysis: When validation fails, determine which phase requires revision (e.g., "Camera solve is drifting" -> Return to Phase I).
- Revision Log: Create a template to track iterations and changes made during the validation process.
Confidence Visualization System​
Communicate the certainty of your reconstruction visually.
Example color coding:
- Green: High confidence (measured, multiple sources confirm).
- Yellow: Medium confidence (single source or estimated).
- Red: Low confidence (interpolated, occluded, or speculative).
- Wireframe: Uncertain geometry.
- Dashed lines: Inferred trajectories.
Summary​
The final phase is about rigor. By systematically validating every element of the scene against the original evidence and ground truth data, you transform a 3D model into a forensic tool. The confidence visualization ensures that the limits of the reconstruction are clearly communicated.
Key Takeaways:
- Overlay: Always project source footage onto your model to check alignment.
- Measure: Verify scale and distance against known real-world values.
- Communicate: Use visual cues (color coding) to show what is fact and what is inference.
Part B: Reporting the Reconstruction​
Once validated, the reconstruction must be communicated as analysis, not just visuals. This aligns methodology with international standards (the Berkeley Protocol) and professional practice (reporting conventions used in legal and analytical work).
Analytical Report​
Write a structured report that includes:
- Research question and approach (from define).
- Methodology: what you did, why, what alternatives you considered.
- Sources and chain of custody: registry summary and hash log references (from collect / preserve-store).
- Findings: what the reconstruction demonstrates or answers.
- Conclusions: what can be claimed from the analysis.
Exhibits and Comparison Charts​
Where relevant, produce:
- Comparison images: source photo alongside rendered view, model overlay on footage.
- Annotated diagrams: measurement points, sight lines, confidence zones.
- Confidence map: the color-coded output from above.
Exhibits make the analysis legible to others and demonstrate that conclusions rest on verified geometry, not aesthetics.
Honest Limitations​
State explicitly:
- The margin of error (from uncertainty quantification in analyze) — e.g., "±15cm at relevant distances."
- What remains uncertain or speculative, and why.
- What the analysis cannot determine (e.g., "This reconstruction establishes physical possibility of sight line, not proof of actual observation").
Transparent acknowledgment of limitations strengthens credibility — it signals that the analysis was rigorous enough to know its own boundaries.
Boundary Awareness​
The report must be clear about what does and does not follow from the analysis:
- What the reconstruction proves vs. what it merely illustrates.
- Where inference starts and evidence ends.
- That jurisdiction-specific admissibility is not assumed — the report provides a sound method; whether it meets a particular court's admissibility rules is a separate question.
This is the difference between a defensible reconstruction and a persuasive graphic: defensible work acknowledges its boundaries.
Documentation for Methodology​
What to document during Validation & Reporting
In Your Method Section​
"The final scene was assembled by integrating the geospatial terrain with the modeled assets. Spatial alignment was verified by projecting the source video [Video ID] onto the 3D geometry. Geometric accuracy was validated by measuring [Known Object] within the scene."
In Your Decision Log​
Record the following:
- Any adjustments made to object positions to achieve alignment.
- The margin of error observed during geometric validation (e.g., "Model aligns within 5cm of ground truth measurements").
- The rationale for assigning specific confidence levels to different parts of the scene.
Verification​
"A confidence map was generated to visually distinguish between verified geometry (Green) and inferred elements (Red)."
Further Resources: