Verified Commit a4df6517 authored by deniss.marinuks's avatar deniss.marinuks
Browse files

updated readme to camelCase

parent 7176cc35
......@@ -7,8 +7,8 @@
| Key | Description |
| ------------- |:-------------|
| **device_id** | id that you receive from sensor registry manager after registration of the device |
| **serial_number** | Serial number of the device. It MUST be inserted dynamically and MUST NOT be hard-coded. |
| **deviceID** | id that you receive from sensor registry manager after registration of the device |
| **serialNumber** | Serial number of the device. It MUST be inserted dynamically and MUST NOT be hard-coded. |
| **timestamp** | The timestamp of creating the telemetry report. The format MUST BE in ISO 8601 format, have the precision down to seconds and include a UTC offset e.g. 2021-11-09T11:32:48+0100 |
| **status** | error: **true** or **false** if there is any problem with the device. <br /> message: detailed, free-text description of the status. The message MAY BE empty, regardless of the error status. |
......@@ -21,8 +21,8 @@ Everything else is optional and can be added to telemetry json file.
| Key | Description |
| ------------- |:-------------|
| **device_id** | id that you receive from sensor registry manager after registration of the device |
| **serial_number** | Serial number of the device. It MUST be inserted dynamically and MUST NOT be hard-coded. |
| **deviceID** | id that you receive from sensor registry manager after registration of the device |
| **serialNumber** | Serial number of the device. It MUST be inserted dynamically and MUST NOT be hard-coded. |
| **timestamp** | The start and stop fields format MUST BE in ISO 8601 format, have the precision down to seconds and include a UTC offset e.g. 2021-11-09T11:32:48+0100. If you only have a start timestamp, use the same value for start and stop. |
| **processed** | **true** or **false**, if the data is in raw format it should be set to **false** |
| **location** | Refer to [location paramter](#1-location). It is mandatory field in metadata. |
......@@ -50,7 +50,7 @@ Everything else is optional and can be added to telemetry json file.
"latitude": 52.520645,
"longitude": 13.409779,
"altitude": 43,
"geodetic_datum": "WGS84"
"geodeticDatum": "WGS84"
}
```
......@@ -59,7 +59,7 @@ Everything else is optional and can be added to telemetry json file.
| **latitude** | true | Latitude in decimal degrees |
| **longitude** | true | Longitude in decimal degrees |
| **altitude** | false | Altitude in meters |
| **geodetic_datum** | false | The geodetic datum. If not present, WGS84 is assumed.|
| **geodeticDatum** | false | The geodetic datum. If not present, WGS84 is assumed.|
<br />
<br />
......
......@@ -13,7 +13,7 @@
"type": "number",
"optional": true
},
"geodetic_datum": {
"geodeticDatum": {
"type": "string",
"optional": true
}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment