... | ... | @@ -144,7 +144,9 @@ The cones are used to cut the different roads that are on the perimeter of the s |
|
|
|
|
|
· **(*)lon** (decimal number): Longitude of WGS 84 type coordinates where the event was generated
|
|
|
|
|
|
· **(*)vehicleTypeId** (integer): Identifier of the type of event. Possible values in /eventTypes. 1 = VAC on the way, 2 = VAC in intervention, 3 = VAC intervention completed.
|
|
|
· **(*)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](https://en.wikipedia.org/wiki/Dilution_of_precision_(navigation))
|
|
|
|
... | ... | @@ -154,4 +156,13 @@ The cones are used to cut the different roads that are on the perimeter of the s |
|
|
|
|
|
· **(*)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:
|
|
|
1. Events of type **On**, a single message (optional).
|
|
|
1. Events of type **Activated**, as many messages as the activity of the beacon lasts with a frequency of 10 minutes between messages.
|
|
|
1. Events of type **Off**, a single message. |