CoastLensDocs

CoastLens / Documentation

How it works

How CoastLens turns two survey epochs into a reviewed, signed and independently verifiable volume figure.

Overview

CoastLens runs five steps in order. Each one writes a record, so a signed report can always show its inputs, its arithmetic and the people who approved it.

StepWhat happensWhat is recorded
1. InputSurfaces are uploaded with a declared vertical datumFile SHA-256, datum, stated uncertainty
2. Quality gatesDatum, grid, coverage and no-data are checkedOne result per check; refusals with a reason code
3. ComputationΔV is computed between two epochsRaw and corrected volume, bias, area, cells, tolerance
4. ReviewFindings are accepted or dismissed by a named reviewerReviewer, decision, reason code, time
5. SealThe report is signed and sealedContent hash, version, signer

1. Input

Each survey epoch belongs to a site and declares its vertical datum and its stated vertical uncertainty. Supported datums are TAW, NAP, LAT, MSL, ODN, chart datum, or a named local project datum.

Supported files

FormatUsed for
ESRI ASCII grid (.asc)Volume and transect computation
GeoTIFF / COGStored and fingerprinted as evidence (not yet read by the volume computation)
LAS / LAZ point cloudsStored and fingerprinted as evidence
JPEG / PNG imagery, CSV, PDFStored and fingerprinted as supporting evidence

Refused uploads

CoastLens does not run photogrammetry. Bring a processed surface, not raw photographs.

Epoch detail: the datum, the stated vertical uncertainty, the stored file with its SHA-256 and the quality checks.
Epoch detail: datum, stated uncertainty, the stored file with its SHA-256, and one row per check.

2. Quality gates

Before any arithmetic runs, both epochs are checked. If a check fails, no volume is produced and the response names the rule that failed.

CheckFails when
DatumThe two epochs declare different datums, or one declares none
GridGrid shape or cell size differ between epochs
CoverageThe epochs do not overlap the area of interest
Control zoneThe control zone contains no usable cells
Note. Cells with no data are excluded from both the sum and the area. A gap is reported as a gap, never as zero change.

3. Computation

Volume change is the summed vertical difference over the area of interest, multiplied by the cell area. A control zone of stable ground is used to estimate the systematic vertical offset (bias) between the two surveys, which is then removed:

ΔV = Σ ( z_after − z_before − bias ) × cellArea

The computation is deterministic and runs in code. Every result records:

Cross-shore transects can be added to show profiles and foreshore slope along fixed lines.

A completed analysis showing corrected and uncorrected volume, the bias removed, excluded cells and the tolerance band.
A completed analysis.

4. Review

Structural observations, such as a displaced armour unit or spalled concrete, are recorded as findings with the status proposed. A reviewer then accepts or dismisses each finding.

5. Seal and verification

Signing a report writes its content hash, method version, input file hashes, reviewer and signer to an append-only, hash-chained ledger. Each ledger entry commits to the one before it, so editing an earlier entry breaks every later hash.

A report after signing: seal intact, version 1, immutable.
A signed report, version 1.

How AI is used

A language model may draft the method statement of a report from a structured set of facts taken from the analysis. Before the draft is stored:

  1. every figure in the text is checked against the analysis;
  2. a figure that is not in the analysis, or certification or guarantee language, rejects the whole draft;
  3. a rejected draft is replaced by a fixed template.

No model computes, adjusts or certifies a volume. The report states whether its method statement was written by the model or by the template, and the report never depends on the model being available.

Limits

Data and billing