<jok3r>
Here it is in a quick nut shell:
You really should Search the archives & threads.
LIDAR is purely a range finder.
It "calculates" a speed reading.
The issues are:
MOST LIDAR operators have a radar background.
This school of thought is that
cosine** error is in the favor of the motorist.
RE: straight line velocity, this IS true. an degree off axis of velocity direction is a mathematical calculation to how much LOWER a speed reading is.
Kinda a reference point thing.
Now carry that over to vehicles using LIDAR.
Once the operator stands off axis (median/shoulder/BDL) to clock traffic, using his/her "range finder" the view of the vehcile to the LIDAR light is now opened up to include the side of the vehicle.
This may increase or decrease the distances the return pulses carry to the LIDAR Rx for processing (
least squares*) USED to calculate a speed reading.
THAT's where the influences / errors affect a speed reading.
Mathematically, every 4 feet in a linear graph, is ~2.7 MPH (for 60 MPH being 88 feet per sec)
So not only is the LIDAR beam 3" square @ 1,000 feet.
The front to back (hood to roof) and vice versa, coupled with the side
pan or sweep "influences" are probable to effect the speed reading calculation.
ENHANCE this with the operator instructions (which *may* objectively, seem to attempt to combat this) to aim at one point AND FOLLOW IT during clocking. <<< this guarantees a "
pan" to the aiming operation >>>
A license plate for example.
Now all this is WITHIN the "external" environment reflections, when
swept by the operator, could, under certain instances lead to readings directly related to the motions of the operator aim solely.
Examples are sign posts, reflectors, objects, guardrails..........any reflective/refractive object.
The videos I reference above show this.
and ONLY because the -video- distances are shorter, is this easy to reproduce consistently.
Since distance isn't really a factor in a LIDAR gun determining a speed,
because LEOs use them beyond 1,000 feet, its a real issue and nearly every reading will be influenced and possibly "calculated" wrong.
Caveat Emptor.
-Suf
* (least squares)
raw data returns graph similar to this way even though school info is COMPLETELY different than speed processing of data (pulse) returns.
-------------------------------------------------------------------------------------------------------------------------------
** Cosine error graph (poor one I'll admit, credit:
http://www.jesbeard.com/figure5.gif)
MPH operator manual has the BEST cosine graph period. IMHO.
But I can never find it on the intarw3b.
-Suf
__________________
Speed detection makes errors. I can prove it. REPEATEDLY.
I'm no attorney, any method I describe may not work for you. You use my experience at your own risk. And as my experience,
this is not legal advice or be considered legal advice.
These are my opinions made from research and experience, sometimes using the technologies discussed.
NO part of my writings may be copied, or used in other writings, postings, articles or works without my permission.
Quoting from my postings ON THIS WEB SITE is allowed on this website for discussion purposes only.
I rent LIDAR and radar, even w/ speed signs!
LTI Marksman
AND Ultralyte 200LR, Stalker LIDAR, Kustom Pro Laser II, Pro Laser III, Laser Atlanta Advantage (R-style) and 6 Doppler's.