Surface Reflectance Consistency Analysis

Purpose

Surface Reflectance Consistency Analysis models and corrects directional reflectance artifacts (Bidirectional Reflectance Distribution Function effects) that vary with sun and view geometry. Produces nadir-normalized, view-invariant reflectance suitable for multi-temporal and multi-sensor comparison.

Typical Questions This Tool Helps Answer

• Are the apparent reflectance differences between these two dates a real land-surface change, or are they artifacts of different sun and view geometry?
• Which pixels carry strong BRDF effects that need normalization before a time-series vegetation index analysis is credible?
• Is our multi-date optical stack view-invariant enough to support cross-scene comparison, or does angular variation still bias the results?

Background

Background sections in this workflow family should make explicit how signal change can be confounded by acquisition geometry, atmosphere, calibration drift, and georegistration error. A reliable interpretation pipeline therefore separates physical signal change from acquisition artifacts through normalization, alignment, and uncertainty-aware thresholds.

Operationally, users should treat these tools as evidence-weighting systems rather than single-threshold detectors. The most robust workflows combine pre-processing diagnostics, method-specific quality indicators, and post-run plausibility checks before decisions are escalated.

BRDF consistency analysis addresses anisotropic reflectance, where measured brightness changes with viewing and illumination geometry. A common approximation is the kernel-weighted reflectance model $R( heta_i, heta_v,\phi)=f_{iso}+f_{vol}K_{vol}+f_{geo}K_{geo}$, used to normalize scenes before cross-date comparison.

Methodological Considerations

• Ensure geometric alignment is within the tolerance required by the downstream metric (pixel-level for many raster differences, sub-pixel for interferometric phase workflows).
• Separate radiometric normalization from change inference so threshold choices reflect physical behavior rather than acquisition artifacts.
• Prefer multi-run sensitivity checks on normalization and detection thresholds when decisions depend on marginal signal differences.

Practical Interpretation Pitfalls

Common failure modes include treating sensor noise as change signal, over-trusting single-date anomalies, and ignoring confidence/context layers when operational prioritization is made.

Inputs

Parameters

• profile (optional): fast, balanced, conservative; default balanced.
• stress_test_level (optional): none, standard, extreme; default standard.
• output_prefix (optional): artifact prefix; default brdf_consistency.

Outputs

Output artifact keys below are runtime outputs, not input parameters.

Summary diagnostics included

• Valid cell count
• Mean and standard deviation of normalization delta
• Mean consistency confidence
• Stress-adjusted mean consistency confidence
• Illumination angle stress indicator

Example

import whitebox_workflows as wbw

env = wbw.WbEnvironment()
env.brdf_surface_reflectance_consistency(
        input_red="red.tif",
        input_nir="nir.tif",
        input_green="green.tif",
        input_dem="dem.tif",
        solar_zenith_deg=40.0,
        solar_azimuth_deg=165.0,
        profile="balanced",
        stress_test_level="standard",
        output_prefix="outputs/brdf_consistency"
)

References

• Roujean, J. L., Leroy, M., & Deschamps, P. Y. (1992). "A Bidirectional Reflectance Model." Remote Sens. Env. 41(2–3), 123–134.

Parameter Interaction Notes

Performance and confidence are influenced by acquisition geometry and stress settings.

• Higher solar zenith values increase geometry stress.
• extreme stress testing applies stricter confidence penalties than standard.
• conservative profile is appropriate for high-governance reporting workflows.

QA and Acceptance Criteria

Use a staged acceptance approach for Surface Reflectance Consistency Analysis:

1. Validate all required inputs and angle ranges.
2. Confirm output rasters and summary JSON are generated under the selected prefix.
3. Verify confidence maps are spatially coherent with expected terrain/illumination behavior.
4. Verify stress-adjusted confidence aligns with policy thresholds.

Recommended acceptance checks:

• summary.workflow is brdf_surface_reflectance_consistency.
• Output inventory in summary.outputs matches generated files.
• Stress-adjusted confidence does not exceed unadjusted mean confidence.

Advanced Operational Guidance

For production deployment of Surface Reflectance Consistency Analysis:

• Keep consistent profile/stress settings across comparison campaigns.
• Archive JSON and HTML artifacts with project metadata for audit traceability.
• Use stress-adjusted confidence as the decision gate for high-angle scenes.

Implementation Patterns

Common implementation patterns with Surface Reflectance Consistency Analysis:

• Baseline monitoring with balanced + standard.
• Governance validation with conservative + extreme.
• Periodic reruns with fixed settings for longitudinal comparability.

Related Tools

Use Surface Reflectance Consistency Analysis together with upstream conditioning and downstream validation tools in the same bundle to ensure end-to-end consistency and stronger decision confidence.

Common Questions

Q: Why is stress-adjusted confidence lower than mean confidence?
A: Stress adjustment applies an illumination-geometry penalty based on zenith angle and selected stress level.

Q: What if optional green band is unavailable?
A: The workflow runs with red, nir, and dem; green is optional.

Q: How do we pick between standard and extreme stress tests?
A: Use standard for routine QA and extreme for conservative governance gates.