The following considerations should be made when defining a Watch Zone.

Overshoot Limitation for Open Zones

Since an overshoot is triggered by border-crossing algorithms, if a tracked point travels around an open zone without explicitly crossing the border, it is not detected as an overshoot.

Overlaps with Custom Shapes

When importing a CSV file to create a custom shape for the Watch Zone, there is no check to ensure the series of points are correctly ordered. This leads to a continuous shape where the border may overlap itself. In this instance, it is more effective to split the zone into simpler shapes where borders touch instead of overlap.

The example below shows an open zone with a continuous shape that overlaps at one point. However, it is best to separate this into three Watch Zones, where 1 is a closed zone, and 2 and 3 are either Linear Shapes or custom curved shapes that do not overlap with zone 1.

Similarly, the zone below could be split into two custom-shaped closed zones that do not overlap.