> 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/user/guide/devices-and-settings/location-and-movement/parking-detection.md).

# Parking detection

Tune idle time and speed thresholds to control trip and stop boundaries in reports, with optional ignition or motion sensor confirmation.

**Parking detection** defines when a vehicle counts as **parked** versus **in a trip**, the basis for trips, stops, and parking in reports. It identifies when an object has been stationary long enough, below a speed threshold, optionally confirmed by ignition or a motion sensor.

![](https://2096203889-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F446mKak1zDrGv70ahuYZ%2Fuploads%2Fgit-blob-4bd65941baf5ae81d287f8717fb80788ef5da2c4%2Fimage-20240815-183001.png?alt=media)

## Settings

* **Minimum idle time**: How long an object must remain stationary before it's considered parked. Range 1–1440 minutes, default 5.
* **Idle speed threshold**: The speed under which the object must stay to be detected as parked. Range 0–200 km/h, default 3.
* **Use ignition**: Confirm parking using the ignition state. Appears only if an **ignition sensor** is configured.
* **Use motion sensor**: Confirm parking using the motion sensor. Appears only on devices with a **motion sensor**.

A **Reset to defaults** button restores the default values.

## How conditions combine

* By speed and time: parking is detected when speed drops below the threshold and stays there longer than the minimum idle time. Stops shorter than the minimum idle time don't interrupt the trip.
* Considering ignition: the trip starts when speed ≥ threshold and ignition is on. The trip ends when speed drops below threshold and either the idle time is exceeded or ignition is off.
* Considering motion sensor: the trip starts when speed ≥ threshold and the motion sensor detects movement. The trip ends when speed drops below threshold or motion stops, and the idle time is exceeded.
* Considering both: ignition takes precedence over the motion sensor.

## Availability

Available on all devices except a few models that don't support parking detection.

## Limitations

* The **Use ignition** and **Use motion sensor** options only appear when the corresponding sensor exists on the device.
* Tuning idle time and speed threshold to the vehicle's real behavior minimizes false detections and improves trip accuracy.

## See also

* [Tracking mode](/docs/user/guide/devices-and-settings/location-and-movement/tracking-mode.md): how often the device reports position.
* [Ignition source](/docs/user/guide/devices-and-settings/location-and-movement/ignition-source.md): how ignition is determined.


---

# 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/user/guide/devices-and-settings/location-and-movement/parking-detection.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.