> 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/lbs-detection-radius.md).

# LBS detection radius

Tune the LBS search radius for cellular and Wi-Fi positioning in Navixy. Use a larger radius in rural areas and a smaller one in cities.

Tunes cellular/Wi-Fi-based positioning, used as a fallback when GPS isn't available. It sets how far the Navixy platform trusts a base-station or Wi-Fi fix to pinpoint the device.

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

## Settings

* **Maximum radius**: The radius within which the platform trusts a cell-tower/Wi-Fi fix. Range 0–5000 m, set with a slider that offers locale-aware presets (for example 100, 500, 1000, 3000, or 5000 m in metric).

## Availability

Appears when the device supports LBS and the plan/account enables it, or for mobile app devices.

## Choosing a radius

* **Rural areas**: Use a larger radius. With fewer base stations, allowing more distant towers improves the chance of locating the device.
* **Urban areas**: Use a smaller radius. Dense towers provide enough signal for accuracy, so a smaller radius keeps precision higher.

## Limitations

* Larger radius = wider search but lower accuracy.
* On the map, LBS positions appear as a circle whose size equals the inaccuracy: a small circle means higher accuracy (typically urban), a large circle means more inaccuracy (typically rural).

## See also

* [Tracking mode](/docs/user/guide/devices-and-settings/location-and-movement/tracking-mode.md): how the device reports GPS position.


---

# 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/lbs-detection-radius.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.