Geofences on the map

Zones you define in the geofence studio render as overlays on the fleet map (by variant: operations or restricted). That gives you immediate context for rules while tracking units.

When a unit enters or leaves a zone, the system can record the transition in the map intelligence stream (entry/exit messages including unit and zone names).

Geofences are polygons or circles you draw on the terrain to mark zones with operational meaning: a site perimeter, a restricted area, a coverage zone assigned to a team. Once created in the geofence studio, they automatically project as semi-transparent layers on the tactical map, color-coded by variant (operations or restricted).

The operational utility of having zones visible on the main map is direct: the operations center sees simultaneously where each unit is and what rules apply at that point. If a patrol approaches a restricted perimeter, you don't have to switch tabs to confirm it's leaving its area; you see it. That coexistence of units + zones reduces coordination errors and speeds up decisions.

When a unit crosses the border of a geofence, the system can record the transition in the tactical log (entry or exit, with unit and zone names). That record stays as later audit and, if the zone rules define it, can trigger a dashboard alert or a mobile notification for the operator. That event → log → alert chain is what differentiates a decorative geofence from an operational one.

A good practice is to periodically review the drawn zones: terrain changes (construction, blocked accesses, expansions) and an outdated geofence generates noise. The tactical log is a good thermometer: if a zone generates entries/exits that nobody acts on, it's probably miscalibrated or unnecessary.