---
service: "Publicasta"
schema_version: "1.0"
article_id: 544
title: "Geofences and object proximity"
language: "en"
default_language: "en"
canonical_url: "https://help.gpsoperator.com/geofences?lang=en"
json_url: "https://help.gpsoperator.com/geofences.json?lang=en"
api_url: "https://help.gpsoperator.com/api/public/v1/channels/gps_operator_help/articles/geofences?lang=en"
channel_url: "https://help.gpsoperator.com/api/public/v1/channels/gps_operator_help"
channel_articles: "https://help.gpsoperator.com/api/public/v1/channels/gps_operator_help/articles"
search_url: "https://help.gpsoperator.com/api/public/v1/search"
documentation_url: "https://publicasta.com/api-docs#reading-publicasta"
openapi_url: "https://publicasta.com/api-docs/openapi.json"
published_at: "2026-09-08T11:34:54+00:00"
updated_at: "2026-09-08T11:34:54+00:00"
translations:
  - language: "en"
    html_url: "https://help.gpsoperator.com/geofences?lang=en"
    markdown_url: "https://help.gpsoperator.com/geofences.md?lang=en"
    json_url: "https://help.gpsoperator.com/geofences.json?lang=en"
  - language: "ru"
    html_url: "https://help.gpsoperator.com/geofences?lang=ru"
    markdown_url: "https://help.gpsoperator.com/geofences.md?lang=ru"
    json_url: "https://help.gpsoperator.com/geofences.json?lang=ru"
---

# Geofences and object proximity

> Configure up to four rectangular map zones, distinguish display from rule state and set supported tracker or stationary-object proximity conditions.

The service has two different geographic mechanisms: rectangular tracking zones on the map and proximity rules between two objects. They are configured in different places and solve different tasks.

 ## Rectangular map zone

 Open the map, select a device and open the alarm settings panel. Each tracker has four colour-coded zone slots. Every slot has its own state and notification channel.

 ![Alarm settings panel with four tracking zones on the map](https://help.gpsoperator.com/storage/projects/47/pages/544/2026/09/d2cfcab8-eac2-4281-8b72-8948e6db4fa4.webp)

 *Green zone 1 is enabled and the other slots are disabled. “Hide geofences from the map” changes only rectangle visibility, not the rule state.*

 To create or change a shape, select the edit icon next to the required slot. A rectangle with corner handles appears on the map. Move and resize it around the required area, enter a clear name and confirm the change.

 ![Editing a rectangular geofence boundary and name](https://help.gpsoperator.com/storage/projects/47/pages/544/2026/09/02b3ec73-19fc-46e0-9bac-74ec36d95697.webp)

 *The displayed rectangle is what gets saved. Leave some margin around a gate, road or wall: normal GPS-point variation near a boundary can create repeated entries and exits.*

 After saving, close and reopen the editor. Check the slot number, colour, name, boundary, **Enabled** state and required channel.

 ## What activation means

 The service detects entry or exit from received coordinates. If no suitable points were received near the boundary, or the device was offline for a long time, the exact crossing may not appear in the log.

 Check the individual history points, not only the line joining them. A log entry and email delivery are separate stages.

 ## Hide, disable and delete

 - **Hide geofences from the map** keeps the rules but stops drawing their rectangles.
- **Disabled** in a zone row stops that rule while preserving its slot.
- the delete icon removes the zone configuration.

 Before deleting, verify the tracker and zone number.

 ## Object proximity

 **Settings → Geofences** contains a separate proximity-rule table. Select a central object, a tracked device, radius, state and notification type.

 ![Creating a proximity rule between central and tracked objects](https://help.gpsoperator.com/storage/projects/47/pages/544/2026/09/78b4f65c-fe8e-4419-bd17-0a28fa2a330f.webp)

 *The centre can be a tracker or an available stationary object. A moving centre uses its current suitable coordinate.*

 Enter a numeric radius supported by the current form. Do not use the `MAX` option: it appears in part of the old interface but is not handled consistently by the active processing chain.

 If a rule does not activate, check both positions at the relevant time, the radius, rule state, event log and delivery channel. Do not delete history or recreate the device to reset a geofence.