SEE MOTION. VERIFY CONTEXT. DECIDE BETTER.
InSAR Intelligence for Ground Motion Analysis
RAUZ turns satellite ground-motion data into engineering intelligence through QA/QC, spatial and time-series analysis, ground-data comparison and engineer-reviewed interpretation for infrastructure and natural systems.
InSAR Intelligence
Satellite ground-motion data is the evidence layer. Interpretation is the intelligence layer.
RAUZ InSAR Intelligence is a platform capability for turning satellite-derived deformation products into a structured engineering and environmental review. It connects ground-motion patterns with data quality, asset location, project events, geology, groundwater, weather and conventional monitoring where those datasets are available.
InSAR Intelligence is the controlled use of satellite-derived ground-motion measurements together with QA/QC, spatial and time-series analysis, physical context and independent ground evidence to decide what the observed movement can reasonably support.
See beyond the instrument line.
InSAR can reveal distributed surface-motion patterns over areas that would be difficult to cover with dense conventional instrumentation alone.
Review movement through time.
Where suitable archives exist, historical and ongoing observations can help distinguish pre-existing movement from a trend that develops during construction or operation.
Compare space-based and ground evidence.
RAUZ uses InSAR as one evidence source alongside survey, GNSS, settlement, inclinometer, groundwater, weather and project records when the comparison is technically meaningful.
Platform boundary: this page explains the RAUZ InSAR Intelligence capability. The separate InSAR Ground Motion solution page explains how a client can scope an InSAR review or monitoring engagement.
How It Works
From radar observations to a reviewable ground-motion interpretation.
InSAR uses repeat SAR acquisitions to estimate changes in distance between the radar sensor and coherent points on the ground or on built assets. The RAUZ platform starts from the delivered InSAR product, preserves its metadata and quality information, and then adds the engineering interpretation layer.
Set the asset, area of interest, engineering question, period and expected movement mechanism.
Receive an agreed public or commercial InSAR product with the metadata needed for interpretation.
Review coverage, measurement-point quality, viewing geometry, time span, reference and uncertainty indicators.
Examine displacement, mean velocity, time series, spatial clusters, acceleration and changes in pattern.
Compare ground monitoring, survey, groundwater, weather, geology and project events where relevant.
State what the evidence supports, what remains uncertain and what follow-up should be discussed.
RAUZ interpretation layer
The platform does not treat a coloured displacement map as a conclusion. The useful output comes from connecting the satellite product to the physical and project context.
- Satellite-derived motion
- Quality and reference checks
- Spatial and temporal pattern review
- Ground-data comparison
- Engineer-reviewed interpretation
Data Inputs
The source product determines what can be interpreted.
RAUZ can work with agreed public or commercial ground-motion products, subject to their coverage, quality, licensing and suitability for the project question. InSAR products are not interchangeable: orbit geometry, radar wavelength, processing method, reference frame, acquisition history and measurement-point quality all matter.
| Input | What it contributes | What RAUZ checks |
|---|---|---|
| Line-of-sight displacement | Change measured along the satellite viewing direction. | Orbit geometry, sign convention, reference, time period and whether the expected movement direction can be observed. |
| Mean velocity | A compact view of longer-term motion rate over a defined period. | Whether a mean rate hides changes, reversals, acceleration or seasonal behaviour in the underlying time series. |
| Displacement time series | How individual measurement points or areas change through time. | Gaps, steps, trend consistency, acquisition dates, uncertainty indicators and relationships with project events. |
| Ascending / descending geometry | Different satellite viewing directions that may help constrain movement components. | Whether both geometries are available and whether decomposition is technically justified for the selected product. |
| Quality metadata | Indicators such as temporal coherence, standard deviations, RMSE or other provider-specific quality fields. | Whether the measurement points used for interpretation meet the quality requirements of the intended review. |
| Ground & project data | Survey, GNSS, settlement, inclinometer, groundwater, weather, geology, construction and asset information. | Coordinate/reference compatibility, timing, physical relationship and whether the comparison actually tests the same mechanism. |
Official European example: the Copernicus European Ground Motion Service provides Basic, Calibrated and Ortho products derived from Sentinel-1. Its documentation includes displacement, velocity and quality fields intended to support informed use of the data.
InSAR QA/QC
Before asking what moved, ask whether the satellite product can see the movement reliably.
The usefulness of InSAR varies by site, surface, satellite geometry, acquisition history and processing product. RAUZ keeps those limitations visible instead of treating every measurement point as equally reliable.
Measurement-point availability
Buildings, bare ground and other coherent surfaces may provide useful radar targets, while vegetation, snow, rapid surface change or other conditions can reduce usable phase information.
Line of sight is not full 3D motion.
A satellite measures displacement along its viewing direction. Movement that is poorly aligned with that direction can be underestimated or difficult to interpret without complementary geometry or ground data.
Relative motion needs a stable frame.
The selected reference and calibration approach influence how movement is reported. RAUZ keeps the reference system explicit when results are compared with survey or GNSS.
Acquisition frequency sets the observation window.
Satellite revisit and provider processing cadence must be compared with the speed of the expected process. Fast or sudden events may require other monitoring methods.
Use the provider’s quality indicators.
Coherence, standard deviation, RMSE, point history and other product-specific indicators should be screened before a point is used in a technical conclusion.
Pattern does not prove mechanism.
A spatial cluster or acceleration can identify an area that deserves review, but geology, groundwater, loading, construction and ground evidence are needed before assigning cause.
Why this matters: USGS work on the densely vegetated island of Pohnpei reported low coherence across much of the interior, preventing use of phase-change products there. It is a practical reminder that InSAR suitability must be checked for the actual site rather than assumed.
InSAR + Ground Monitoring
Use satellite and field measurements to challenge each other, not to duplicate each other.
Conventional instruments and InSAR observe different parts of the problem. Their value increases when each dataset is used for the question it is best suited to answer.
Spatial context and historical pattern
InSAR can extend the field of view around an asset, show distributed surface movement and, where suitable archive data exist, provide evidence from before a local instrument network was installed.
Local mechanism and direct project control
Inclinometers, piezometers, survey, GNSS and other field systems can target known structures, depths, groundwater zones or construction interfaces and can be designed around project trigger requirements.
| Engineering question | InSAR contribution | Ground evidence | RAUZ interpretation |
|---|---|---|---|
| Is settlement local or wider? | Spatial surface-motion pattern outside the instrument footprint. | Levelling, settlement points, GNSS. | Compare extent, rate and timing rather than forcing exact point-for-point agreement. |
| Is a slope changing? | Surface displacement pattern where coherence and geometry are suitable. | Inclinometer, GNSS, survey, groundwater, rainfall. | Check whether spatial motion, depth behaviour and hydrological changes support the same mechanism. |
| Did movement exist before construction? | Historical archive where available. | Baseline survey, GI, asset records. | Separate pre-existing trend from a change that develops during the works. |
| Where should field instruments be concentrated? | Wide-area screening for persistent or anomalous zones. | Site inspection and targeted monitoring. | Use remote sensing to support, not replace, risk-based field design. |
Applications
InSAR is most useful when the project question has a spatial or historical dimension.
RAUZ uses the same intelligence framework across infrastructure, ground and natural systems, while the physical mechanism and supporting evidence change by application.
Excavation, tunnelling & urban works
Review whether deformation remains concentrated around the expected zone of influence or extends into a wider area.
Rail, roads & linear corridors
Screen long routes for spatially distributed settlement, embankment behaviour or recurring motion that may not be covered by dense point monitoring.
Landslides & slope instability
Use surface-motion patterns together with groundwater, rainfall, geology and ground instruments where the radar geometry and surface conditions are suitable.
Groundwater, mining & extraction effects
Map distributed vertical or line-of-sight motion and compare the spatial pattern with known abstraction, mining, loading or geological conditions.
Dams, bridges, buildings & facilities
Use satellite-derived deformation as an additional evidence layer for long-term asset behaviour, foundations, approaches and surrounding ground.
Environmental & land monitoring
Where surface motion is relevant, connect remote-sensing evidence with hydrology, terrain, land use and other environmental observations.
Regional Delivery
One analytical method, different data environments across RAUZ markets.
RAUZ currently works in English and is structured for remote-first delivery across the South Caucasus, European Union, United Kingdom, Middle East and Africa. InSAR availability and the right processing source should be checked for the actual location rather than assumed from a generic global claim.
Mountain terrain, corridors and urban assets
Potential use cases include slope movement, transport corridors, hydropower-related ground behaviour and urban construction. Site-specific suitability depends on geometry, land cover, archive availability and the engineering question.
Public ground-motion baseline through EGMS
Copernicus EGMS provides Sentinel-1-derived ground-motion products across EU27, Iceland, Norway and the United Kingdom, creating an official public dataset that can support initial screening and contextual review.
Project-specific source selection
Large infrastructure, mining, urban development, subsidence and remote assets can be relevant applications, but satellite mission, archive depth, resolution and update frequency should be selected for each project rather than copied from European assumptions.
Regional SEO boundary: RAUZ does not create country-specific technical claims unless there is verified local evidence, a real project need, public official data or an established delivery relationship for that market.
Platform Outputs
Move from coloured points to a technical record someone else can review.
The RAUZ output should preserve the evidence chain: source product, quality flags, selected area, observed pattern, cross-checks, interpretation, uncertainty and recommended follow-up.
Ground-motion view
Spatial distribution of selected measurement points, velocity or displacement with asset and area-of-interest context.
Movement through time
Selected point, cluster or zone histories with acquisition dates, trend, project events and quality information kept visible.
Ground + satellite evidence
Comparison with survey, GNSS, settlement, groundwater or other monitoring where the reference and physical relationship are suitable.
Suitability and confidence notes
Coverage, geometry, quality indicators, reference assumptions, gaps and known limitations that affect interpretation.
Engineer-reviewed interpretation
Separate observation from possible mechanism and state what is supported, what remains uncertain and what should be checked next.
Recurring or focused output
One-off diagnostic note, periodic review, portfolio screening summary or automated reporting workflow depending on the agreed scope.
Publishing requirement: add a real RAUZ platform screenshot or an anonymised/demonstration output before using this page as final product evidence. A real interface image is intentionally not fabricated in this HTML.
Official International Evidence
Public agencies and specialist providers show where InSAR adds value—and where interpretation still matters.
The examples below are based on official source material. They are not RAUZ projects and do not imply a partnership, endorsement or commercial relationship.
Copernicus European Ground Motion Service
EGMS uses Sentinel-1 InSAR to provide systematic ground-motion products across Europe. The official product documentation distinguishes Basic, Calibrated and Ortho products and publishes quality fields and product specifications for informed use.
Official Copernicus source ↗USGS — Barry Arm Fjord
USGS used repeat satellite SAR observations to monitor movement of a remote landslide where field monitoring is difficult, demonstrating the value of remote deformation measurements for large or hard-to-access terrain.
Official USGS source ↗Sixense — satellite + ground monitoring
Sixense’s official satellite-monitoring material describes InSAR for wide-area and historical deformation and explicitly combines satellite results with ground instrumentation and a multi-sensor monitoring platform.
Official Sixense source ↗SkyGeo — civil infrastructure InSAR
SkyGeo’s official civil-engineering material positions historical InSAR, construction-period monitoring and long-term asset review as complementary to conventional monitoring across roads, rail, utilities, buildings and other infrastructure.
Official SkyGeo source ↗Technical Boundaries
InSAR can be powerful without being universal.
A credible InSAR platform should make the limits easy to find. RAUZ treats suitability and uncertainty as part of the technical output, not as fine print after the interpretation.
Line-of-sight geometry
Coherence, vegetation and changing surfaces
Fast or sudden movement
Reference frame and calibration
Cause versus correlation
RAUZ rule: do not use InSAR to create false certainty. Use it to widen the evidence base, test hypotheses and identify where ground investigation, field monitoring, inspection or additional review is justified.
Why RAUZ
Independent interpretation above the satellite product.
RAUZ is the environmental intelligence and monitoring platform of Rauz Caucasus LLC in Tbilisi, built for remote-first international delivery. The InSAR capability is intentionally vendor-neutral: the platform can work from an agreed public or commercial InSAR source and focus on what the evidence means for the asset or natural system.
- Vendor-neutral use of public or commercial InSAR products.
- QA/QC before engineering or environmental interpretation.
- Spatial patterns reviewed together with time-series behaviour.
- InSAR compared with survey, GNSS and geotechnical instruments where appropriate.
- Groundwater, weather, geology and project events added when they affect the mechanism.
- Independent review without forcing replacement of the existing monitoring system.
- AI-assisted screening and reporting with engineer-reviewed conclusions.
- Traceable separation between observation, inference, uncertainty and action.
Frequently Asked Questions
Questions that should be settled before an InSAR dataset becomes a project conclusion.
What does InSAR measure?
Can RAUZ use public InSAR data?
Can InSAR replace ground monitoring?
Can InSAR be compared with settlement or GNSS data?
Is InSAR suitable for vegetated slopes?
Can RAUZ identify the cause of movement from InSAR alone?
What should a client send for a first review?
Official Reference Library
Primary sources behind the technical context on this page.
These sources support the general InSAR principles, public data environment and international examples described above. Project-specific conclusions must still use the controlled records for the actual site.
Copernicus Land Monitoring Service — EGMS
Official European Ground Motion Service overview, product documentation and Sentinel-1-derived datasets.
Open official EGMS source ↗USGS — InSAR
Official explanation of interferometric SAR and its use for high-density land-surface deformation measurements over large areas.
Open official USGS source ↗ESA — Ground Displacement
Official Earth-observation capability material describing satellite radar data for tracking ground displacement associated with natural and human-driven processes.
Open official ESA source ↗USGS — Barry Arm Landslide Data
Official remote InSAR monitoring dataset for a large landslide in Alaska where field access is challenging.
Open official USGS case ↗Discuss an InSAR Scope
Start with the ground-motion question, not the satellite name.
Send RAUZ the project or asset location, the movement concern, the period of interest and any existing ground or satellite data. A first technical discussion can determine whether the useful next step is public-data screening, commercial InSAR, historical analysis, ground-data comparison or a recurring monitoring workflow.
What to send
Location or AOI, asset type, project stage, movement question, expected mechanism, existing monitoring plan, representative data, geology/groundwater information and the decision the team needs to support.
What RAUZ can define
Suitable data source, archive or monitoring period, required QA/QC, comparison datasets, expected limitations, output format and whether a focused review or recurring InSAR Intelligence workflow is justified.