> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/expert-center/faq-and-troubleshooting/access-iot-data/view-tracks-recorded-in-interval-tracking-mode.md).

# View tracks recorded in interval tracking mode

There are a large number of GPS devices that work in interval mode. They send points once in a certain period of time.

To save the device battery and traffic, this period can be large (some devices can transmit data once a day, for example, asset trackers for cargo transportation).\
However, such data does not allow for building accurate tracks on the map, and if the data transmission interval will exceed the idle time of the "parking" state, tracks will not be displayed at all and the device will always have the **Parked** status.

If you need to show the movement of the device as a line on the map in any case, then generate a track

![Displaying tracks in interval mode](/files/Rz7g822s3xpzeKJfapPh)

And disable the **Split by stops** option in the **Tracks** settings.

![Displaying tracks in interval mode](/files/C0L72RquoWI5fgkBeYVO)

In this case, all points transmitted by the device during the specified time period are shown as one trip.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/expert-center/faq-and-troubleshooting/access-iot-data/view-tracks-recorded-in-interval-tracking-mode.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.