Path Events provide additional information along a path. This may be single events, such as a change of vehicle operation mode or information about an electronic stability program event. It can also be continuously collected information such as velocity or curvature measurements. Path Events are of different types and can be mixed in the Path Events list. Path Events reference the Path based on the timestamp of each Path Event. This timestamp may not exactly match a timestamp in the Path, which means interpolation is required during processing of the information in the HERE cloud. Note that Path Events should not be collected before the first Position Estimate in the Path and also not collected after the last Position Estimate in the Path. Path Events are optional in the sensor data submission message. Onnly a Path is provided, which may have a meaning of its own without actual events. Nevertheless given that the HERE Sensor Data Ingestion interface is supposed to collection rich sensor data it is expected that a number of Path Events are typically included. Path Events are included in the sensor message as a list of Path Events. The Path Events are ordered starting with the oldest Path Event towards the newest Path Event. This means they are not grouped by type. A Path Event is typically a complex data type, which has a number of mandatory and optional components. Vehicles must be configured to report the components consistently. For example, if the vehicle reports transmission mode and temperature as part of the VehicleStatus complex type then it must report these two informations at the very beginning of the path initially. Whenever the transmission mode changes, another Path Event must be reported that indicates the transmission mode in the VehicleStatus complex type. Whenever temperature changes, another Path Event must be reported that indicates the temperature change in the VehicleStatus complex type. If by chance two Path Events are reported at the exact same timestamp, then all Information can be merged into one combined Path Events, as long as both events do not have conflicting information. The order within each list of Path Event Types is by timestamp ascending.
| ||VehicleStatus||repeated|| |
The list of zero or more vehicle status messages.
| ||VehicleDynamics||repeated|| |
The list of zero or more vehicleDynamics messages.
| ||SignRecognition||repeated|| |
The list of zero or more sign recognition messages.
| ||LaneBoundaryRecognition||repeated|| |
The list of zero or more LaneBoundaryRecognition messages.
| ||ExceptionalVehicleState||repeated|| |
The list of zero or more ExceptionalVehicleState messages
| ||ProprietaryInfo||repeated|| |
The list of zero or more ProprietaryInfo messages.
| ||EnvironmentStatus||repeated|| |
The list of zero or more Environmental Status messages.
| ||ObjectDetection||repeated|| |
The list of zero or more ObjectDetection messages.
| ||ADServiceAndSensorState||repeated|| |
The list of zero or more ADServiceAndSensorState messages.
| ||SpecificObservedEvent||repeated|| |
The list of zero or more SpecificObservedEvent messages.
| ||RoadCondition||repeated|| |
The list of zero or more RoadCondition messages
| ||RoadBoundaryRecognition||repeated|| |
An sensor event that has specific Information about the road boundary recognition
| ||VehicleManeuverEvent||repeated|| |
The information about the vehicle maneuver or movement.
| ||LocalizationInformation||repeated|| |
An sensor event that has specific Information about the localization system of the vehicle
| ||RoadAttributeRecognition||repeated|| |
An sensor event that has specific Information about road attributes
| ||PassengerEnvironment||repeated|| |
The information covering the passenger environment status in the vehicle.
| ||RoadMarkingRecognition||repeated|| |
An event on recognized Markings on the road surface (lane)
| ||TrafficSignalHeadRecognition||repeated|| |
The information of recognized Traffic Signal Heads. A traffic signal head is the group of lights (green, yellow, red).
| ||ProprietaryDataContainer||repeated|| |
A message object, for proprietary usage.