~~NOTOC~~
====== Routes ======

A route is a series of road sections that the tracked device travels over a specified period of time. A route always has a start point (A) and an end point (B). The device sends position and event data to the Service Provider's center at the intervals specified in the schedule specified in the [[software: desktop: manual: handle-devices: send-commands | settings]]. Events that occurred while traversing the route (eg stopping, waiting) divide the route into road sections.

You can get information about each road section separately, as well as event and position submission points, both on the map and on various data sheets and diagrams.

===== Route model =====

{{ en:software:common:manual:route-model.png?500&direct |Route model}}

A and B: The position of the device at the start and end time of the "measurement", respectively. In reality, A and B are the points from which the GPS device sent position data and their time is closest to the limits of the query time interval we specified.

E1 ... En: Events that occurred while traversing the route. The tracking system divides the route into wait and run sections based on start-wait events.

A wait (waiting point) is a stop where the device (or its carrier) has been at the minimum time specified during segmentation.

A journey (section of road) is the section of road bounded by two waiting points on which the device has moved.

===== Route on the map with event or GPS position entry points =====

Event points that divide the route into road sections are shown on the map by numbered markers:

{{common:software:common:manual:route-with-points.png?500&direct |}} {{common:software:common:manual:route-with-data-sending-points.png?500&direct|}}
\\
\\
After querying, we can get detailed graphical and textual information about the route, its points and sections.