Description
Return background-, range- and overlap-corrected lidar response.
Radar and lidar measurements combine propagation distance, pulse/gate geometry, background and instrument response. A local range or normalization term can be useful without detecting a target, retrieving atmospheric properties or establishing calibrated sampling resolution.
Return background-, range- and overlap-corrected lidar response.
When to use this tool
Use Lidar Overlap Normalized Return Term when checking the stated radar/lidar geometry, signal or transmission convention.
How to use the tool and how it works
- Enter signal, background, range, overlapFraction, energy. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read netSignal, correctedReturn. Use the output convention below.
Return background-, range- and overlap-corrected lidar response. Require range >= 0, energy > 0 and overlapFraction in (0,1]; netSignal = signal-background, correctedReturn = netSignal*range²/(overlap*energy).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| signal | Signal | Required. Finite number. |
| background | Background | Required. Finite number. |
| range | Range | Required. Finite number; minimum 0. |
| overlapFraction | Overlap Fraction | Required. Finite number; maximum 1; strictly above 0. |
| energy | Energy | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| netSignal | Net Signal | Required. Finite number. |
| correctedReturn | Corrected Return | Required. Finite number. |
{
"input": {
"signal": 10,
"background": 2,
"range": 5,
"overlapFraction": 0.5,
"energy": 2
},
"output": {
"netSignal": 8,
"correctedReturn": 200
}
}Limitations and assumptions
- Signed returns are retained; this local normalization does not retrieve an aerosol profile, extinction or calibrated backscatter.
- 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 instrument calibration and a complete appropriate retrieval/response model, including geometry and signal uncertainty, for actual remote-sensing conclusions.
References
Similar or alternative tools
- Lidar Window Transmission Basis
Return repeated-window transmission and corrected signal.
- Lidar Range Squared Factor
Apply the geometric range-squared factor to one background-corrected lidar signal sample without an atmospheric inversion.