Skip to content

Commit 596a9c6

Browse files
authored
Merge pull request #95351 from uhabiba04/master
included additional content and minor format updates
2 parents a363fce + 68a74ec commit 596a9c6

9 files changed

+189
-212
lines changed

articles/industry/agriculture/generate-maps.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ Soil moisture is the water that is held in the spaces between soil particl
165165
Ensure the following before you attempt to generate a Soil Moisture Heatmap:
166166

167167
- At least three soil moisture sensors must be deployed. Microsoft recommends that you do not try to create a Soil Moisture map before sensors are deployed and associated with the farm.
168-
- At least one cloud free Sentinel Scene must be available for the last 120 days, from the day for which the Soil Moisture map was requested.
168+
- Generate Soil Moisture Heatmap is influenced by Sentinel's path coverage, cloud cover and cloud shadow. At least one cloud free Sentinel Scene must be available for the last 120 days, from the day for which the Soil Moisture map was requested.
169169
- At least half of the sensors deployed on the farm must be online and have data streaming to the Data hub.
170170
- The Heatmap should be generated using sensor measures from the same provider.
171171

@@ -215,6 +215,6 @@ Use the following steps:
215215
4. Select the **Sort** icon next to the table headers to sort according to Farm, Date, Created On, Job ID, and Job Type.
216216
5. Scroll through the list of maps available using the navigation buttons at the end of the page.
217217
6. Select the map you want to view. A pop-up window displays the preview for the selected map.
218-
7. Select **Download** drop-down menu to select the download format and the map is downloaded and stored in the local folder of your computer.
218+
7. Select **Download** drop-down menu to select the download format and the map is downloaded and stored in the specified folder.
219219

220220
![Project Farm Beats](./media/get-sensor-data-from-sensor-partner/download-soil-moisture-map-1.png)

articles/industry/agriculture/get-drone-imagery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Use the following steps:
5050

5151
```azurepowershell-interactive 
5252
53-
PS> ./generateCredentials.ps1
53+
./generateCredentials.ps1
5454
5555
```
5656

articles/industry/agriculture/get-sensor-data-from-sensor-partner.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ Alternatively, you can generate the credentials by running this script from the
5656

5757
```azurepowershell-interactive 
5858
59-
PS> ./generateCredentials.ps1
59+
./generateCredentials.ps1
6060
6161
```
6262
7. Follow the onscreen instructions to capture the values. (API Endpoint, Tenant ID, Client ID, Client Secret and EventHub Connection String).

articles/industry/agriculture/imagery-partner-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ Optionally, you can include query parameters on GET calls to filter, limit the s
9393

9494
The below sample request is to get the list of devices:
9595

96-
```
96+
```azurepowershell-interactive
9797
curl -X GET "https://microsoft-farmbeats.azurewebsites.net/Device" -H
9898
"Content-Type: application/json" -H
9999
"Authorization: Bearer <Access-Token>”
@@ -104,7 +104,7 @@ Most GET, POST, and PUT calls require a JSON request body.
104104
The below sample request is to create a device (This has an input JSON with the request body).
105105

106106

107-
```json
107+
```azurepowershell-interactive
108108
curl -X POST "https://microsoft-farmbeats.azurewebsites.net/Device" -H
109109
"accept: application/json" -H
110110
"Content-Type: application/json" -H "Authorization: Bearer <Access-Token>" -d

articles/industry/agriculture/ingest-historical-telemetry-data.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,14 @@ Follow the below steps to generate these:
4545

4646
![Project Farm Beats](./media/for-tutorials/power-shell-two-1.png)
4747

48-
5. Go to the directory where the files were uploaded (By default it gets uploaded to the home directory /home/username/.
48+
5. Go to the directory where the files were uploaded
49+
50+
>[!NOTE]
51+
> By default, file gets uploaded to the home directory /home/username/.
4952
6. Run the script by using the command:
5053

5154
```azurepowershell-interactive
52-
PS> ./generateCredentials.ps1
55+
./generateCredentials.ps1
5356
```
5457
5558
7. Follow the onscreen instructions to complete the procedure.
@@ -122,7 +125,9 @@ FarmBeats Data hub uses bearer authentication, which needs the following credent
122125
123126
Using the above credentials, the caller can request for an access token, which needs to be sent in the subsequent API requests in the header section as follows:
124127
128+
```
125129
headers = *{"Authorization": "Bearer " + access_token, …}*
130+
```
126131
127132
**HTTP Request Headers**:
128133
@@ -156,8 +161,10 @@ Here are the most common request headers that need to be specified when making a
156161
"additionalProp3": {}
157162
}
158163
}
164+
```
159165

160166
Device
167+
161168
```json
162169
{
163170
"deviceModelId": "string",
@@ -237,7 +244,7 @@ Sensor
237244
```
238245
The below sample request is to create a device (This has an input json as payload with the request body).
239246

240-
```
247+
```azurepowershell-interactive
241248
curl -X POST "https://<datahub>.azurewebsites.net/Device" -H
242249
"accept: application/json" -H "Content-Type: application/json" -H
243250
"Authorization: Bearer <Access-Token>" -d "
@@ -263,6 +270,7 @@ Once you have a connection established as an EventHub client, you can send messa
263270
Convert the historical sensor data format to a canonical format that Azure FarmBeats understands. The canonical message format is as below:
264271

265272

273+
266274
```
267275
{
268276
“deviceid”: “<id of the Device created>”,
35 KB
Loading

0 commit comments

Comments
 (0)