This use case has a REST API for publishing (sending) the data. There are two types of publishers:
-
The Organizers of the Event that using the V2 signals, indicate the situation in real time of the event.
-
The devices distributed in the event, cones, which indicate the different road closures that affect the event in question.
Required methods for integration with V2 signals
Update of the dynamic information of the progress of a sporting event
The event is the main part of this data ingestion API. With this event you can update the dynamic information of the sporting event. With it, the information received by the V2 signals of the escort cars located at the head and tail of the sporting event will be updated.The information will be sent with the following fields in the following format:
Information about the endpoint:
-
Method: POST
-
URL: {baseUrl}/v1/tracking/event
-
Body:
{
"actionId": "CLI_235",
"beaconId": "cff92179-dc0a-47da-bd9e-5e9c5b14d251",
"beaconTypeId": 1,
"timestamp": "2022-03-15T13:34:00.000Z",
"lon" : "-7.009654361999935",
"lat" : "38.52736428400004",
"hdop" : 5,
"speed": 50
}
* = Required field
-
(*) actionId (text): unique identifier of the event.
-
(*) beaconId (text): unique identifier of the beacon (for example, the MAC).
-
(*) beaconTypeId (enter number): Beacon type identifier. Possible values in /beaconTypes. 1=Start, 2=End. The values (3 = Intermediate and 4 = Unique) do not apply to this type of event.
-
(*) 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.
-
(*) lon (decimal number): longitude of WGS 84 type coordinates where the event was generated.
-
(*) lat (decimal number): latitude of WGS 84 type coordinate where the event was generated.
-
(*) hdop (enter number): DOP value to determine the quality of the GPS information. More information here
-
(*) speed (decimal number): speed in kilometers per hour at which the element is at the moment the event is sent
Note: To identify an event that requires dynamic tracking (type of tracking that requires two beacons), each one must be identified with its respective position in the test:
- If the beacon is on the lead vehicle, the value of the field beaconTypeId will be 1= Start.
- If the beacon is on the trailing vehicle, the value of the field beaconTypeId will be 2= End.
Update of the static information of the progress of a sporting event
The event is the main part of this data ingestion API. With this event you can update the dynamic information of the sporting event. With it, the information received by the V2 signals will be updated as the event is completed. The information will be delivered with the following fields in the following format:
Information about the endpoint:
-
Method: POST
-
URL: {baseUrl}/v1/tracking/event
-
Body:
{
"actionId": "CLI_235",
"beaconId": "cff92179-dc0a-47da-bd9e-5e9c5b14d251",
"beaconTypeId": 4,
"timestamp": "2022-03-15T13:34:00.000Z",
"lon" : "-7.009654361999935",
"lat" : "38.52736428400004",
"hdop" : 5,
"speed": 50
}
* = Required field
-
(*) actionId (text): unique identifier of the event.
-
(*) beaconId (text): unique identifier of the beacon (for example, the MAC).
-
(*)beaconTypeId (enter number): Beacon type identifier. The only possible value is beaconType/ 4=Unique. The rest of the values do not apply to this tracking method.
-
(*) 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.
-
(*) lon (decimal number): longitude of WGS 84 type coordinates where the event was generated.
-
(*) lat (decimal number): latitude of WGS 84 type coordinate where the event was generated.
-
(*) hdop (enter number): DOP value to determine the quality of the GPS information. More information here
-
(*) speed (decimal number): speed in kilometers per hour at which the element is at the moment the event is sent
Note: To identify an event that requires a static trace (type of trace that requires a single beacon), the beacon must be identified with a beaconTypeId field value of 1= Start.
Methods required for the integration of connected cones
Publication of the location of a cone
The cones are used to cut the different roads that are on the perimeter of the sports event. The cone will send its positioning every certain period of time. Once the cone is deactivated, it means that the road has been cleared and circulation can be restored on it.
-
Method: POST
-
URL: {baseUrl}/v1/events
-
Response:
{ "actionId": "CLI_236", "beaconId": "862506044003724", "beaconTypeId": 4, "timestamp": "2021-03-15T13:34:00.000Z", "lat": 41.456123, "lon": 1.928123, "vehicleTypeId": 0, "hdop": 1, "deviceTypeId": 3, "deviceUseTypeId": 3, "speed": 0 }
(*)= Required field
· (*)actionId (string): Unique identifier of the event
· (*)beaconId (string): Unique identifier of the beacon (for example, the MAC)
· (*)beaconTypeId (integer): Beacon type identifier. The only possible value is /beaconTypes. 4=Unique
· (*)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 15 seconds old with respect to UTC time and it can not be a future timestamp. The date must end with the character 'Z' that marks that it is in UTC.
· (*)lat (decimal number): WGS 84 type coordinate latitude where the event was generated
· (*)lon (decimal number): Longitude of WGS 84 type coordinates where the event was generated
· (*)vehicleTypeId (integer): Identifier of the type of event. The only possible value for /vehicleTypeId is 0 (None).
· (*)eventTypeId (integer) : identifier of the event type. Possible values 1 = On, 2 = Activated, 3 = Off
· (*)hdop: DOP value to determine the quality of the GPS information. More information here
· (*)deviceTypeId: Identifier of the type of device from which the information is sent. The value is /DeviceTypes. 3= Cone.
· (*)deviceUseTypeId: Identifier of the type of use of the device that sends the information. deviceUseTypeId =3 for infrastructure
· (*)speed (decimal number): speed in kilometers per hour at which the element is at the moment the event is sent
Cone requirements
In order to maintain the quality of the messages, the following requirements will apply to the content of the messages:
- The geographical position must be contained in the Spanish territory
- The position provided by the GPS must not have an error greater than 5 meters
- The order, quantity and frequency of messages are set out below:
- Events of type On, a single message (optional).
- Events of type Activated, as many messages as the activity of the beacon lasts with a frequency of 10 minutes between messages.
- Events of type Off, a single message.