> 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/qna/using-navixy/raw-data/why-the-platform-may-consider-telematics-data-invalid.md).

# Why the platform may consider telematics data invalid

Platform filters data with zero satellites or invalid coordinates (0,0) to prevent inaccurate location display and track quality issues

## Question

Why can the platform ignore or mark certain telematics data as invalid?

## Answer

There are two key factors that can cause the platform to ignore or mark telematics data as invalid when received from a device:

1. **Zero satellites (0 satellites)**\
   When the device reports zero satellites, the platform automatically treats this as an invalid reading. As a result, even though the device may still be transmitting data, those points will not appear on the platform. This prevents inaccurate location data from being displayed.
2. **Invalid coordinates (0,0)**\
   If the coordinates received are (0,0), this indicates an invalid geographic point. Displaying such data could lead to a misleading interpretation of the route, so the platform filters these points out by default.


---

# 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/qna/using-navixy/raw-data/why-the-platform-may-consider-telematics-data-invalid.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.