SAR Readiness QA

What This Tool Does

SAR Readiness QA prepares SAR for downstream analysis by producing calibrated backscatter, RTC support, optional coherence proxy, and readiness diagnostics.

What You Need

Input	Required	Notes
`input_sar` or `input_sar_bundle`	Yes (exactly one)	Primary SAR source in raster mode or bundle mode.
`input_dem`	Yes	DEM used for RTC support.
`pair_sar` or `pair_sar_bundle`	No	Optional pair scene for coherence-proxy estimation (at most one).
`input_measurement_key` / `pair_measurement_key`	No	Optional selectors for bundle mode.

Optional controls include look-angle checks, auto-coregistration settings, speckle_window, z_factor, and output_prefix.

What You Get

Output Key	Description
`sar_backscatter_calibrated`	Calibrated primary SAR raster.
`speckle_filtered`	Speckle-filtered raster.
`rtc_factor`	RTC factor raster.
`coherence_proxy`	Optional pair-based coherence proxy raster.
`readiness_rule_trace`	JSON readiness rule evaluation trace.
`readiness_blockers`	CSV blocker list for triage/reporting.
`summary`	JSON summary with warnings, timings, readiness score, and outputs.
`html_report`	Optional HTML report.

Example

import whitebox_workflows as wbw

env = wbw.WbEnvironment()
result = env.sar_analysis_readiness(
        input_sar_bundle="sentinel1_scene.SAFE",
        input_measurement_key="vv",
        input_dem="dem_30m.tif",
        pair_sar_bundle="sentinel1_scene_pair.SAFE",
        pair_measurement_key="vv",
        auto_coregister_pair=True,
        coreg_max_offset_px=24,
        coreg_decimation=4,
        coreg_min_overlap_fraction=0.20,
        output_prefix="sar_ready"
)

Common Questions

Q: Why is coherence_proxy sometimes missing? A: It is only written when a pair scene is supplied.

Q: What should I review first for go/no-go? A: Check summary.warnings, summary.readiness_score, and the readiness_blockers CSV.

Q: Why are there auto-coregistration warnings? A: They indicate pair-scene harmonization was required before coherence-proxy estimation.