Steerpath's geofence zones, also known as trigger areas, will trigger a notifications to occur to the application when a user enters or exits a given area.
A common usage is to make a room a trigger zone, in which case the application is notified when the user enters the room or exits it. Another example is to make a trigger zone around a piece of interest, for example around a sculpture in a museum.
With Nimble Sense, the zones can be drawn on the map using the mapping tool. The information is then bundled into the data file together with other information of the map. This means that the application does not need to set up areas using lists of coordinates, and the area information can be updated together with all the other map data, independently from the library. From the application development point of view using trigger areas requires practically no set-up.
Each zone has a unique numeric id, which the application can use. Additionally the mapping tool allows to associate any text to a zone which doesn't need to be unique. For example each meeting room on a map could have the textual id of "meeting room", simplifying application programming logic as the same logic can be triggered regardless of which meeting room was entered.
The textual id also allows consistent operating logic through unified naming across different venues. For a retail chain application, each store can have the same section names like "sports wear" or "electronics". The application can then have same logic in all stores when user enters "electronics" zone.
Multiple zones can overlap, meaning for example that a whole floor of a building can be one zone, and each room on the floor can also be a zone. Triggering happens both when the floor is entered as well as when the room is entered. Partially overlapping zone edges can also be used to implement hysteresis between moving between areas when such functionality is needed.
- Trigger zone are sometimes called geofences or trigger areas
- The application is notified when a zone is entered or exited
- Zones are drawn up with the floor plan
- Zones are located within the map data file
- Zones are polygons meaning any shape is possible
- Zones have a numeric ID
- Zones can have any given (non-unique) textual ID
- Zones can be nested