Geofencing: Difference between revisions
(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...") |
No edit summary |
||
| Line 17: | Line 17: | ||
* Shape/object details | * Shape/object details | ||
* Static information contained in the template, for instance textual warnings and importance of the event | * 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. | 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. | ||
{{Note|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.}} | {{Note|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.}} | ||
This example was generated using recorded AIS data and sample symbology. Notifications are displayed using the geofencing service diagnostic application. | This example was generated using recorded AIS data and sample symbology. Notifications are displayed using the geofencing service diagnostic application. | ||
[[File:map.png|none|frame|Track entering ]] [[File:notifications.png|none|frame|Notification details]] | [[File:map.png|none|frame|Track entering Langesund area]] [[File:notifications.png|none|frame|Notification details]] | ||
[[Category:Geofencing]] | [[Category:Geofencing]] | ||
Revision as of 14:14, 2 August 2019
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
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.
This example was generated using recorded AIS data and sample symbology. Notifications are displayed using the geofencing service diagnostic application.
