Create and monitor Geofences - iOS

Use region monitoring to determine when the user enters or leaves a geographic region.
  1. Create and monitor geofences

Create and monitor geofences

Use region monitoring to determine when the user enters or leaves a geographic region.

Region monitoring (also known as geofencing) combines awareness of the user’s current location with awareness of the user’s proximity to locations that may be of interest. This region is a way for your app to be alerted when the user enters or exits a geographical region. To mark a location of interest, you specify its latitude and longitude. To adjust the proximity for the location, you add a radius. The latitude, longitude, and radius define a geofence, creating a circular area, or fence, around the location of interest.

In iOS, regions are monitored by the system, which wakes up your app as needed when the user crosses a defined region boundary.

Region monitoring is a natural complement to Search requests performed on collected locations. Indeed, Search requests help monitoring the approach to some assets you want to monitor. On every collected location you are aware of the surronding assets (distance to them and even time if using Distance API request). You can then decide to monitor some of those surrounding assets (e.g. the closest ones). Region monitoring is designed to do so.

POI Region

Set up for geofence monitoring

The first step in requesting geofence monitoring is to set regionDelegate, this should be done as early as possible in your didFinishLaunchingWithOptions App Delegate.

let dataLocation = DataLocation()
let dataPOI = DataPOI()
let dataDistance = DataDistance()
let dataRegion = DataRegion()
let dataVisit = DataVisit()

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
	// Set Woosmap API Private key
        WoosmapGeofencing.shared.setWoosmapAPIKey(key: WoosmapKey)
        WoosmapGeofencing.shared.setGMPAPIKey(key: GoogleStaticMapKey)
        // Set the Woosmap Search API url
        WoosmapGeofencing.shared.setSearchWoosmapAPI(api: searchWoosmapAPI)
        // Set the Woosmap Distance API url
        WoosmapGeofencing.shared.setDistanceWoosmapAPI(api: distanceWoosmapAPI)
        WoosmapGeofencing.shared.setDistanceAPIMode(mode: drivingModeDistance)
        // Set classification of zoi enable 
        WoosmapGeofencing.shared.setClassification(enable: true)
        // Set delegate of protocol Location, POI and Distance
        WoosmapGeofencing.shared.getLocationService().locationServiceDelegate = dataLocation
        WoosmapGeofencing.shared.getLocationService().searchAPIDataDelegate = dataPOI
        WoosmapGeofencing.shared.getLocationService().distanceAPIDataDelegate = dataDistance
        WoosmapGeofencing.shared.getLocationService().regionDelegate = dataRegion

Retrieve Region events

In your class delegate, retrieve Region data :

public class DataRegion:RegionsServiceDelegate  {
    public init() {}
    public func updateRegions(regions: Set<CLRegion>) { .updateRegions, object: self,userInfo: ["Regions": regions])
    public func didEnterPOIRegion(POIregion: Region) { .didEventPOIRegion, object: self,userInfo: ["Region": POIregion])
    public func didExitPOIRegion(POIregion: Region) { .didEventPOIRegion, object: self,userInfo: ["Region": POIregion])
    public func workZOIEnter(classifiedRegion: Region) { .didEventPOIRegion, object: self, userInfo: ["Region": classifiedRegion])
    public func homeZOIEnter(classifiedRegion: Region) { .didEventPOIRegion, object: self, userInfo: ["Region": classifiedRegion])
    public func readRegions()-> [Region] {
        return Regions.getAll()
    public func eraseRegions() {

Whenever the user crosses the boundary of one of your app’s registered regions, the system notifies your app.

Boundary crossing notifications are delivered to your region delegate object. Specifically, (_:didEnterRegion:) or (_:didExitRegion:) methods.

On the object Region, there are an boolean didEnter that indicate if you enter or exit of the region. You have another boolean fromPositionDetection to know if the detection was launch by the position detection or by the system detection.

When determining whether a boundary crossing happened, the system waits to be sure before sending the notification. Specifically, the user must travel a minimum distance over the boundary and remain on the same side of the boundary for at least 20 seconds. These conditions help eliminate spurious calls to your delegate object’s methods.

Exit region event

By experience, the region exit event from iOS seems not to be as accurate as the region entry event (exit event can tiggered from a position not in the immediate proximity of the region boundary). It is therefore advisable to rely on the input event to trigger actions is accuracy matters for you.

Regions have an associated identifier, which this method uses to look up information related to the region and perform the associated action.

Regions creation is enabled on the nearest result of the Search API request . The closest POI is so used to create 3 regions around it (100 m, 200m, and 300 m). If the automatic region monitoring is not necessary for your use cases, settings of the SDK can be modified as follow:

WoosmapGeofencing.shared.setSearchAPICreationRegionEnable(enable: false)

You can change the radius of POI regions by settings the SDK as follow :

WoosmapGeofencing.shared.setFirstSearchAPIRegionRadius(radius: 150.0)
WoosmapGeofencing.shared.setSecondSearchAPIRegionRadius(radius: 350.0)
WoosmapGeofencing.shared.setThirdSearchAPIRegionRadius(radius: 550.0)

Monitoring ZOI Classified

When a ZOI is classified HOME or WORK, you can get events enter or exit status in the Region table of the database. To launch a Region event from a ZOI classified, you must define a distance detection threshold (meters) in the settings of the SDK like this :

WoosmapGeofencing.shared.setRadiusDetectionClassifiedZOI = 50;

Create a custom region

A region is a circular area centered on a geographic coordinate. You can define one using a CLLocationCoordinate2D object. The radius of the region object defines its boundary. You define the regions you want to monitor and register them with the system by calling the addRegion(center: CLLocationCoordinate2D, radius: CLLocationDistance) method of WoosmapGeofencing.shared.locationService. The system monitors your regions until you explicitly ask it to stop or until the device reboots.

let (regionIsCreated, identifier) = WoosmapGeofencing.shared.locationService.addRegion(identifier: region_identifer, center: coordinate, radius: 100)

This method returns the state of creation (true or false) and the identifier of the region created by the SDK. If this method returns false, the limit of numbers of regions monitored has been exceed. Indeed, regions are shared resources that rely on specific hardware capabilities. To ensure that all apps can participate in region monitoring, Core Location prevents any single app from monitoring more than 20 regions simultaneously. The SDK creates 13 regions to monitor the user location, so you have only 7 slot regions available.

To work around this limitation, monitor only regions that are close to the user’s current location. As the user moves, update the list based on the user’s new location.

If you add a region with the same identifier than old region, the old region will be removed from the monitoring and replace by the new one.

Remove regions

To remove all regions created, you can use this method :

WoosmapGeofencing.shared.locationService.removeRegions(type: LocationService.regionType.NONE)

To remove only POI regions created by the result of the search API, you can use this method :

WoosmapGeofencing.shared.locationService.removeRegions(type: LocationService.regionType.POI_REGION)

To remove only custom regions created, you can use this method :

WoosmapGeofencing.shared.locationService.removeRegions(type: LocationService.regionType.CUSTOM_REGION)