Skip to content

Relative Zone

A relative_zone object defines a virtual geometric zone within the coordinate space of a relative tracking system. Its shape is determined by a polygon whose vertices are expressed in local (X, Y) coordinates of the same reference system used by relative_tracker objects.

Unlike other objects, a relative zone is static and passive: it has no states or actions of its own. Its purpose is to serve as a region of interest that automations and analytics engines can query to determine whether a relative_tracker is inside or outside it.

Main characteristics

  • Polygonal geometry: The zone is defined by an ordered list of vertices (X, Y) that form a closed polygon.
  • Relative coordinates: Uses the same local coordinate system as relative_tracker objects, without depending on GPS or global coordinates.
  • No states or actions: The zone does not change on its own; other parts of the system reference it to make decisions.
  • Integration with tracking: Enables defining presence regions, restricted zones, or analysis areas within a bounded space (industrial plant, warehouse, sports field).

Common use cases

  • Delimiting a safety zone in an industrial plant and alerting if an autonomous vehicle leaves it.
  • Defining work areas in a warehouse to analyze worker distribution.
  • Creating regions of interest in sports fields for tactical player analysis.
  • Establishing virtual perimeters in indoor environments where GPS is unavailable.

State properties

Property Description
shape Zone polygon in JSON format. Contains a vertex array, each with x and y fields.
state Always active on initialization. Indicates the zone is registered and available in the platform.

shape example

{
  "vertices": [
    { "x": 0.0, "y": 0.0 },
    { "x": 5.0, "y": 0.0 },
    { "x": 5.0, "y": 4.0 },
    { "x": 0.0, "y": 4.0 }
  ]
}

Note: Vertices must be defined in order (clockwise or counter-clockwise) for the polygon to be valid. Units are meters in the relative space coordinate system.