Get desktop application:
View/edit binary Protocol Buffers messages
A segment of a lane with a given adjacent boundary.
Used in:
,The index into the lane's polyline where this lane boundary starts.
The index into the lane's polyline where this lane boundary ends.
The adjacent boundary feature ID of the MapFeature for the boundary. This can either be a RoadLine feature or a RoadEdge feature.
The adjacent boundary type. If the boundary is a road edge instead of a road line, this will be set to TYPE_UNKNOWN.
Used in:
The polygon defining the outline of the crosswalk. The polygon is assumed to be closed (i.e. a segment exists between the last point and the first point).
The dynamic map information at a single time step.
Used in:
The traffic signal states for all observed signals at this time step.
Used in:
The timestamp associated with the dynamic feature data.
The set of traffic signal states for the associated time step.
Used in:
The speed limit for this lane.
True if the lane interpolates between two other lanes.
The polyline data for the lane. A polyline is a list of points with segments defined between consecutive points.
A list of IDs for lanes that this lane may be entered from.
A list of IDs for lanes that this lane may exit to.
The boundaries to the left of this lane. There may be different boundary types along this lane. Each BoundarySegment defines a section of the lane with a given boundary feature to the left. Note that some lanes do not have any boundaries (i.e. lane centers in intersections).
The boundaries to the right of this lane. See left_boundaries for details.
A list of neighbors to the left of this lane. Neighbor lanes include only adjacent lanes going the same direction.
A list of neighbors to the right of this lane. Neighbor lanes include only adjacent lanes going the same direction.
Type of this lane.
Used in:
Used in:
The feature ID of the neighbor lane.
The self adjacency segment. The other lane may only be a neighbor for only part of this lane. These indices define the points within this lane's polyline for which feature_id is a neighbor. If the lanes are neighbors at disjoint places (e.g., a median between them appears and then goes away) multiple neighbors will be listed. A lane change can only happen from this segment of this lane into the segment of the neighbor lane defined by neighbor_start_index and neighbor_end_index.
The neighbor adjacency segment. These indices define the valid portion of the neighbor lane's polyline where that lane is a neighbor to this lane. A lane change can only happen into this segment of the neighbor lane from the segment of this lane defined by self_start_index and self_end_index.
A list of segments within the self adjacency segment that have different boundaries between this lane and the neighbor lane. Each entry in this field contains the boundary type between this lane and the neighbor lane along with the indices into this lane's polyline where the boundary type begins and ends.
The full set of map features.
A set of dynamic states per time step. These are ordered in consecutive time steps.
Used in:
,A unique ID to identify this feature.
Type specific data.
Used in:
, , , , , ,Position in meters. The origin is an arbitrary location.
Used in:
Coordinates of the center of the object bounding box.
The dimensions of the bounding box in meters.
The yaw angle in radians of the forward direction of the bounding box (the vector from the center of the box to the middle of the front box segment) counter clockwise from the X-axis (right hand system about the Z axis). This angle is normalized to [-pi, pi).
The velocity vector in m/s. This vector direction may be slightly different from the heading of the bounding box.
False if the state data is invalid or missing.
An object that must be predicted for the scenario.
Used in:
An index into the Scenario `tracks` field for the object to be predicted.
The difficulty level for this object.
A difficulty level for predicting a given track.
Used in:
Used in:
The type of road edge.
The polyline defining the road edge. A polyline is a list of points with segments defined between consecutive points.
Type of this road edge.
Used in:
Physical road boundary that doesn't have traffic on the other side (e.g., a curb or the k-rail on the right side of a freeway).
Physical road boundary that separates the car from other traffic (e.g. a k-rail or an island).
Used in:
The type of the lane boundary.
The polyline defining the road edge. A polyline is a list of points with segments defined between consecutive points.
Type of this road line.
Used in:
,The unique ID for this scenario.
Timestamps corresponding to the track states for each step in the scenario. The length of this field is equal to tracks[i].states_size() for all tracks i and equal to the length of the dynamic_map_states_field.
The index into timestamps_seconds for the current time. All time steps after this index are future data to be predicted. All steps before this index are history data.
Tracks for all objects in the scenario. All object tracks in all scenarios in the dataset have the same number of object states. In this way, the tracks field forms a 2 dimensional grid with objects on one axis and time on the other. Each state can be associated with a timestamp in the 'timestamps_seconds' field by its index. E.g., tracks[i].states[j] indexes the i^th agent's state at time timestamps_seconds[j].
The dynamic map states in the scenario (e.g. traffic signal states). This field has the same length as timestamps_seconds. Each entry in this field can be associated with a timestamp in the 'timestamps_seconds' field by its index. E.g., dynamic_map_states[i] indexes the dynamic map state at time timestamps_seconds[i].
The set of static map features for the scenario.
The index into the tracks field of the autonomous vehicle object.
A list of objects IDs in the scene detected to have interactive behavior. The objects in this list form an interactive group. These IDs correspond to IDs in the tracks field above.
A list of tracks to generate predictions for. For the challenges, exactly these objects must be predicted in each scenario for test and validation submissions. This field is populated in the training set only as a suggestion of objects to train on.
Used in:
The polygon defining the outline of the speed bump. The polygon is assumed to be closed (i.e. a segment exists between the last point and the first point).
Used in:
The IDs of lane features controlled by this stop sign.
The position of the stop sign.
The object states for a single object through the scenario.
Used in:
The unique ID of the object being tracked. The IDs start from zero and are non-negative.
The type of object being tracked.
The object states through the track. States include the 3D bounding boxes and velocities.
Used in:
This is an invalid state that indicates an error.
Used in:
,The ID for the MapFeature corresponding to the lane controlled by this traffic signal state.
The state of the traffic signal.
The stopping point along the lane controlled by the traffic signal. This is the point where dynamic objects must stop when the signal is in a stop state.
Used in:
States for traffic signals with arrows.
Standard round traffic signals.
Flashing light signals.