> 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

Display interval-mode device data as map tracks by generating tracks and disabling the Split by stops option in the Navixy tracking settings.

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 devices 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](https://3650643549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgDb43gtyXcm1Av4h1np%2Fuploads%2Fgit-blob-82fe2303be0decc03e1a060202d453e7012a1392%2Fimage-20231130-084047.png?alt=media)

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

![Displaying tracks in interval mode](https://3650643549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgDb43gtyXcm1Av4h1np%2Fuploads%2Fgit-blob-75271ed50763431b965bdb58e68a678cc6817584%2Fimage-20231130-084219.png?alt=media)

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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.