Fleetrun
Hecterra
NimBus
Other apps
Wialon for Android/iOS
Logistics
Wialon Local
Wialon Hosting
WiaTag
Configurator
LeaseControl
en
Contents
Visited Streets
  • tables

This report shows what streets were visited and when. Highways, roads, and other places with available addresses are also considered as streets in this report.

Below are the columns which can be presented in this kind of report.

ColumnDescription
StreetThe name of the street, road, highway, etc.
Initial locationThe place where the first message from this street was received. It can be the same as the previous cell or more detailed (for example, it can additionally contain a house number).
BeginningThe time when the unit started moving along the street.
EndThe time when the unit left the street.
DurationThe total time the unit was on the street.
MileageThe distance that was travelled by the unit while moving along the street.
Mileage (adjusted)The mileage subject to the coefficient set in advanced unit properties. More information about mileage in the report can be found here.
Avg speedThe average speed while moving along the street.
Max speedThe maximum speed detected while moving along the street. More information about speed in reports can be found here.
Streets countThe number of performed visits (can be helpful if there is grouping by years/months/weeks/days/shifts).
NotesAn empty column for your custom comments.

When clicking on a green cell in the table, the map is moved so that to display a point where the unit entered or left the indicated street, or reached the maximum speed.

Sometimes there can be gaps in cells. This means that only one message was received on this street, and therefore it is difficult to determine the length of time it was on the street, the mileage, and the average and maximum speed.

Interval filtration by duration, mileage, engine hours, speed range, trips, stops, parkings, sensors, fuel fillings, and drains can be applied to this table. For example, you can display only the streets where a particular sensor was turned on or the streets where the sensor was turned off. To specify the sensor, you can set a mask for it. This function is convenient, for example, for snow removal equipment — it allows you to know that the car did not just pass along the street, but had the brushes on.

Questions and answers

  Reports show incorrect mileage. What should I do?

Possible explanations and actions:

1. Outliers of data.

To detect such outliers, build a track of unit movement for the appropriate period. Outliers of data will be seen on the track as dashed lines.

Ways to overcome outliers:

  • Enable filtration of unit positional information in messages (on the Advanced tab of unit properties). This will not affect old messages but applied to new ones.
  • To correct data in reports, change settings of trip detection, in particular, reduce Maximum interval between messages and increase Minimum satellites.

2. Incorrect settings or operation of the mileage counter.

  • Check the mileage counter settings on the General tab of unit properties.


If you find a mistake in the text, please select it and press Ctrl+Enter.
Thank you for your feedback!
Report a mistake
Text with the mistake Comment
Maximum 500 characters