LoRa Geolocation and Local Gateway decoding
Describes the LoRa Geolocation and Local gateway decoding output
LoRa messages may contain Local Gateway data and Geolocation data based on your Connectivity Plan. If you are using one of the official decoders for a LoRa device and the necessary data is present, then this data will be added to resulting SenML payload.
Note that the deprecated decoders related to the Decoder Migration do not add these records.
You can expect the following data to be added:
Geolocation data
name | type | unit | example | description |
---|---|---|---|---|
latitude | number | lat |
| |
locAccuracy | number | % |
| |
locMethod | string |
| ||
locOrigin | string |
| ||
locPrecision | number | % |
| |
locTime | number |
| ||
longitude | number | lon |
| |
radius | number | m |
|
Local Gateway data
If there is any Local Gateway data, the following fields will be added.
name | type | unit | example | description |
---|---|---|---|---|
detectedBeacon | string |
| ||
detectedBeaconSNR | string |
| ||
DvLocOrigin | string |
| ||
DvLocOriginID | string |
| ||
DvLocTime | string |
|
In addition, for each Local Gateway the following fields may be added where i is replaced by the index of the gateway (starting with 1)
name | type | unit | example | description |
---|---|---|---|---|
beacon_i | string |
| The identifier of the beacon. Always present. For the first beacon the name is | |
DvLocation | string |
| Present if this beacon received this uplink. | |
DvNearByLoc | string |
| Present if this beacon did not receive this uplink. |
Example SenML
SenML can be structured in different ways, and we do not guarantee the examples below will look the same as what you will receive on your Destination. To make sure you can handle the SenML optimally, take a look at our documentation about Understanding and Interpreting SenML Data.
Last updated