Brainport, Urban driving, VRU smartphone detection, camera detection

Scenario description:

Only GeoFenching VRU detection with 3 smartphone detection
Test detection of multiple VRUs close to each other and compare with camera detections.
Test different size GeoFence area (20m wide x 50m long) of detection with different pedestrian walking paths (for pedestrian prediction) see Test plan Table 4

Session description:

Route is fixed, vehicle drives north - south. Underway 1 group of 3 VRU crosses the road.

Datasets descriptions:

AUTOPILOT_BrainPort_UrbanDriving_DriverVehicleInteraction: Data extracted from the CAN of the vehicle

Dataset Description This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle

AUTOPILOT_BrainPort_UrbanDriving_EAI2Mobile: Data from the service to the mobile

Dataset Description This dataset contains information sent to the mobile about the Estimated Arrival time and position

AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsAbsolute: Data extracted from the vehicle environment sensors

Dataset Description This dataset contains information about detected object, with absolute coordinates

AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsRelative: Data extracted from the vehicle environment sensors

Dataset Description This dataset contains information about detected object, with relative coordinates

AUTOPILOT_BrainPort_UrbanDriving_IOT_CEMA_Message: Data from the service to the vehicle

Dataset Description This dataset contains information from the Crowd Estimation and Mobility Analytics service

AUTOPILOT_BrainPort_UrbanDriving_IOT_FlowRadar_Message: Data from the vehicle to the service

Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the vehicle

AUTOPILOT_BrainPort_UrbanDriving_IotVehicleMessage: Data sent between all devices, vehicles and services

Dataset Description Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.

AUTOPILOT_BrainPort_UrbanDriving_IOT_VehicleStatus: Data sent from the vehicle to the service

Dataset Description This dataset contains the current status of the vehicle

AUTOPILOT_BrainPort_UrbanDriving_PositioningSystem: Data from GPS on the vehicle

Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS

AUTOPILOT_BrainPort_UrbanDriving_SmartphoneGPS: Data sent by the mobile to the service

Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the mobile

AUTOPILOT_BrainPort_UrbanDriving_SmartphoneStatus: Data sent from the mobile to the service

Dataset Description This dataset contains the current status of the mobile

AUTOPILOT_BrainPort_UrbanDriving_TaxiRequest: Data sent from the mobile to the service

Dataset Description This dataset contains the requests for a taxi from the mobile phones

AUTOPILOT_BrainPort_UrbanDriving_Vehicle: Data from the CAN and sensors about the state of the vehicle

Dataset Description This dataset contains a.o temperature and battery state of the vehicles

AUTOPILOT_BrainPort_UrbanDriving_VehicleDynamics: Data from the CAN and sensors about the state of the vehicle

Dataset Description This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors