Stops visualization on map

Greetings,

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.

Hello,

Markers on the track, in new charts are given by the system in places, where the stop was indicated - it means, that according to trip detector, the trip is in progress, but the speed parameter in the message is 0 km/h.

There are no options to filter markers output on the map - all of them are indicated and some of them of course might have a duration 0 sec - that means, your tracker sent a message with 0 speed, stayed awhile silent and next message contained the speed >= min. movement speed in trip detector.

Having in mind, that filtering of markers is impossible, you should think over trip detection settings of frequency of sent messages from the tracker - both ways will give you duration on markers.

Thanks for replying serd!

Could you please clarify about adjusting the trip detection speed? Should I increase or decrease it?

As monitoringnet says, adjusting the HW configuration would impact gprs costs.

Hello,

As most of you know, those stops appeared in your reports because the time interval between the speed below trip detector's and above (two consecutive messages) currently is added into the "movement" state of the unit. That was done due to two reasons - to match mobile app's mileage and reports + to have mileage in reports more accurate (closer to mileage "in all messages"). SOme of the trackers are set up to fall asleep once they stop - basically the system receives the speed 0, then in several minutes a message already contains speed and therefore your stop contains only one message - which has duration 0 sec.

We had a conversation regarding possible additional options in order to let you have the stops as they were previously.
All variants were considered inappropriate in the current version of Wialon - what will be done is displaying N/A in the markers, where the stop is detected as 0.

What Wialon can do to avoid such stops now:
- increase minimum speed in the trip detector. This will let you have stops longer.
- create a sensor with inverted speed parameter (like the one in the attachment) - "digital sensors" table will give you the stops as they were before the end of the May 2016 - when yo uclick on the date in that table - you will automatically be focused on the necessary marker on the track
- filter stops in the respective table - this will not filter your markers but will give you longer stops in result - their overall count will be reduced

The most effective though will be adjusting your equipment - most of "intellectually" set trackers allow you to configure them so they fall asleep in several minutes after the stop, keeping normal messages frequency forawhile (Teltonicas, Ruptellas, Galileos for instance). AFAIR - we discussed that with Petar in June already. Some 2-3 minutes will be more than eough to have correct stops - this should not impact traffic costs much. If you need additional assistance with setting your trackers up - please, let us know to support@gurtam.com mentioning the device model and attaching some typical settings of yours - we'll try to help you with settings. Frequency of 1 message per 10 seconds is usually enough for that.