Flash-Lidar Frame Coverage
Calculate flash-lidar points per frame and angular pixel pitch.
Description
Flash-lidar frame sampling divides angular fields by pixel counts.
Flash-lidar frame sampling divides angular fields by pixel counts. The nominal point count assumes one point per pixel.1
Calculate flash-lidar points per frame and angular pixel pitch.
When to use Flash-Lidar Frame Coverage
Use this tool to calculate flash-lidar points per frame and angular pixel pitch.
Prepare the optical measurements, geometry, fitted coefficients or caller-selected thresholds requested. Confirm wavelength, radius/diameter, pulse-width, angle and unit conventions before running the calculation.
How to use Flash-Lidar Frame Coverage and understand its results
- Prepare the optical measurements, geometry, fitted coefficients or caller-selected thresholds requested. Confirm wavelength, radius/diameter, pulse-width, angle and unit conventions before running the calculation.
- Enter horizontalPixels, verticalPixels, horizontalFieldDegrees, verticalFieldDegrees using the field table and calculation rules, then run the tool.
- Read pointsPerFrame, horizontalDegreesPerPixel, verticalDegreesPerPixel. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| horizontalPixels | Horizontal pixels | integer; minimum: 1 | Required |
| verticalPixels | Vertical pixels | integer; minimum: 1 | Required |
| horizontalFieldDegrees | Horizontal field of view (°) | number; minimum: 0 | Required |
| verticalFieldDegrees | Vertical field of view (°) | number; minimum: 0 | Required |
Enter positive integer dimensions and nonnegative angular fields. Return point count and horizontal/vertical degrees per pixel.
points=horizontalPixels×verticalPixels; pitch=field/pixels Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| pointsPerFrame | Points per frame | integer; minimum: 1 |
| horizontalDegreesPerPixel | Horizontal angular pitch (°/px) | number; minimum: 0 |
| verticalDegreesPerPixel | Vertical angular pitch (°/px) | number; minimum: 0 |
{
"input": {
"horizontalPixels": 1024,
"verticalPixels": 512,
"horizontalFieldDegrees": 60,
"verticalFieldDegrees": 30
},
"output": {
"pointsPerFrame": 524288,
"horizontalDegreesPerPixel": 0.05859375,
"verticalDegreesPerPixel": 0.05859375
}
}Limitations and assumptions
Uses pixel count rather than endpoint spacing count. Missing returns, lens distortion and projected ground area are not modeled.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Lidar Point Density: Estimate lidar point density after a caller-supplied swath-overlap adjustment. For a complementary task, use Repeat-Orbit Swath Coverage: Estimate nominal repeat-orbit swath coverage against a supplied reference surface area.
References
-
Flash-Lidar Frame Coverage — tool.io
Similar or alternative tools
- Lidar Point Density
Estimate lidar point density after a caller-supplied swath-overlap adjustment.
- Repeat-Orbit Swath Coverage
Estimate nominal repeat-orbit swath coverage against a supplied reference surface area.