## 6 Analysis and Results
### SensorData Connector: Payload Analysis and Results
```
{ name:\"SensorData\", description:\"SensorDataLRWANisabattery orlinepowereddatacommunicatorthatinterfaces toarangeofsensors,GPS,inputsandoutputs,anduploadsataviaL&WANnetworks\" encodingtype:\"application/pdf\" metadata:\"HTHS/digmatic.freshdesk.com/helpdesk/attachments/1607369925\" ] ]
```
**Listing 8**SensorData. Finally, the measurement is published, linking it to the corresponding FEATURE OF INTEREST entity. In fact, similar to the previous entities, there is a table within the connector containing information related to the FEATURE OF INTEREST entities, as shown in Listing 8. ```
{  name: \"Battery\",  description: \"Device battery\",  encodingType:\"application/vnd.geo+json\",  feature:\" }
```
**Listing 8**. FEATURE OF INTEREST entity. Note how the internal database links the FEATURE OF INTEREST with the DATAS-TREAM and the unique ID that identifies the device. While the previous entities (OBSERVED PROPERTY and SENSOR) are common to all devices of the same model, the FEATURE OF INTEREST is specific to each individual device, as measurements can be taken in spaces with different dimensions and/or locations. If there is no FEATURE OF INTEREST to link to the observation, the central server will derive one from the LOCATION entity with which it is connected. The steps related to the creation of the OBSERVED PROPERTY, SENSOR, and FEATURE OF INTEREST entities discussed so far will be omitted from the upcoming payload analyses to make the explanation clearer. ```
80126061: The first byte has a decimal value of 128, which corresponds to the SDI-12 Measurement 1 \"data field\". The first value of the second byte (1) indicates the data type used to express the values, in this case, \"Temperature UINTS\", while the second value (2) represents the number of observations, in this case, 2. The last 2 bytes correspond to the measurement values _measurement_1 = 8 and _measurement_2 = 8.5, which represent two measurements of soil temperature. The connector does not have enough information about the nature of \"SDI-12 Measurement\" type measurements to create a new DATASREAM for them (Listing 9). Therefore, it can only search among the associated DATASTEAMS to check if one has been previously loaded. Once the DATASREAM is obtained, as shown in Listing 10. ```
{  name: \"Soil temperature\",  description: \"Temperature 20 cm under the soil\",  unitOfMeasurement: {  name: \"Degrees Celsius\",  symbol:\"C\",  definition: \" },  observationType:\"OM_Measurement\", }
```
**Listing 10**. Soil temperature OBSERVATION. ```
{  result: 8 }  result: 8.5 }
```
**Listing 11**. Soil temperature DATASREAM. ```
{  result: 8 } {  result: 8.5 }
```  
**Listing 12**. Soil temperature DATASREAM. **Listing 13**. Soil temperature DATASREAM. **Listing 14**. Soil temperature DATASREAM. **Listing 15**. Soil temperature DATAS  
```
1 name:\"Nitrogenconcentration\", description:\"Nitrogenconcentrationinthesoil,moponKg\", unitOMMeasuremen\": name:\"milligramstokilogram\", symbol:\"mg/Kg\", definition:\", ]observationType:\"OM_Measurement\", resultTime:\"2024-11-03T13:00:00Z/2024-11-03T13:00:00Z\" ]
```  
Listing 12: Nitrogen concentration OBSERVATION.