I've encountered this problem with the latest Android Geofence API. The usage is exact to the example usage. I set Geofence.GEOFENCE_TRANSITION_ENTER
type geofence with 500m radius and expiration is Geofence.NEVER_EXPIRE
. This works ok, but if I'm about 10 meters to latitude longitude and I set the geofence, it triggers immediately.
So am I understanding the term Geofence.GEOFENCE_TRANSITION_ENTER
wrong here, shouldn't it trigger only when we are outside the zone and enter it, not when we are already in the zone?
Thanks.
Under the right circumstances, device tracking can pinpoint a location within a few feet. Device-based geolocations play a big role in geofencing and geotargeting. A geofence is an invisible, virtual fence that triggers a response each time a geolocation-compatible device enters or exits a geofence.
For best results, the minimum radius of the geofence should be set between 100 - 150 meters.
The API uses a pay-as-you-go pricing model. After you consume all the initial free requests, the charges are 5.00 USD per 1000 hits.
App developers can use native Android and iOS location detection to power their location-based experiences and engagement. However, native geofencing technology can only deliver accuracy of around 100-200 meters.
Well, think of Geofences of 3D objects: 2 dimensions in space, one dimension in time. Between the checks, if a Geofence was hit, your new fence got moved into place.
However, I just save the timestamp on adding fences and ignore all hits within seconds after that.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With