> For the complete documentation index, see [llms.txt](https://docs.trafficmonitor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trafficmonitor.ai/ui/movements.md).

# Movements

{% hint style="success" %}
Movement patterns are based on [Frigate Zones](https://docs.frigate.video/configuration/zones). Configure zones properly before analyzing movements.
{% endhint %}

The Movements tab allows operators to see counts of objects through zones. This is commonly used to provide confirmation counts against manual counts and to determine if deployment and zones provide accurate counts.

## Sample screenshot

<figure><img src="/files/B9OLhMjwF8yF54mxlJ7a" alt=""><figcaption></figcaption></figure>

## Descriptions

1. Movements Selection: Selectable filters to specify.
2. Movement behavior selection: Provides the ability to filter objects that go through *any* of the selected zones or objects that go through *only selected zones*.
3. Table of counts by object for selected movement pattern filters.

## Example of complex movement patterns

A complex intersection provides potentially dozens of combinations of turning behaviors and movement. The movements tab provides the ability to confirm against manual counts.

<figure><img src="/files/x2MIz2c3hH8AEC0KAD8M" alt="Screen shot of Frigate zones configured with 12 zones drawn on a busy 5-way intersection"><figcaption><p>Frigate zones configured with 12 zones drawn on a busy 5-way intersection</p></figcaption></figure>

<figure><img src="/files/kyJwjBRElOuBuoTZQA5c" alt="Slide of two manual hand-written counts for traffic movement through area"><figcaption><p>Example of manual, hand-written confirmation counts through various intersections (left image matches above zones)</p></figcaption></figure>


---

# 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://docs.trafficmonitor.ai/ui/movements.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.