> 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/vehicle-telematics-technology/video-telematics/video-telematics-101/what-makes-dash-cam-video-reliable-for-fleets-a-benchmarking-guide/test-framework-checklist-to-videocameras-in-navixy.md).

# Test framework checklist for videocameras in Navixy

Dashcam testing checklist for Navixy covering video quality, GPS accuracy, streaming stability, compression, and AI recognition rates.

| Video quality             | Resolution                      | Pixels (e.g., 1920×1080) | ≥ 640x360 minimum to record an event                |
| ------------------------- | ------------------------------- | ------------------------ | --------------------------------------------------- |
| <p><br></p>               | Video sensibility               | High / Medium / Low      | Reducing or increasing the frequency of events.     |
| Frame Rate                | Video transition                | FPS                      | ≥ 10 FPS                                            |
| Dynamic Range             | Low-light clarity transition    | Seconds                  | At least 1 sec.                                     |
| GPS Performance           | Location accuracy               | Meters                   | ≤ 15 m (open sky)                                   |
| <p><br></p>               | Streaming stability             | Seconds                  | ≤30 seconds                                         |
| Network & Streaming       | Data usage at 720p              | MB/hour                  | ≤ 300 MB/h                                          |
| Compression Quality       | Protocol Data                   | H264 or H265             | At least H264                                       |
| Video Quality Recognition | Plate recognition               | Meters                   | Readability at a range of 0-30–80 km/h.             |
| <p><br></p>               | Face recognition/Id recognition | Meters                   | Alerts for ID recognition or driver not recognized. |
| <p><br></p>               | Stress test                     | Frequency                | Wrong events/minute                                 |
| Range of temperature      | Operating temp                  | °C                       | –20°C to +60°C                                      |
| Maintenance               | OTA firmware                    | Pass/Fail                | Pass                                                |


---

# 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/vehicle-telematics-technology/video-telematics/video-telematics-101/what-makes-dash-cam-video-reliable-for-fleets-a-benchmarking-guide/test-framework-checklist-to-videocameras-in-navixy.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.