You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some basic checks can be implemented on top of the database. The most important one is the speed check: if the speed is higher of 30 m/s max speed, the point should be flag outlier. It could be implemented by computing the moving average over three points.
Speed outlier check is in place; by default it checks if the column speed_km_h has a value greater than a certain value, which can be defined in the environment. The logic to detect outlier can be customized per parser.
Hei Niccolo, great that the speed outlier check is now in Place! One question regarding this: Is it possible to define the speed outlier as speed_m_s instead of km_h? As you see above when FraFra opened this thread, we work with speeds in m/s. Obviously, we can re-calculate, but things like that usually lead to some issues / confusion. So if possible, I would prefer to stick to m/s
Some basic checks can be implemented on top of the database. The most important one is the speed check: if the speed is higher of 30 m/s max speed, the point should be flag outlier. It could be implemented by computing the moving average over three points.
This issue depends on #3.
The text was updated successfully, but these errors were encountered: