-
Notifications
You must be signed in to change notification settings - Fork 133
Expand file tree
/
Copy pathosi_trafficupdate.proto
More file actions
55 lines (47 loc) · 1.88 KB
/
Copy pathosi_trafficupdate.proto
File metadata and controls
55 lines (47 loc) · 1.88 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
syntax = "proto2";
option optimize_for = SPEED;
import "osi_version.proto";
import "osi_common.proto";
import "osi_object.proto";
import "osi_hostvehicledata.proto";
package osi3;
//
// \brief The traffic update message is provided by traffic
// participant models to provide updates to their position and
// state back to the simulation environment.
//
// \note For reasons of convenience and consistency, the
// updated information is provided as a MovingObject. Certain fields
// of this sub-message are not required to be set and will be ignored by the
// simulation environment, because they are static information.
// Instead of creating a seperate message type for only the non-static
// information, re-use existing message.
//
message TrafficUpdate
{
// The interface version used by the sender (traffic participant model).
//
optional InterfaceVersion version = 1;
// The data timestamp of the simulation environment. Zero time is arbitrary
// but must be identical for all messages. Zero time does not need to
// coincide with the UNIX epoch. Recommended is the starting time point of
// the simulation.
//
// \note For moving object update data the timestamp coincides both with
// the notional simulation time the data applies to and the time it was sent.
// There is no inherent latency for moving object update data, as opposed
// to sensor data.
//
optional Timestamp timestamp = 2;
// Updated moving object
//
// \note Only the following members are considered in updates: id, base member
// without dimension and base_polygon and the vehicle_classification.light_state.
// All other members can be left undefined and will be
// ignored by the receiver of this message.
//
optional MovingObject update = 3;
// Updated host vehicle data
//
optional HostVehicleData host_vehicle_data_update = 4;
}