DOI: 10.5281/zenodo.3608069
title: Brainport, Urban driving, route request, VRU detection

description: <strong>Scenario description</strong>: Smartphone 3120 sends request, route 2 is being blocked by crowd (depending on run this changes), vehicle receives correct route and drives from west to east. Underway 2 VRU (3121 & 3122) crosses the road. <strong>Session description</strong>: Complete use case: Request vehicle, choose route on CEMA and GeoFenching VRU detection with 2 smartphone detection <strong>Datasets descriptions</strong>: <strong>AUTOPILOT_BrainPort_UrbanDriving_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle Dataset Description This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle <strong>AUTOPILOT_BrainPort_UrbanDriving_EAI2Mobile</strong>: Data from the service to the mobile Dataset Description This dataset contains information sent to the mobile about the Estimated Arrival time and position <strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors Dataset Description This dataset contains information about detected object, with absolute coordinates <strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors Dataset Description This dataset contains information about detected object, with relative coordinates <strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_CEMA_Message</strong>: Data from the service to the vehicle Dataset Description This dataset contains information from the Crowd Estimation and Mobility Analytics service <strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_FlowRadar_Message</strong>: Data from the vehicle to the service Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the vehicle <strong>AUTOPILOT_BrainPort_UrbanDriving_IotVehicleMessage</strong>: 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. <strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_VehicleStatus</strong>: Data sent from the vehicle to the service Dataset Description This dataset contains the current status of the vehicle <strong>AUTOPILOT_BrainPort_UrbanDriving_PositioningSystem</strong>: Data from GPS on the vehicle Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS <strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneGPS</strong>: Data sent by the mobile to the service Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the mobile <strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneStatus</strong>: Data sent from the mobile to the service Dataset Description This dataset contains the current status of the mobile <strong>AUTOPILOT_BrainPort_UrbanDriving_TaxiRequest</strong>: Data sent from the mobile to the service Dataset Description This dataset contains the requests for a taxi from the mobile phones <strong>AUTOPILOT_BrainPort_UrbanDriving_Vehicle</strong>: 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 <strong>AUTOPILOT_BrainPort_UrbanDriving_VehicleDynamics</strong>: 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