Skip to content

Commit 187639d

Browse files
authored
Merge pull request #107233 from sunasing/master
Added Documentation to query ingested sensor telemetry data
2 parents e1216f0 + 49a3cea commit 187639d

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/industry/agriculture/query-telemetry-data-from-azure-farmbeats.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,22 +11,22 @@ ms.author: sunasing
1111

1212
This article describes how to query ingested sensor data from Azure FarmBeats.
1313

14-
Ingesting data from Internet of Things (IoT) resources such as devices and sensors is a common scenario in FarmBeats. You create metadata for devices and sensors and then ingest the historical data to FarmBeats in a canonical format. Once the sensor data is available on FarmBeats Datahub, we can query the same to generate actionable insights or build models.
14+
Ingesting data from Internet of Things (IoT) resources such as devices and sensors is a common scenario in FarmBeats. You create metadata for devices and sensors and then ingest the historical data to FarmBeats in a canonical format. Once the sensor data is available on FarmBeats Data hub, we can query the same to generate actionable insights or build models.
1515

1616
## Before you begin
1717

18-
Before you proceed with this article, make sure that you've installed FarmBeats and ingested sensor telemetry data from your IoT devices to FarmBeats
18+
Before you proceed with this article, make sure that you've installed FarmBeats and ingested sensor telemetry data from your IoT devices to FarmBeats.
1919
To ingest sensor telemetry data, visit [ingest historical telemetry data](ingest-historical-telemetry-data-in-azure-farmbeats.md)
2020

21-
Before you proceed, also make sure you are familiar with FarmBeats REST APIs as you will query ingested telemetry using APIs. For more details on FarmBeats APIs, please see [FarmBeats REST APIs](rest-api-in-azure-farmbeats.md). **Ensure that you are able to make API requests to your FarmBeats Datahub endpoint**
21+
Before you proceed, also make sure you are familiar with FarmBeats REST APIs as you will query ingested telemetry using APIs. For more details on FarmBeats APIs, please see [FarmBeats REST APIs](rest-api-in-azure-farmbeats.md). **Ensure that you are able to make API requests to your FarmBeats Data hub endpoint**
2222

2323
## Query ingested sensor telemetry data
2424

2525
Follow the below steps to query the ingested sensor telemetry data:
2626

2727
1. Identify the sensor you are interested in. You can do this by making a GET request on /Sensor API. Note the **id** and the **sensorModelId** of the interested sensor object.
2828

29-
2. Make a GET/{id} on /SensorModel API for the **sensorModelId** as noted in step 1. The SensorModel has all the metadata and details about the ingested telemetry from the sensor. For example, SensorMeasure within the SensorModel object has details about what measures is the sensor sending and in what types and units. For example,
29+
2. Make a GET/{id} on /SensorModel API for the **sensorModelId** as noted in step 1. The "Sensor Model" has all the metadata and details about the ingested telemetry from the sensor. For example, "Sensor Measure" within the "Sensor Model" object has details about what measures is the sensor sending and in what types and units. For example,
3030

3131
```json
3232
{
@@ -38,7 +38,7 @@ Follow the below steps to query the ingested sensor telemetry data:
3838
"description": "<Description of the measure>"
3939
}
4040
```
41-
Make a note of the response from the GET/{id} call for the SensorModel.
41+
Make a note of the response from the GET/{id} call for the Sensor Model.
4242

4343
3. Do a POST call on /Telemetry API with the following input payload
4444

@@ -89,8 +89,8 @@ Make a note of the response from the GET/{id} call for the SensorModel.
8989
]
9090
}
9191
```
92-
In the above example response, the queried sensor telemetry gives data for two timestamps along with the measure name ("moist_soil_last") and values of the reported telemetry in the two timestamps. You will need to refer to the associated /SensorModel (as described in step 2) to interpret the type and unit of the reported values.
92+
In the above example response, the queried sensor telemetry gives data for two timestamps along with the measure name ("moist_soil_last") and values of the reported telemetry in the two timestamps. You will need to refer to the associated Sensor Model (as described in step 2) to interpret the type and unit of the reported values.
9393

9494
## Next steps
9595

96-
You now have queried sensor data from your Azure FarmBeats instance. Now, learn how to [generate maps](generate-maps-in-azure-farmbeats.md#generate-maps) for your farms.
96+
You now have queried sensor data from your Azure FarmBeats instance. Now, learn how to [generate maps](generate-maps-in-azure-farmbeats.md#generate-maps) for your farms.

0 commit comments

Comments
 (0)