Geofencing

From Maria GDK Wiki
Revision as of 14:12, 2 August 2019 by Mbu (talk | contribs) (Created page with "Geofencing allows the user to define geographical shapes that acts as virtual "fences". By defining interaction rules, it is possible to generate events based on how tracks in...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Geofencing allows the user to define geographical shapes that acts as virtual "fences". By defining interaction rules, it is possible to generate events based on how tracks interact with these shapes.

General

Geofencingserviceoverview.png

A geofence consists of the following components:

  • A geographical shape. Various object types are supported, for instance lines, polygon areas, sectors and range circles
  • Interaction type, one of entering, leaving or crossing
  • Track filter
  • Report template

When a track interacts with a geofence in accordance with a rule, a report is generated. A report template determines the contents of the report. Typically, the report includes:

  • Time of interaction
  • Track details
  • Shape/object details
  • Static information contained in the template, for instance textual warnings and importance of the event


The core geofencing component is the geofencing service. It is responsible for fetching tracks and fence objects from respective services, for handling rule setup and execution as well as for providing clients with events.

Rules by default apply to all tracks and shapes/objects in the service. Take care to define filters that only include the desired combination of tracks and shapes.

Example

This example was generated using recorded AIS data and sample symbology. Notifications are displayed using the geofencing service diagnostic application.

Track entering
Notification details