Support Document
0 mins to read
•GPS Curve Log Reasons
Support Document
0 mins to read
•Learn more about the GPS Curve Log reasons, based on the Ramer-Douglas-Peucker algorithm, including how each run of the curve is considered as an isolated atomic event, and why the curve algorithm is run.
GPS curve logging is based on the Ramer-Douglas-Peucker algorithm, with each run of the curve being considered as an isolated atomic event. The reasons the curve algorithm is run is dependant on several factors, either;
Log Reason | Description |
CurveBased | This GPS point was logged by running the curve algorithm on the GPS positional data. |
CurveSpeed | This GPS point was logged by running the curve algorithm on the GPS speed data. If the GPS valid flag is marked as invalid then the speed was received from the engine. |
CurvePositionEstimateError | The curve algorithm was run up until this point because the difference between the actual position of the vehicle and the estimated position of the vehicle (based on the last set of data sent to MyGeotab) is greater than the allowed threshold. |
CurveSpeedEstimateError | The curve algorithm was run up until this point because the difference between the actual speed of the vehicle and the estimated speed of the vehicle (based on the last set of data sent to MyGeotab) is greater than the allowed threshold. If the GPS valid flag is marked as invalid then the speed was received from the engine. |
CurveTimeOut | The curve algorithm was run up until this point because the timeout value of 100 seconds was reached. |
CurveOtherEvent | The curve algorithm was run up until this point because of a non-GPS based event, currently only includes the saving of a system fault. |
CurveZeroSpeed | This GPS point was logged because the vehicle either came to a stop or started moving from a stop. If the GPS valid flag is marked as invalid then the speed was received from the engine. |