We are also having negative feedback from clients and personally I do not think this works very well,
especially in reports.
How so? Well, here is the issue: a lot of vehicle stops that occur in real life are
presented on the system as "0 seconds", which means you cannot know the duration of that stop.
You can filter the report with duration, but that just means it will only show those FEW stops that have
positive time values, based on the new detection. So, the end-user doesn't have results
that reflect what actually happened (if and how long was a field worker on a certain location, buyer for example).
The point of STOPS is to know if a vehicle stopped somewhere, if you filter it you lose a lot of those
stops because of the new detection.
Very few stops trigger positive values now, that is the core issue.
Before it was simpler and meaningful: vehicle stops-time passes-vehicle starts moving,
the time in between is the stop duration.
Maybe experienced users have found a way to fix this somehow?
Please contribute if you can, looking at you @Buwo and @Baltika.
I repeat, filtering the reports will just hide the problem not fix it.
PS Sorry for the long post, but explaining the problem cannot fit in couple of sentences.