See what changed.
Know where to inspect first.
Omniterra Pulse turns current InSAR ground-motion and SAR surface-disturbance signals into a ranked site review for infrastructure teams. Start with one site, see where movement or fresh change is concentrated, and decide what deserves field review before the next inspection cycle.
History for baseline review, with optional commercial SAR sources when the site needs more.
Combined AOI coverage across the current benchmark sites used to validate first-site delivery.
Dense AOIs can approach twice-weekly radar coverage. The standard 12-month baseline uses 24 selected acquisitions.
Median delivered motion coverage per pilot site on exported vertical-motion rasters.
Median benchmark quality score across the current exported ground-motion run set.
Median persistent-scatterer density per square kilometer across the current benchmark run set.
01 / InSAR Ground Motion
See where movement is persistent enough to escalate.
Airports
Use InSAR ground motion monitoring around runway edges, aprons, shoulders, and drainage packages where reclaimed ground or heavy pavement loads make settlement credible.
Ports and reclaimed terminals
Track quay backlands, terminal yards, waterfront embankments, and reclaimed pads for settlement patterns that episodic walkdowns can miss.
Refineries and industrial pads
Separate persistent tank-pad, berm, and industrial-edge movement from recent surface works when reliability teams need evidence of long-running ground behavior.
City subsidence districts
Extend InSAR screening across streets, utilities, and public-works districts where levelling, GNSS, or civil reports suggest subsidence but coverage is uneven.
Levees, dams, and landfills
Add repeatable SAR satellite review for crest settlement, embankment movement, slope behavior, and stability signals across monitored water-control and waste assets.
Pipelines and corridor infrastructure
Focus on buffered segments, slope-prone crossings, and settlement-sensitive approaches where the question is which corridor unit is persistently moving.
Airport runway motion in one review panel.
A monthly InSAR baseline starts with the full airport motion field, then narrows the review to named runway assets for inspection planning.
SFO / Runway 10L-28R
runway
These examples reflect publicly documented site conditions. Omniterra Pulse outputs shown here are sample product views from satellite-derived monitoring and are provided for information only.
Kansai / Runway 06L-24R
runway
These examples reflect publicly documented site conditions. Omniterra Pulse outputs shown here are sample product views from satellite-derived monitoring and are provided for information only.
Tanjung Priok / New Priok Kalibaru
reclaimed terminal
These examples reflect publicly documented site conditions. Omniterra Pulse outputs shown here are sample product views from satellite-derived monitoring and are provided for information only.
Tanjung Emas / Container Wharf
container wharf
These examples reflect publicly documented site conditions. Omniterra Pulse outputs shown here are sample product views from satellite-derived monitoring and are provided for information only.
Copler Mine / Heap Leach Pad
heap leach pad zone
These examples reflect publicly documented site conditions. Omniterra Pulse outputs shown here are sample product views from satellite-derived monitoring and are provided for information only.
02 / Surface Disturbance
Find the parts of the site that changed first.
Transport hubs and reclaimed waterfronts
Screen apron, yard, berth-backland, shoreline, embankment, drainage, and flood-cleanup change across airports, ports, reclaimed terminals, and other waterfront infrastructure where teams need to know which zones to inspect first.
Industrial pads and active buildout
Track pad clearing, trenching, grading, stockpiles, utility work, access-road cuts, and expansion boundaries across refineries, industrial sites, freight terminals, and active buildout programs.
Corridors and crossings
Rank excavation approaches, disturbed crossings, access-road cuts, slope scars, and right-of-way activity across pipelines and other corridor infrastructure so field review starts in the right segments.
03 / Environmental Context
Add vegetation and air layers when the site needs the full picture.
Vegetation context around campuses, corridors, and site edges.
Add vegetation, moisture, and land-cover context when teams need a broader read on site surroundings, landscaped campuses, utility corridors, or district-scale ground conditions.
NDVI layer
Vegetation index
Air context around airports, industrial sites, and city districts.
Add NO2 and related atmospheric layers when surrounding exposure, traffic, or industrial activity matters to the site review and helps teams read the wider operating picture.
NO2 layer
Air quality
A fuller site picture when one layer is not enough.
Use these layers beside disturbance and ground motion when the job is to understand a whole site, campus, or district with more environmental context around the core signal.
NDVI layer
Vegetation index
04 / Features & FAQ
Features
Use SAR satellite monitoring to see where earthworks, trenching, shoreline change, flood cleanup, or other fresh disturbance is concentrated.
Screen for settlement, subsidence, and embankment movement where persistent ground behavior matters.
Give site and engineering teams one clear place to start, with confidence notes and supporting fields that help separate a strong lead from something that needs a closer read.
Tie the signal back to aprons, berths, pads, embankments, corridors, or other reviewed geometry when it exists.
Ship files, layers, and delivery formats that drop into GIS, engineering maps, dashboards, and existing review workflows, with review packet, export, or API delivery depending on how the team already works.
Move from one first study into monthly or event-driven monitoring when the signal earns it.
FAQ
Should we start with one site or a software evaluation?
Start with one site when the job is a fast review decision, not a long platform evaluation or portfolio rollout. Omniterra Pulse works best when the first step stays scoped and operational.
Why not just work from raw feeds or manual triage?
Raw change feeds, InSAR layers, and manual GIS review can show activity, but they often stop short of the next action. Omniterra Pulse turns that signal into hotspot maps, asset-linked outputs, and a clearer review path.
Can this start as one review and expand into monitoring?
Yes. Omniterra Pulse is designed to roll forward cleanly. If the first site proves useful, it can expand into recurring monitoring or a second-site rollout without changing the workflow.
What do we get in the first project?
The first scope stays tight: one named site, one hotspot map, ranked review output when reviewed geometry exists, a short interpretation memo, and one review call. Dashboard access can be added when it helps the review workflow.
What should we send, and do we need reviewed geometry?
Send one named site, asset area, or AOI and the decision you need to support. If reviewed geometry exists, include it. If not, Omniterra Pulse can still start from a clear site boundary or AOI and deliver a useful first hotspot map.
How fast is the first packet?
A scoped first review is typically delivered in two to three weeks. A recurring monitoring start is broader and usually runs six to ten weeks, depending on site scope and data readiness.
Start with one site.
Request a pilot.
Begin with a scoped paid pilot or a recurring monitoring start.
Send one site or area of interest and the decision you need to support. We will reply with fit, timing, and a pilot scope for surface disturbance screening, InSAR ground motion review, or both.