Sensor Data Collection
Using location services to collect sensor data
There are two modes that location services can function in
- Local only All sensor data is coming from platforms with drivers in the current system
- Building search Sensors can exist in any system, as well as locally, and the building is searched for modules implementing the sensor interface
Add the sensor platform sources and their location service modules to the location services system.
Some examples include
To enable building search, add the following setting to the buildings location services system
The location services driver auto-detects the building it is providing locations for.
Ensure all the sensor data is up-to-date in AreaManagement.
If the sensors have just been configured, perform the following actions in backoffice to ensure sensor meta data is saved (this occurs automatically periodically)
- 1.select the location services system
- 2.select the modules tab
- 3.execute the following commands
- 1.AreaManagement_1 -> synchronize_all_levels
- 2.AreaManagement_1 -> write_sensor_discovery
This saves building level metadata:
Level zones have a
Sensorstab that allows placement of sensor data on a map
- Data coming from local only configuration is listed when selecting any level
- Data coming from building search will only show on matching levels
Sensor placement UI
Remember to click save!
Sensor locations are stored in level metadata called
Level zones have a
Sensorstab that allows drawing of regions on the map.
- 1.Either select an existing region OR click
- 2.Click and drag the desired area on the map
- 3.Remember to click save!
Region metadata is stored in
map_regions- you can edit this for fine tuned adjustment or if you would like to define more complex polygon shapes.
Both Sensor Placement and Map Regions UIs are backoffice extensions. The following will enable the tabs if they are not available
Backoffice extension UI