> 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/qna/using-navixy/lbs-signals-and-false-geofence-events.md).

# LBS Signals and false geofence events

## Question

Are LBS signals taken into account when generating geofence entry and exit events, and can they cause false positives in geofence reports?

## Answer

Yes. LBS-based positions can be used by the platform, and they can cause false positives in geofence reporting.

This usually happens when:

* the tracker cannot provide reliable GPS/GNSS (indoors, weak signal, etc.)
* the tracker sends an LBS position with a large radius
* the LBS radius overlaps a geofence boundary

If the radius overlaps the geofence, the platform can interpret it as an exit and later an entry.

### How to reduce false positives

Check the device's GSM/LBS data quality first.

Then adjust **LBS detection radius** in device settings so the LBS radius remains within the expected area.

## Links

* [LBS detection radius](/docs/user/guide/devices-and-settings/location-and-movement/lbs-detection-radius-block.md)


---

# 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:

```
GET https://navixy.com/docs/qna/using-navixy/lbs-signals-and-false-geofence-events.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.