Fleet Telematics Geofencing Developer's Guide


This document introduces the Fleet Telematics Geofencing .

For the terms and conditions covering this documentation, see the HERE Documentation License.

What Is the Fleet Telematics Geofencing?

The HERE Fleet Telematics Geofencing is a REST API that allows you to track whether or not mobile assets are located within the specified geographic areas. An asset is any kind of trackable object, such as a person, car, smartphone, or delivery package.

You can define the geographic areas as geometries in the form of geographic polygons, polylines, or points that are relevant for these assets.

You can also choose to check the assets' position against Map layers, for example country boundaries, postal code boundaries or census boundary layers.

Why Use the Fleet Telematics Geofencing?

The table below lists the high level use cases for the Fleet Telematics Geofencing.

Table 1. Main features of the HERE Fleet Telematics Geofencing
Feature Description
Close access to certain areas in cities Based on various requirements, you can specify areas in a city as no-go areas for assets at certain times of the day or week. For example, if the assets should avoid areas with heavy traffic during peak hours. For each asset group, there is a static set of polygons defined where the assets and/or management system is alerted if an asset approaches or enters the no-go area. These polygons can have individually defined validity periods.
Alert the warehouse 15 minutes before a mobile asset arrives To prepare for a delivery, warehouses want to be notified when a mobile asset, such as a truck, is less than 15 minutes away. The isochrone polygons around each warehouse can be:
  • static – computed using reverse isoline routing via the HERE Routing API
  • dynamic – according to a weekly recurring traffic pattern or current live traffic situation
The validity period for each polygon can be the warehouse's opening hours.
Alert the end user 15 minutes before a package arrives To prepare for a postal or drone delivery, end users want to be notified when a mobile asset, such as a delivery truck, person, or a drone, is less than 15 minutes away. End users are entered on the fly as isochrone polygons, as soon as the delivery process starts. Each mobile asset is then checked against one user polygon.
Notify taxi service if there are less than five (5) cars within a hot spot polygon In the vicinity of a train station or a stadium, after a big event, there should be sufficient cars within 3 minutes reach to be ordered by users. In this case, many static and a few dynamic polygons are defined. The alerts are not for individual assets but for the total number of assets within a polygon. Currently, fleet management systems must maintain the number of polygon themselves and trigger alerts in case of an underflow.
Alert a consumer when he or she is close to a shop For advertising purposes, while the mobile asset such as a car driver or a pedestrian, is moving, an advertisement alerts the consumer if a particular shop or restaurant is close by. The validity period for each static polygon or point can be the respective opening hours.
Notify the car rental agency if an asset enters a forbidden country or area Certain groups of rental cars have a restricted set of countries or areas where their use is permitted, due to insurance or security reasons. In this case, you can define a few static polygons that extend across a large geographic area with a fine grained resolution (number of vertices) per asset group. Or you can simply use the existing PDE country boundary layer as geofences.