> 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.md).

# Video Telematics 101

This section covers the technical foundations of dash cam hardware, from the processors and codecs inside devices to structured methods for benchmarking video quality under real fleet conditions.

## Contents

* [Inside the dashcam: what really powers video telematics](/docs/expert-center/vehicle-telematics-technology/video-telematics/video-telematics-101/inside-the-dashcam-what-really-powers-video-telematics.md): How SoC architecture determines AI capability, compression, and feature support across budget and premium chips.
* [H.264 vs H.265 in fleet telematics: Cracking the codec puzzle](/docs/expert-center/vehicle-telematics-technology/video-telematics/video-telematics-101/h.264-vs-h.265-in-fleet-telematics-cracking-the-codec-puzzle.md): Comparing compression efficiency, thermal load, and licensing costs to guide dashcam deployment decisions.
* [What makes dash cam video reliable for fleets? A benchmarking guide](/docs/expert-center/vehicle-telematics-technology/video-telematics/video-telematics-101/what-makes-dash-cam-video-reliable-for-fleets-a-benchmarking-guide.md): Evaluating driver monitoring sensitivity, HDR performance, and low-light handling under real fleet conditions.


---

# 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/vehicle-telematics-technology/video-telematics/video-telematics-101.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.