Skip to main content

​
Overview

A zone always has a centre point (lat_center, lng_center). You can also give it a boundary: a polygon made of GPS points that traces the exact area the zone covers. The boundary is stored with the zone and returned by the zone endpoints. The dashboard draws it on the zone map and on each team’s zone map, so dispatchers see at a glance which area a zone and its teams cover. If you use the optional teams and dispatch module, the boundary also counts when wede ranks teams for an event. See Boundaries and team ranking.

​
Defining a boundary

In the dashboard, open Zones, edit a zone and click on the map to place the points of the polygon. Through the API, send the boundary as an array of { lat, lng } points when you update the zone:
Updating a zone needs a session with the zones:manage permission (company_admin, company_tech or country_admin). A tenant cannot change the boundary of a zone shared with other tenants (403 shared_zone). Use at least three points so the boundary forms an area. Points are joined in the order you send them and the last point connects back to the first. GET /v1/tenant/zones and GET /v1/tenant/zones/:zone_code return the zone with its boundary.

​
Zones without a boundary

A boundary is optional. A zone without one is represented by its centre point, and everything else about the zone works the same way: its connectivity state, its teams and its events.

​
Boundaries and team ranking

When the score engine ranks teams for an event, it checks whether the event falls inside the boundary of each team’s zone. A team whose zone boundary does not contain the event ranks lower than a comparable team whose boundary does. The team is not excluded: if it is still the best option available, it can be recommended and dispatched. Teams whose zone has no boundary are ranked as before.

​
Positions and the centre point

The zone centre also acts as a fallback position. When none of a team’s members has reported a position, the score engine uses the centre of the team’s zone to estimate how close the team is to an event.