Platform

Four tools, one model.

Hachure is a set of tools around a single versioned terrain model. Each tool reads the same ground, so nothing is rebuilt between the field and the report.

Atlas / Sample massif / Slope

Atlas / Slope

Sample data

Layers

Contours, 20 m

Slope classes

Drainage lines

Survey points

Traverse A

Revision r. 41

Engraved mountain massif sketch with contour lines

Slope classes

Flat

0 to 5°

18%

Gentle

5 to 12°

24%

Moderate

12 to 20°

21%

Steep

20 to 30°

17%

Very steep

30 to 40°

11%

Extreme

40 to 55°

Cliff

over 55°

Profile A to A′

Illustration with sample values. Not survey data.

01 Terrain model

Atlas

The model itself. Elevation grids, surfaces and survey points live in one versioned store. Every change creates a revision with a note on who changed what, and why.

Versioned surfaces and point sets

Error bounds stored with every reading

Compare any two revisions side by side

02 Terrain analysis

Slope

Reads the model and returns slope, aspect, curvature and drainage as classes. The rule behind each class is written next to it, so a reviewer can disagree with the rule, not only with the result.

Seven slope bands with written rules

Drainage and catchment tracing

Change maps between revisions

03 Field capture

Traverse

The notebook that goes out with the crew. Lines, points and photographs are recorded offline, tied to the same control points as the model, and synced when the truck is back in range.

Works without signal

Control points shared with Atlas

Photographs pinned to the ground position

04 Compliance

Ledger

Turns the model into documents. Each report names the revision it describes, lists its limits, and can be reproduced later from the same inputs.

Report templates for permitting offices

Revision named on every page

Reproducible from stored inputs

Method

Slow on purpose.

Four steps, in this order, every time.

I

Survey

We start at the ground, with control points whose position is known better than anything built on them. Lines, points and sensor series are logged with their error bounds, not rounded for tidiness.

II

Model

Surfaces are built from the survey and stamped with a revision. Nothing is edited in place. A correction is a new revision, and the old one stays readable.

III

Verify

A second reader checks the classes against the ground, on foot where the stakes are high. Disagreements are written down and resolved before a report is issued.

IV

Report

Findings are written together with their limits, in the format the receiving office already uses. A report that hides its uncertainty is a worse report.

Compliance

Five questions every report answers.

Which revision does this report describe?

Where do the control points come from, and how good are they?

Which slope rule was applied, and who approved it?

What was checked on foot, and what only on the model?

What does this report not show?

Documentation

Docs, in four topics.

Written for the person who inherits the model.

Getting a model in

Accepted inputs, coordinate systems and how control points are matched.

Reading the classes

The seven slope bands, their rules and the cases where we refuse to classify.

Field capture

Setting up a crew, working offline and syncing back into the model.

Reports and revisions

Templates, reproducing an old report and exporting for an audit.

Inputs

GeoTIFF, LAS and LAZ point clouds, GeoJSON, GPX tracks, CSV control points

Outputs

GeoTIFF, GeoJSON, contour lines as vector, PDF reports, CSV tables

Revisions

Every output carries its model revision and input checksums

See it on a real site.

Request a briefing