Skip to content

Main content

Rain Gauge Catch Correction Factor Tool

Calculate rain gauge catch correction factor from explicit caller-supplied inputs.

Loading tool…

Description

Correct rainfall depth using supplied catch fraction.

Atmospheric state formulas depend on absolute temperature, pressure reference, water mass/volume bases and layer assumptions. Local adiabatic, hydrostatic or precipitation terms can illustrate a supplied model without reconstructing an actual profile, validating an instrument or predicting weather hazards.

Correct rainfall depth using supplied catch fraction.

When to use this tool

Use Rain Gauge Catch Correction Factor when checking the stated atmospheric pressure, temperature, humidity or water-basis term.

How to use the tool and how it works

  1. Enter measuredDepth, catchFraction. 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 correctedDepth, missedDepth. Use the output convention below.

Correct rainfall depth using supplied catch fraction. Require measuredDepth >= 0 and catchFraction in (0,1]; correctedDepth = measured/catch, missedDepth = corrected-measured.1

Input fieldMeaning and unitsAccepted input
measuredDepthMeasured DepthRequired. Finite number; minimum 0.
catchFractionCatch FractionRequired. Finite number; maximum 1; strictly above 0.
Output fieldInterpretationReturned shape
correctedDepthCorrected DepthRequired. Finite number.
missedDepthMissed DepthRequired. Finite number.
json
{
  "input": {
    "measuredDepth": 8,
    "catchFraction": 0.8
  },
  "output": {
    "correctedDepth": 10,
    "missedDepth": 2
  }
}

Limitations and assumptions

  • Catch fraction is not estimated; wind effects, instrument calibration and actual precipitation are not determined.
  • 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

Use verified observations and an appropriate complete thermodynamic/profile analysis with explicit units, references and moisture assumptions for meteorological conclusions.

References

  1. Calculation and input contract: atmospheric-science/rain-gauge-catch-correction-factor — tool.io

Similar or alternative tools