Skip to content

Main content

Lidar Range Bin Path Length

Convert supplied two-way lidar bin time width to one-way range using an explicit positive propagation speed.

Loading tool…

Description

Convert a supplied round-trip timing width to a one-way range-bin width.

Atmospheric scalar terms require explicit averaging, spectral, geometric and propagation conventions. One fluctuation product is not a time-averaged flux, a squared deviation is not a full scintillation index, and a Nyquist interval does not de-alias radar velocity. Layer terms require compatible units and model assumptions.

Convert a supplied round-trip timing width to a one-way range-bin width.

When to use this tool

Use Lidar Range Bin Path Length when you already have roundTripTimeWidthSeconds, propagationSpeed and need to convert a supplied round-trip timing width to a one-way range-bin width.

How to use the tool and how it works

  1. Enter roundTripTimeWidthSeconds, propagationSpeed. 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 oneWayRangeWidth. Use the output convention below.

Require time width>=0 and propagationSpeed>0; return speed*roundTripTimeWidthSeconds/2.1

Input fieldMeaning and unitsAccepted input
roundTripTimeWidthSecondsRound Trip Time Width SecondsRequired. Finite number; minimum 0.
propagationSpeedPropagation SpeedRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
oneWayRangeWidthpropagationSpeed*roundTripTimeWidthSeconds/2; factor two removes round-trip travel.Required. Finite number.
json
{
  "input": {
    "roundTripTimeWidthSeconds": 0.000001,
    "propagationSpeed": 300000000
  },
  "output": {
    "oneWayRangeWidth": 150
  }
}

Limitations and assumptions

  • Speed in m/s gives meters. The factor two is for round-trip travel; no pulse shape, instrument response or achieved range resolution 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

Use the complete measurement and physical retrieval model. Include calibration, averaging, source geometry, spectral response and relevant transfer or flow effects when local weights and signal factors cannot establish the desired atmospheric quantity.

References

  1. Calculation and input contract: atmospheric-physics/lidar-range-bin-path-length — tool.io

Similar or alternative tools