... | ... | @@ -74,7 +74,7 @@ In the topic, the events are published in JSON format. Here you can see an examp |
|
|
|
|
|
- beaconTypeId (integer number): beacon type identifier. 1 = Individual, 2 = Group
|
|
|
|
|
|
- timestamp (UTC time): date and time in UTC format of when the event was generated. It must be a maximum of 30 seconds old with respect to UTC time. The date must end with the character 'Z' that marks that it is in UTC
|
|
|
- timestamp (UTC time): date and time in UTC format of when the event was generated. It must be a maximum of 15 seconds old with respect to UTC time. The date must end with the character 'Z' that marks that it is in UTC
|
|
|
|
|
|
- deviceTypeId (integer number): identifier of the type of device from which the information is sent. 1 = Baliza, 2 = App
|
|
|
|
... | ... | @@ -92,9 +92,9 @@ In the topic, the events are published in JSON format. Here you can see an examp |
|
|
|
|
|
- latStart (decimal number): latitude in WGS 84 coordinate system where the event was generated
|
|
|
|
|
|
- lonEnd (decimal number): longitude in WGS 84 coordinate system where the event was generated
|
|
|
- lonEnd (decimal number): longitude in WGS 84 coordinate system where the event ended
|
|
|
|
|
|
- latEnd (decimal number): latitude in WGS 84 coordinate system where the event was generated
|
|
|
- latEnd (decimal number): latitude in WGS 84 coordinate system where the event ended
|
|
|
|
|
|
See more information and a connection example [here](https://gitlab.cs.cmobility30.es/dgt3.0_eng/general/-/wikis/MQTT).
|
|
|
|
... | ... | |