Omniterra Atlas · Application 06

Version every cell and cap state across the closure programme.

Track cell geometry, cover, drainage, cap progress, stockpiles, and closure change as versioned site states.

Starts with
Photos, video, drone capture, plans, control, and prior site states.
You receive
A repeatable Atlas workflow around each cell, cap, or closure milestone and review date.
Product output / application view
Atlas versioned site record for landfill cap and closure review.
Inspect metric, visual, semantic, and temporal layers together, with direct links back to the capture and prior site states.
01 / Operational outcome
What improves

Keep every cell and cap state comparable through construction and aftercare.

The workflow is organized around one operating question: What was built or changed, how does it compare with design, and where is capture or field confirmation still insufficient?
Benefit 01

Creates a durable record across construction and aftercare

Output used

Georeferenced orthophoto, surface, and 3D site state

Benefit 02

Makes plan-vs-actual exceptions easier to review

Output used

Cell, cap, drainage, stockpile, and design comparison

Benefit 03

Keeps field, survey, and environmental evidence connected

Output used

Closure evidence pack and open-format archive

02 / Operational context
Who uses it and when

Start with the operating team, trigger, and decision.

The technical scope starts from the operating moment, available observations, site geometry, time window, and the result the team needs to use.
Teams
Waste operators, landfill managers, environmental consultancies, closure contractors, and regulators’ technical teams.
Primary users
Landfill manager, closure director, environmental lead, survey manager, or consulting partner.
When it applies
Cell progression, interim or final cover, cap construction, closure certification, drainage review, or aftercare.
Decision to support
What was built or changed, how does it compare with design, and where is capture or field confirmation still insufficient?
03 / Evidence and deliverables
Configured workflow

A repeatable Atlas workflow around each cell, cap, or closure milestone and review date.

The workflow connects named inputs, spatial processing, technical review, and reusable outputs for a defined site state or review period.
Atlas stores the capture, spatial products, findings, and comparison state as one versioned site record.
Output set

What the team receives to support the decision.

01

Georeferenced orthophoto, surface, and 3D site state

Generated from the registered capture and stored in the current Atlas site version.

02

Cell, cap, drainage, stockpile, and design comparison

Linked to source imagery, geometry, control, and review state.

03

Change record with observed/inferred/planned classes

Structured for browser inspection, comparison, and repeat processing.

04

Closure evidence pack and open-format archive

Exported in open spatial formats for GIS, engineering, and operations systems.

04 / Related use cases

Bring the decision and the site evidence.
Define the record that can support it.

A repeatable Atlas workflow around each cell, cap, or closure milestone and review date.

Send the decision date, site or capture, review period, and the assets or work package under review. We will reply with the required inputs, processing scope, output formats, and next step.

Email Us

Performance cookies.