Geofencing integration

Geofencing integration

NAOGeofencingHandleDelegate

This class provides the callbacks for receiving alerts configured on NAO Cloud in the Geonotifications section.

The recommended implementation is as follows:

  1. Make the class where you want to receive the callbacks implement NAOGeofencingHandleDelegate.
  2. Implement the didFireNaoAlert callback with the desired associated behavior. API reference: NAOGeofencingHandleDelegate

Code snippet:

@interface GeofencingViewController : UIViewController <NAOGeofencingHandleDelegate, NAOSyncDelegate, NAOSensorsDelegate>
- (void) didFireNAOAlert:(NaoAlert *)alert {
    // Desired behavior for the received alert.
}

NAOGeofenceHandleDelegate

This class provides the same callback as the NAOGeofencingHandleDelegate, plus 2 additional callbacks to receive alerts for all geofencing events associated to every geofence defined on NAO Cloud in the Geofences section, without the need to define any geonotification.

The recommended implementation is as follows:

  1. Make the class where you want to receive the callbacks implement NAOGeofenceHandleDelegate.
  2. Implement the onFireNaoAlert callback with the desired associated behavior. API reference: NAOGeofenceHandleDelegate

Code snippet:

@interface GeofencingViewController : UIViewController <NAOGeofenceHandleDelegate, NAOSyncDelegate, NAOSensorsDelegate>
- (void) didFireNAOAlert:(NaoAlert *)alert {
    // Desired behavior for the received alert.
}

- (void)didEnterGeofence:(int)regionId andName:(NSString *)regionName {
    // Desired behavior when entering the geofence with ID regionId.
}

- (void)didExitGeofence:(int)regionId andName:(NSString *)regionName {
    // Desired behavior when exiting the geofence with ID regionId.
}
    • Related Articles

    • Integration workflow

      This page gives useful information for the project management aspect of the integration of the SDK. Planning and effort estimation for the integration of the SDK: Coding effort: 1 staff day per OS, integration support : 1 staff day Testing effort: 1 ...
    • Integration workflow and recommendations

      This page gives useful information for the project management aspect of the integration of the MQTT API. Planning and effort estimation for the integration: Coding effort: from 1 to 2 staff days, integration support : 1 staff day; Testing effort: 1 ...
    • Self-hosted integration

      This page describes how to configure NAO Logger and NAO SDK when using the NAO Server default installation parameters. In the .env file in the self-hosted install folders you used to deploy NAO Server, the server IP and port information are defined ...
    • Emulate User Position

      If you want to test your integration of the NAO SDK without the need to be on site, we provide an emulated mode. That emulated mode is only available for the Location Service and Geofencing Service. Warning: The emulator mode bypasses the sensors, so ...
    • Overview

      Features Indoor positioning, using WiFI/BLE/GPS/MEMS sensors Beacon proximity detection, using BLE sensor Geofencing notification, using Indoor Positioning and Beacon proximity detection Geofencing-based analytics, using Geofencing notification ...