InSAR monitoring tools

The InSAR workbench takes the output of standard processing chains — MintPy, LiCSBAS, HyP3 or insarmaps velocity points, coherence layers and time series — and turns them into engineering numbers: geometrically corrected vertical rates, hazard classes, GNSS-validated results, error budgets and a report skeleton. Every tool below runs entirely in your browser. The chain is the point: points you import into the LOS converter feed the hazard classifier, the GNSS validation tool and the report generator without being re-imported.

Core processing tools

• LOS to Vertical Deformation Converter — projects LOS velocity onto vertical and along-slope components, propagates incidence-angle uncertainty, and exports CSV/SVG. Start here: most interpretation errors in InSAR reporting come from reading a LOS velocity map as vertical settlement.
• InSAR Site Suitability Check — screens an area for coherence, vegetation and slope-aspect conditions before committing to a monitoring campaign.
• Subsidence Gradient & Hazard Classifier — classifies vertical rates and gradients into low / moderate / high risk classes for screening reports.
• GNSS / Levelling Validation — compares InSAR-derived velocities against ground-truth stations and reports bias and scatter statistics.
• Error Budget Calculator — decomposes atmospheric, orbital, unwrapping and noise contributions, and checks the result against the tolerance you need.
• Displacement Time-Series & Velocity Analyzer — fits rates, detects breaks and plots the settlement curve for reporting.
• Deformation Report Generator — assembles the tables, statistics and charts into a reviewer-ready report skeleton with PDF/CSV export.

Which tool to reach for, and when

Each tool answers one question, and reaching for the right one early is half of the professional habit. Use the site pre-check before you commit budget to a campaign: if the physics of the area (vegetation, slope, atmosphere) will not support a usable product, the honest deliverable is a documented negative pre-check, not a forced map. Use the LOS converter for every velocity value that will enter a report: an LOS rate read as vertical settlement is the most common interpretation error in this field, and the correction needs each point's own incidence geometry. Use the hazard classifier once you have vertical rates and need to localise differential movement — gradients, not isolated values, damage structures. Use the time-series tool when the classifier has told you where and you need how it unfolded: steady, accelerating, or interrupted by a step that is usually an unwrapping artefact rather than geology. Use the GNSS validation tool before any map enters a report: independent ground truth turns a hypothesis into a defensible number, and the bias/RMSE pair is the sentence reviewers look for. Use the error budget to predict what the validation should have measured and to identify the dominant source — and use the report generator last, to assemble the evidence into a reviewer-ready skeleton that still requires your own conclusions. The discipline of using the chain, rather than jumping to the final plot, is what separates a screening deliverable that survives review from one that has to be reworked — and the hub is designed so that the chain, once started, stays consistent through every export and every re-analysis. Start with the pre-check, and let the stages decide the rest.

How the chain stays consistent

The tools share a data tray: points imported into the LOS converter pass to the classifier, the validation tool and the report generator without re-importing, and every export carries the column names, units and coordinate reference used at the previous step. That single chain is also why the site enforces one datum and one zone per file — a mixed file would propagate a silent shift through every downstream tool. The hub above is the working area; the workflow page is the procedural map (which gate to pass at each stage), and the InSAR basics and sample dataset guide pages are the reference material for the concepts and the expected numbers. The three perspectives — tools, procedure, theory — cover the same chain, and the sample exercise lets you rehearse it end to end in about ten minutes before touching your own data.

Monitoring & foundation instrumentation tools (in progress)

The following tools are under construction and will be published on this hub in the coming days: SBAS / PS-InSAR parameter selection, GNSS displacement time-series processing, inclinometer analysis, strut load monitoring, and groundwater level monitoring. They complete the monitoring workflow that the core tools above start.

Coordinate entry

InSAR points carry coordinates. The single site-wide coordinate conversion entry lives in the Coordinate Converter (also reachable from the Survey & coordinates board on the home page), so every tool in every discipline uses the same coordinate conventions.

Workflow and documentation

Follow the step-by-step route through the chain in the workflow guide. The InSAR basics document explains LOS geometry and velocity conventions; the CSV format specification lists every import column; the sample dataset guide documents expected results so you can verify the tools on your machine before using your own data.

Common questions

Why do I need to convert LOS to vertical first?

Because the satellite measures motion along a tilted viewing direction. A vertical rate of 12 mm/yr appears as roughly 9.5 mm/yr in the LOS measurement; reporting the LOS number directly understates settlement by 20–30%.

Can the tools read my MintPy / LiCSBAS output directly?

Yes for the standard velocity columns (velocity, los_vel) and CSV layouts documented in the format spec; the header matcher recognises the common column names automatically.

Is my survey data uploaded?

No. There is no upload path; everything is processed in your browser.

Are results suitable for an official geohazard assessment?

No — these are screening aids. Official assessments require licensed investigation and field verification by qualified professionals.