... | ... | @@ -195,13 +195,13 @@ Description of the fields for the use case of "Eventos deportivos" through the D |
|
|
|
|
|
- **geom**(string): Collection of coordinates that represent the total route of the segment being tracked. From the collection of coordinates that is published, the first in the list corresponds to the location where the event starts, while the last in the list corresponds to the location where the event ends.
|
|
|
|
|
|
- **tsinicio**(ZonedDateTime): Event start date.
|
|
|
- **tsinicio**(ZonedDateTime): Event start date.
|
|
|
|
|
|
- **tsfin**(ZonedDateTime): Event end date.
|
|
|
- **tsfin**(ZonedDateTime): Event end date.
|
|
|
|
|
|
- **evento** (Integer): Name of the event resolved in DGT.
|
|
|
- **evento** (Integer): Name of the event resolved in DGT.
|
|
|
|
|
|
- **timestamp** (UTC Date): Date and time in UTC format of the moment in which the event was generated. It needs to be a maximum of 30 seconds old with respect to UTC time.
|
|
|
- **timestamp** (UTC Date): Date and time in UTC format of the moment in which the event was generated. It needs to be a maximum of 30 seconds old with respect to UTC time.
|
|
|
|
|
|
See more information and a connection example [here](https://gitlab.cs.cmobility30.es/dgt3.0_esp/general/-/wikis/MQTT).
|
|
|
|
... | ... | |