Skip to content
Ingo Simonis edited this page Jul 27, 2015 · 3 revisions

#SensorML SensorML is used to define sensor instances with all properties important for the observation purpose.

Aggregated Sensors

One issue that often arises when describing sensor systems, i.e. constellations of sensors that communicate their measurements through the same output interface, is the fact that all the individual sensors need to be described with their capabilties, inputs and outputs in unambiguous way. The easiest way to achieve this is to split the sensors description file into one file per sensor and to integrate all components into a master file. The description of the ELV KS300 is such an example.

ELV KS300

The sensor provides the following examplarily output string:

1;1;;;;;;13,0;;;;;;;;58;;;;18,9;39;0,0;2680;0;0 The record consists of 25 fields, separated by semicolons, due to the fact that the KS300 sensor can be expanded with with up to 8 additional temperature and humidity sensors. The first two fields are fixed to "1", indicating that everything works fine. The next 16 fields provide temperature (first eight) and humidity (second eight) measurements of the additional sensors, followed by temperature, relative humidity, windspeed, rain (teeter board changes), and rain sensor (0/1). Each records ends with "0". The nature of this datarecord together with the encoding is provided as part of the sml:outputs description.

Clone this wiki locally