Skip to content

Main content

Radar Gauge Bias Pair

Compare explicit matched radar and gauge precipitation depths, reporting an undefined gauge-ratio denominator separately.

Loading tool…

Description

Compare supplied radar and gauge rainfall depths additively and multiplicatively.

Weather accumulation records need explicit reset, carry, observation-time and area-weight conventions. Trace or missing precipitation differs from measured zero, and radar dBZ must be converted to a linear basis before a linear reflectivity mean. Supplied density, timing and weighting terms do not create a forecast or verify actual weather conditions.

Compare supplied radar and gauge rainfall depths additively and multiplicatively.

When to use this tool

Use Radar Gauge Bias Pair when you already have radarDepth, gaugeDepth and need to compare supplied radar and gauge rainfall depths additively and multiplicatively.

How to use the tool and how it works

  1. Enter radarDepth, gaugeDepth. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read additiveBias, multiplicativeBias, ratioDefined. Inspect ratioDefined before interpreting the associated values.

Require nonnegative depths; additive=radar-gauge, multiplicative=radar/gauge when gauge>0, otherwise zero with ratioDefined=false.1

Input fieldMeaning and unitsAccepted input
radarDepthRadar DepthRequired. Finite number; minimum 0.
gaugeDepthGauge DepthRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
additiveBiasAdditive BiasRequired. Finite number.
multiplicativeBiasMultiplicative BiasRequired. Finite number.
ratioDefinedFalse for gaugeDepth=0, with multiplicativeBias=0 placeholder; additiveBias is still radar-gauge.Required. Boolean.
json
{
  "input": {
    "radarDepth": 12,
    "gaugeDepth": 10
  },
  "output": {
    "additiveBias": 2,
    "multiplicativeBias": 1.2,
    "ratioDefined": true
  }
}

Limitations and assumptions

  • A zero-gauge ratio is undefined rather than a measured zero; no gauge/radar calibration, matched coverage or bias model is established.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review the original gauge/radar series, clock and accumulation metadata, including resets and missing intervals. Use the complete spatial or process model for basin precipitation, snow or forecasting; local depth contributions and reference gaps do not infer unobserved weather.

References

  1. Calculation and input contract: hydrometeorology/radar-gauge-bias-pair — tool.io

Similar or alternative tools