Impact of geofence proximity and search radius on asset distance

For each polygon geofence that covers the asset position or is close to it, the HERE Geofencing API returns the geofence geometry together with the asset's distance to this geometry.

The asset distance can be influenced by the following factors:

• The asset is outside of the geofence. The distance is measured in a straight line to the closest border of the geofence. This is always the case for line and point geofences.
• The asset is inside the geofence. The distance is measured in a straight line to the closest border of the polygon. The value is a negative number.
• The asset is outside of the search radius. The geofence isn't listed in the response.
• The asset is inside the polygon but further away from the border of the search radius. A special value indicating "far inside" is returned.

In your app, you can use the asset distance to generate events with different severity levels based on specific distance thresholds. You can suppress superfluous events if the asset moves along the boarder of the geofence, and enters or leaves it frequently without a significant change in the asset distance.

For performance reasons, the asset distances are only straight line distances, not equivalent to driving distances or driving times. Asset distances are limited to approximately 20 kilometers, so a distance can be one of the following:

• Within the polygon 250m from the closest border
• Within the polygon more than 20km from the closest border
• Outside the geofence 333m from the closest border
• Outside the geofence more than 20km from the closest border (this value applies to all non-listed geofences, when the asset is outside of the search radius)

Events such as entering, leaving, flickering along the border of the geofence, or re-entering the geofence don't receive an explicit response, only the asset distances. The same applies to a sequence of events, such as the asset entering the geofence for the third time or leaving for the second time on the same day.

📘

Note

HERE Geofencing API v8 doesn't require or support asset identification or registration.