Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Geofence Entry/Exit Events Are Too Frequent

This article explains why this behaviour occurs, how Perspio processes GPS and geofence data, and provides best practices to reduce event frequency while maintaining data accuracy.

This article explains why this behaviour occurs, how Perspio processes GPS and geofence data, and provides best practices to reduce event frequency while maintaining data accuracy.

 

How Geofence Events Work

When an asset equipped with a GPS-enabled device moves in or out of a geofence boundary, Perspio receives a location update and compares it against all existing geofence coordinates.

If the asset’s last known position was outside and the new position is inside a geofence (or vice versa), Perspio triggers:

  • A Geofence Entry Event

  • Or a Geofence Exit Event

These events are logged in the system and can be used for:

  • Workflow triggers (notifications, servicing, or reporting)

  • Historical activity tracking

  • Auditing and compliance reporting

However, GPS readings are not always static or perfectly accurate, which can result in unexpected or frequent event triggers.

Why Frequent Entry/Exit Events Occur

1. GPS Drift (Random Location Variations)

GPS devices can occasionally report slight position changes even when the asset is stationary. This phenomenon, known as GPS drift, happens due to natural signal inaccuracies caused by:

  • Satellite signal interference or weak coverage

  • Weather conditions or cloud density

  • Reflections from nearby structures (e.g., metal sheds, tall buildings)

  • Device antenna placement or environmental obstructions

When these small coordinate shifts occur near a geofence boundary, Perspio may interpret them as multiple entry and exit movements in rapid succession.

Example:
A parked truck inside a yard geofence may momentarily appear outside the geofence due to drift, triggering an exit, followed shortly by an entry when the signal stabilises.

2. Small or Irregular Geofence Shapes

Very small or narrow geofences increase the likelihood of repeated events. A geofence that tightly wraps around an asset’s normal parking location provides no buffer for positional error.

Recommendation:
Whenever possible, enlarge the geofence or apply rounded boundaries around sensitive areas to accommodate GPS variance. A margin of 15–30 metres is often sufficient to prevent false triggers.

3. High-Frequency Device Reporting

Some devices are configured to send frequent position updates (e.g., every few seconds). When an asset moves near the edge of a geofence, this can produce a high volume of alternating entry/exit detections.

Recommendation:
If the geofence is not mission-critical (e.g., for alerts), consider reducing the device’s position reporting frequency to balance accuracy and event volume. Contact our support team to investigate the frequency of reporting.

4. Device Reconnection or Wake Events

Battery-powered or motion-activated devices may “wake up” and send a new location on power-up or vibration detection. Each wake event prompts Perspio to re-evaluate geofence status, which can appear as repetitive entries/exits if the asset has not moved significantly.

Recommendation:
If using battery powered trackers, verify their wake/sleep configuration in the device management console to reduce unnecessary updates. Only with devices managed by you.

5. Overlapping Geofences

If two or more geofences overlap partially, an asset located in that overlapping zone can repeatedly trigger entry/exit events between them, even though it has not physically moved much.

Recommendation:
Check for overlapping boundaries in the Geofences list or Map View, and consolidate or realign them if possible.

How to Diagnose Frequent Events

  1. Open the Geofences Module

    • Navigate to Inventory → Geofences.

    • Select the affected geofence from the list.

  2. Review Asset Activity

    • Use the Events tab or Asset Inspector to check entry/exit timestamps.

    • Note if events occur within seconds or minutes of each other.

  3. Verify Device Communication Frequency

    • Navigate to the Device Health screen.

    • Check how often the device reports GPS updates.

  4. Cross-check Location Trail

    • Open the Map view for the affected asset.

    • Enable the Trail or Trip History overlay to see if the device’s reported positions fluctuate within a small area.

Best Practices to Reduce False or Excessive Events

  • Increase Geofence Radius
    Add a buffer zone around the boundary to account for GPS variance.

  • Avoid Placing Geofences on Exact Perimeters
    For example, instead of aligning with a gate line, offset the geofence inward to ensure stationary assets remain “inside.”

  • Optimise Device Reporting Intervals
    Use moderate reporting frequencies (e.g., 1–5 minutes) for stationary or slow-moving assets.

  • Filter Workflow Triggers
    Configure workflows to trigger alerts only if multiple entries/exits occur within a defined time threshold (e.g., “ignore if within 2 minutes”).

  • Monitor Device Accuracy
    Review devices that consistently cause high-frequency location changes. A poor GPS antenna or installation position may need correction.

Summary

Frequent geofence entry/exit events are typically caused by GPS signal variations, small boundary zones, or device over-reporting rather than actual asset movement.

Perspio records these events faithfully based on live GPS telemetry, which means the system behaves correctly — but the data may appear noisy due to environmental and configuration factors.

Implementing buffer zones, optimising update intervals, and verifying device placement can significantly reduce false triggers and improve operational reporting accuracy.