edit pass: imagery-and-sensory-partner-integration

Author: paulth1

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

@@ -15,8 +15,8 @@ Data, once available, can be visualized through the FarmBeats Accelerator and po
 
 FarmBeats provides the ability to:
 
-- Define custom image types, source, and file format by using ExtendedType APIs.
-- Ingest imagery data from various sources via the Scene and SceneFile APIs.
+- Define custom image types, source, and file format by using /ExtendedType APIs.
+- Ingest imagery data from various sources via the /Scene and /SceneFile APIs.
 
 The following information focuses on getting any form of imagery into the FarmBeats system.
 
@@ -104,7 +104,7 @@ curl -X GET "https://microsoft-farmbeats.azurewebsites.net/Device" -H
 
 Most GET, POST, and PUT calls require a JSON request body.
 
-The following sample request is to create a device. (This sample has an input JSON with the request body.)
+The following sample request is to create a device. This sample has an input JSON with the request body.
 
 
 ```bash
@@ -121,7 +121,7 @@ JSON is a common language-independent data format that provides a simple text re
 
 ## Ingest imagery into FarmBeats
 
-After the partner has credentials to connect to FarmBeats Datahub, the partner does the following in the Translator component.
+After the partner has credentials to connect to FarmBeats Datahub, the partner takes the following steps in the Translator component.
 
 1.	Create a new extended type for the following fields, in accordance with the type of imagery to be uploaded:
 
@@ -130,21 +130,21 @@ After the partner has credentials to connect to FarmBeats Datahub, the partner d
     - **Scene File Type**: For example, chlorophyll index
     - **Scene File Content Type**: For example, image/tiff
 
-2.	Call the Farms API to get the list of farms from within the Azure FarmBeats system.
+2.	Call the /Farms API to get the list of farms from within the Azure FarmBeats system.
 3.	Provide the customer with an ability to choose a single farm from the list of farms.
 
     The partner system must show the farm within the partner software to do the path planning and drone flight and image collection.
 
-4.	Call the Scene API and provide required details to create a new scene with a unique scene ID.
-5.	Receive a blob SAS URL to upload the required images into the FarmBeats data hub, in the context of the chosen farm, in the FarmBeats system.
+4.	Call the /Scene API and provide required details to create a new scene with a unique scene ID.
+5.	Receive a blob SAS URL to upload the required images into FarmBeats Datahub, in the context of the chosen farm, in the FarmBeats system.
 
 Here's a detailed flow on the API calls.
 
 ### Step 1: ExtendedType
 
-Check in the ExtendedType API, if the type and file source are available on FarmBeats. To do so, call a GET on the /ExtendedType API.
+Check in the /ExtendedType API to see whether the type and file source are available on FarmBeats. To do so, call a GET on the /ExtendedType API.
 
-Following are the system-defined values:
+Here are the system-defined values:
 
 ```json
 {
@@ -328,7 +328,7 @@ Following are the system-defined values:
 
 This step is a one-time setup. The scope of this new scene type is limited to the subscription in which the FarmBeats project is deployed.
 
-For example, to add SceneSource: “SlantRange,” you do PUT on the ID of the /ExtendedType with the key "SceneSource" input payload.
+For example, to add SceneSource: “SlantRange,” you do a PUT on the ID of the /ExtendedType API with the key "SceneSource" input payload.
 
 ```json
 {
@@ -446,7 +446,7 @@ The scene ID returned in step 3 is the input for the scene file. The scene file
 
 If the user requires a programmatic way of uploading a stream of images, the blob storage SDK can be used to define a method by using the scene file ID, location, and URL.
 
-Example input payload for the POST call on the /Scenefile API:
+Example input payload for the POST call on the /SceneFile API:
 
 ```json
 {

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

@@ -11,7 +11,7 @@ ms.author: v-umha
 
 This article provides information about the Azure FarmBeats Translator component, which enables sensor partner integration.
 
-Using this component, partners can develop sensors that integrate with FarmBeats to use the API and send customer device data and telemetry to the FarmBeats data hub. Data is visualized by using the FarmBeats Accelerator. Data can be used for data fusion and for building machine learning/artificial intelligence models.
+Using this component, partners can develop sensors that integrate with FarmBeats to use the API and send customer device data and telemetry to FarmBeats Datahub. Data is visualized by using the FarmBeats Accelerator. Data can be used for data fusion and for building machine learning/artificial intelligence models.
 
 ## Link a FarmBeats account
 
@@ -143,7 +143,7 @@ FarmBeats Datahub has the following APIs that enable device partners to create a
 - /**SensorModel**: SensorModel corresponds to the metadata of the sensor, such as the manufacturer, the type of sensor, which is either analog or digital, and the sensor measure, such as ambient temperature and pressure.
 - /**Sensor**: Sensor corresponds to a physical sensor that records values. A sensor is typically connected to a device with a device ID.
 
-  **DeviceModel**| DeviceModel corresponds to the metadata of the device, such as the manufacturer and the type of device, which is either gateway or node.
+  **DeviceModel** |  |
   --- | ---
   Type (node, gateway)  | 1 Star |
   Manufacturer  | 2 Star |
@@ -152,35 +152,35 @@ FarmBeats Datahub has the following APIs that enable device partners to create a
   Name  | Name to identify resource. For example, model name or product name. |
   Description  | Provide a meaningful description of the model. |
   Properties  | Additional properties from the manufacturer. |
-  **Device** | **Device corresponds to a physical device present on the farm. Each device has a unique device ID.** |
+  **Device** |  |
   DeviceModelId  |ID of the associated device model. |
   HardwareId   |Unique ID for the device, such as a MAC address.  |
-  reportingInterval |Reporting interval in seconds. |
+  ReportingInterval |Reporting interval in seconds. |
   Location    |Device latitude (-90 to +90), longitude (-180 to 180), and elevation (in meters). |
   ParentDeviceId | ID of the parent device to which this device is connected. For example, if a node is connected to a gateway, the node has parentDeviceID as the gateway. |
   Name  | Name to identify the resource. Device partners need to send a name that's consistent with the device name on the device partner side. If the device name is user defined on the device partner side, the same user-defined name should be propagated to FarmBeats.  |
   Description  | Provide a meaningful description.  |
   Properties  |Additional properties from the manufacturer.  |
-  **SensorModel** | **SensorModel corresponds to the metadata of the sensor, such as the manufacturer, the type of sensor, which is either analog or digital, and the sensor measure, such as ambient temperature and pressure.** |
+  **SensorModel** |  |
   Type (analog, digital)  |Mention analog or digital sensor.|
   Manufacturer  | Name of manufacturer. |
   ProductCode  | Product code or model name or number. For example, RS-CO2-N01.  |
   SensorMeasures > Name  | Name of the sensor measure. Only lowercase is supported. For measurements from different depths, specify the depth. For example, soil_moisture_15cm. This name has to be consistent with the telemetry data. |
-  sensorMeasures > DataType  | Telemetry data type. Currently, double is supported. |
-  sensorMeasures > Type  | Measurement type of the sensor telemetry data. Following are the system-defined types: AmbientTemperature, CO2, Depth, ElectricalConductivity, LeafWetness, Length, LiquidLevel, Nitrate, O2, PH, Phosphate, PointInTime, Potassium, Pressure, RainGauge, RelativeHumidity, Salinity, SoilMoisture, SoilTemperature, SolarRadiation, State, TimeDuration, UVRadiation, UVIndex, Volume, WindDirection, WindRun, WindSpeed, Evapotranspiration, PAR. To add more, refer to the /ExtendedType API.
-  sensorMeasures > Unit | Unit of sensor telemetry data. Following are the system-defined units: NoUnit, Celsius, Fahrenheit, Kelvin, Rankine, Pascal, Mercury, PSI, MilliMeter, CentiMeter, Meter, Inch, Feet, Mile, KiloMeter, MilesPerHour, MilesPerSecond, KMPerHour, KMPerSecond, MetersPerHour, MetersPerSecond, Degree, WattsPerSquareMeter, KiloWattsPerSquareMeter, MilliWattsPerSquareCentiMeter, MilliJoulesPerSquareCentiMeter, VolumetricWaterContent, Percentage, PartsPerMillion, MicroMol, MicroMolesPerLiter, SiemensPerSquareMeterPerMole, MilliSiemensPerCentiMeter, Centibar, DeciSiemensPerMeter, KiloPascal, VolumetricIonContent, Liter, MilliLiter, Seconds, UnixTimestamp, MicroMolPerMeterSquaredPerSecond, and InchesPerHour. To add more, refer to the /ExtendedType API.
-  SensorMeasures > aggregationType  | Either none, average, maximum, minimum, or StandardDeviation.
-  SensorMeasures > depth  | The depth of the sensor in centimeters. For example, the measurement of moisture 10 cm under the ground.
-  sensorMeasures > description  | Provide a meaningful description of the measurement.
+  SensorMeasures > DataType  | Telemetry data type. Currently, double is supported. |
+  SensorMeasures > Type  | Measurement type of the sensor telemetry data. Following are the system-defined types: AmbientTemperature, CO2, Depth, ElectricalConductivity, LeafWetness, Length, LiquidLevel, Nitrate, O2, PH, Phosphate, PointInTime, Potassium, Pressure, RainGauge, RelativeHumidity, Salinity, SoilMoisture, SoilTemperature, SolarRadiation, State, TimeDuration, UVRadiation, UVIndex, Volume, WindDirection, WindRun, WindSpeed, Evapotranspiration, PAR. To add more, refer to the /ExtendedType API.
+  SensorMeasures > Unit | Unit of sensor telemetry data. Following are the system-defined units: NoUnit, Celsius, Fahrenheit, Kelvin, Rankine, Pascal, Mercury, PSI, MilliMeter, CentiMeter, Meter, Inch, Feet, Mile, KiloMeter, MilesPerHour, MilesPerSecond, KMPerHour, KMPerSecond, MetersPerHour, MetersPerSecond, Degree, WattsPerSquareMeter, KiloWattsPerSquareMeter, MilliWattsPerSquareCentiMeter, MilliJoulesPerSquareCentiMeter, VolumetricWaterContent, Percentage, PartsPerMillion, MicroMol, MicroMolesPerLiter, SiemensPerSquareMeterPerMole, MilliSiemensPerCentiMeter, Centibar, DeciSiemensPerMeter, KiloPascal, VolumetricIonContent, Liter, MilliLiter, Seconds, UnixTimestamp, MicroMolPerMeterSquaredPerSecond, and InchesPerHour. To add more, refer to the /ExtendedType API.
+  SensorMeasures > AggregationType  | Either none, average, maximum, minimum, or StandardDeviation.
+  SensorMeasures > Depth  | The depth of the sensor in centimeters. For example, the measurement of moisture 10 cm under the ground.
+  SensorMeasures > Description  | Provide a meaningful description of the measurement.
   Name  | Name to identify resource. For example, the model name or product name.
   Description  | Provide a meaningful description of the model.
   Properties  | Additional properties from the manufacturer.
-  **Sensor**  | **Sensor corresponds to a physical sensor that records values. A sensor is typically connected to a device with a device ID.** |
-  hardwareId  | Unique ID for the sensor set by the manufacturer.
-  sensorModelId  | ID of the associated sensor model.
+  **Sensor**  |  |
+  HardwareId  | Unique ID for the sensor set by the manufacturer.
+  SensorModelId  | ID of the associated sensor model.
   Location  | Sensor latitude (-90 to +90), longitude (-180 to 180), and elevation (in meters).
-  port > name  |Name and type of the port that the sensor is connected to on the device. This must be the same name as defined in the device model.
-  deviceId  | ID of the device that the sensor is connected to.
+  Port > Name  |Name and type of the port that the sensor is connected to on the device. This must be the same name as defined in the device model.
+  DeviceId  | ID of the device that the sensor is connected to.
   Name  | Name to identify the resource. For example, the sensor name or product name and model number or product code.
   Description  | Provide a meaningful description.
   Properties  | Additional properties from the manufacturer.