> 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/id/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).

# Daftar periksa kerangka uji untuk kamera video di Navixy

Daftar periksa pengujian dashcam untuk Navixy yang mencakup kualitas video, akurasi GPS, stabilitas streaming, kompresi, dan tingkat pengenalan AI.

| Kualitas video            | Resolusi                              | Piksel (mis., 1920×1080) | ≥ 640x360 minimum untuk merekam kejadian                                |
| ------------------------- | ------------------------------------- | ------------------------ | ----------------------------------------------------------------------- |
| <p><br></p>               | Sensitivitas video                    | Tinggi / Sedang / Rendah | Mengurangi atau meningkatkan frekuensi kejadian.                        |
| Laju bingkai              | Transisi video                        | FPS                      | ≥ 10 FPS                                                                |
| Rentang dinamis           | Transisi kejernihan pada cahaya redup | Detik                    | Setidaknya 1 detik.                                                     |
| Kinerja GPS               | Akurasi lokasi                        | Meter                    | ≤ 15 m (langit terbuka)                                                 |
| <p><br></p>               | Stabilitas streaming                  | Detik                    | ≤30 detik                                                               |
| Jaringan & Streaming      | Penggunaan data pada 720p             | MB/jam                   | ≤ 300 MB/jam                                                            |
| Kualitas kompresi         | Data protokol                         | H264 atau H265           | Setidaknya H264                                                         |
| Pengenalan kualitas video | Pengenalan plat nomor                 | Meter                    | Keterbacaan pada rentang 0-30–80 km/jam.                                |
| <p><br></p>               | Pengenalan wajah/Pengenalan identitas | Meter                    | Aturan peringatan untuk pengenalan identitas atau supir tidak dikenali. |
| <p><br></p>               | Uji beban                             | Frekuensi                | Kejadian salah/menit                                                    |
| Rentang suhu              | Suhu operasi                          | °C                       | –20°C hingga +60°C                                                      |
| Pemeliharaan              | Firmware OTA                          | Lulus/Gagal              | Lulus                                                                   |


---

# 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/id/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.