Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
8
datasets available to search
ShareScore release 0.7.1
Dataset results
8 results for “VRU detection”
Versailles, Urban driving, Automated Driving and VRU detection
<p>Scenario description: cyclist and pedestrian detection during automated driving.</p> <p>Session description: Automated Driving part of the trip only. Two rounds: the first one without IoT (VRUs not connected) then with IoT (pedestrian with smartphone/watch and cyclist with connected bike).</p> <p>Datasets descriptions:</p> <p><strong>AUTOPILOT_Versailles_UrbanDriving_Vehicle: </strong>Data generated from the vehicle sensors</p> <p>Vehicle datasets generated by the vehicle sensors during urban driving at Versailles. This includes the data coming from the CAN bus and GPS. It includes following kind of datasets: Vehicle: general data (speed, battery), PositioningSystem: data from GPS, VehicleDynamics: data about dynamic (acceleration...), Accel: acceleration data, EnvironmentSensorsAbsolute: environment sensors in absolute coordinates</p> <p><strong>AUTOPILOT_Versailles_UrbanDriving_V2X: </strong>V2X messages during uraban driving sessions</p> <p>Data exchanged with other vehicles and pedestrian during urban driving. SortOfCam: messages sent or received from bicycles</p> <p><strong>AUTOPILOT_Versailles_UrbanDriving_IoT: </strong>Data extracted from IoT oneM2M platform</p> <p>This dataset refers to messages exchanged by urban driving and car sharing application with vehicle, across oneM2M platform. oneM2M: car sharing status data</p> <p><strong>AUTOPILOT_Versailles_UrbanDriving_CAM: </strong>CAM messages</p> <p>This dataset refers to messages captured inside the vehicle during car sharing.</p>
Brainport, Urban driving, route request, VRU detection
<p><strong>Scenario description</strong>:</p> <p>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.</p> <p><strong>Session description</strong>:</p> <p>Complete use case: Request vehicle, choose route on CEMA and GeoFenching VRU detection with 2 smartphone detection</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>Dataset Description This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EAI2Mobile</strong>: Data from the service to the mobile</p> <p>Dataset Description This dataset contains information sent to the mobile about the Estimated Arrival time and position</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_CEMA_Message</strong>: Data from the service to the vehicle</p> <p>Dataset Description This dataset contains information from the Crowd Estimation and Mobility Analytics service</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_FlowRadar_Message</strong>: Data from the vehicle to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>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.</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_VehicleStatus</strong>: Data sent from the vehicle to the service</p> <p>Dataset Description This dataset contains the current status of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneGPS</strong>: Data sent by the mobile to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneStatus</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the current status of the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_TaxiRequest</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the requests for a taxi from the mobile phones</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Urban driving, VRU smartphone detection, camera detection
<p><strong>Scenario description</strong>:</p> <p>Only GeoFenching VRU detection with 3 smartphone detection<br> Test detection of multiple VRUs close to each other and compare with camera detections.<br> 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</p> <p><strong>Session description</strong>:</p> <p>Route is fixed, vehicle drives north - south. Underway 1 group of 3 VRU crosses the road.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>Dataset Description This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EAI2Mobile</strong>: Data from the service to the mobile</p> <p>Dataset Description This dataset contains information sent to the mobile about the Estimated Arrival time and position</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_CEMA_Message</strong>: Data from the service to the vehicle</p> <p>Dataset Description This dataset contains information from the Crowd Estimation and Mobility Analytics service</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_FlowRadar_Message</strong>: Data from the vehicle to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>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.</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_VehicleStatus</strong>: Data sent from the vehicle to the service</p> <p>Dataset Description This dataset contains the current status of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneGPS</strong>: Data sent by the mobile to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneStatus</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the current status of the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_TaxiRequest</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the requests for a taxi from the mobile phones</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Urban driving, route request, rerouting reception, VRU detection
<p><strong>Scenario description</strong>:</p> <p>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 1 VRU crosses the road.</p> <p><strong>Session description</strong>:</p> <p>Complete use case: Request vehicle, choose route on CEMA and GeoFenching VRU detection with 1 smartphone detection</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>Dataset Description This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EAI2Mobile</strong>: Data from the service to the mobile</p> <p>Dataset Description This dataset contains information sent to the mobile about the Estimated Arrival time and position</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_CEMA_Message</strong>: Data from the service to the vehicle</p> <p>Dataset Description This dataset contains information from the Crowd Estimation and Mobility Analytics service</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_FlowRadar_Message</strong>: Data from the vehicle to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>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.</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_VehicleStatus</strong>: Data sent from the vehicle to the service</p> <p>Dataset Description This dataset contains the current status of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneGPS</strong>: Data sent by the mobile to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneStatus</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the current status of the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_TaxiRequest</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the requests for a taxi from the mobile phones</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Urban driving, car rebalancing, VRU detection, rerouting
<p><strong>Scenario description</strong>:</p> <p>Precondition:<br> - AD Vehicle (3177) is at starting position<br> - VRU with Smartphone (3120) is at end position<br> - VRU with Smartphone (3121) and FlowRadar (3175) is positioned halfway the vehicle track<br> - CEMA device is on route 2 and detecting crowd<br> <br> Initiate Rebalancing phase:<br> 1. Smartphone 3120: send taxi request (send end location to vehicle (lon / lat))<br> Initiate Routing phase:<br> 2. CEMA devices detect crowds on route 1 or route 2 --> dynamically change routes base on CEMA<br> 3. Motion planning: Vehicle uses CEMA detection and call taxi request as input for choosing one of the two routes<br> Initiate Urban Driving phase (incl. VRU detection)<br> 4. Vehicle starts driving<br> 5. Underway VRU (3121) is detected using smartphone and FlowRadar ITS-G5<br> 6. With GeoFenching, vehicle starts slowing down on smartphone<br> 7. With camera detection vehicle brakes when VRU is inline of camera<br> 8. After VRU passes, vehicle continues journey<br> 9. Vehicle arrives at requested end point (at VRU 3120).</p> <p><strong>Session description</strong>:</p> <p>Rebalancing:<br> - relocate the vehicle on request<br> Urban Driving:<br> - rerouting on crowd estimation (CEMA)<br> - VRU detection with GeoFenching in vehicle (speed reduction) and warning on VRU smartphone</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>Dataset Description This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EAI2Mobile</strong>: Data from the service to the mobile</p> <p>Dataset Description This dataset contains information sent to the mobile about the Estimated Arrival time and position</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_CEMA_Message</strong>: Data from the service to the vehicle</p> <p>Dataset Description This dataset contains information from the Crowd Estimation and Mobility Analytics service</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_FlowRadar_Message</strong>: Data from the vehicle to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>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.</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_VehicleStatus</strong>: Data sent from the vehicle to the service</p> <p>Dataset Description This dataset contains the current status of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneGPS</strong>: Data sent by the mobile to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneStatus</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the current status of the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_TaxiRequest</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the requests for a taxi from the mobile phones</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Urban driving, request route, VRU detection, route correction
<p><strong>Scenario description</strong>:</p> <p>Complete use case: Request vehicle, choose route on CEMA and GeoFenching VRU detection with 4 smartphone detections<br> Test detection of multiple VRUs close to each other and compare with camera detections.<br> Test GeoFence area of detection with different pedestrian walking paths (for pedestrian prediction)<br> Make comparison with GeoFenching enabled (runs 1-12) and with GeoFencing disabled (runs 13-25)</p> <p><strong>Session description</strong>:</p> <p>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 groups of each 2 VRU crosses, or walk alongside the road (see Test Plan Table 3 for exact walking patterns).</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>Dataset Description This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EAI2Mobile</strong>: Data from the service to the mobile</p> <p>Dataset Description This dataset contains information sent to the mobile about the Estimated Arrival time and position</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_CEMA_Message</strong>: Data from the service to the vehicle</p> <p>Dataset Description This dataset contains information from the Crowd Estimation and Mobility Analytics service</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_FlowRadar_Message</strong>: Data from the vehicle to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>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.</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_VehicleStatus</strong>: Data sent from the vehicle to the service</p> <p>Dataset Description This dataset contains the current status of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneGPS</strong>: Data sent by the mobile to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneStatus</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the current status of the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_TaxiRequest</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the requests for a taxi from the mobile phones</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Urban driving, fixed route, VRU detection
<p><strong>Scenario description</strong>:</p> <p>Only GeoFenching VRU detection with 3 smartphone detection<br> Test detection of multiple VRUs close to each other and compare with camera detections.<br> Test different size GeoFence area (20m wide x 50m long) of detection with different pedestrian walking paths (for pedestrian prediction) </p> <p><strong>Session description</strong>:</p> <p>Route is fixed, vehicle drives north - south. Underway 1 group of 3 VRU crosses the road.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>Dataset Description This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EAI2Mobile</strong>: Data from the service to the mobile</p> <p>Dataset Description This dataset contains information sent to the mobile about the Estimated Arrival time and position</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>Dataset Description This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_CEMA_Message</strong>: Data from the service to the vehicle</p> <p>Dataset Description This dataset contains information from the Crowd Estimation and Mobility Analytics service</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_FlowRadar_Message</strong>: Data from the vehicle to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>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.</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_IOT_VehicleStatus</strong>: Data sent from the vehicle to the service</p> <p>Dataset Description This dataset contains the current status of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneGPS</strong>: Data sent by the mobile to the service</p> <p>Dataset Description This dataset contains the GPS informaton (speed,position,heading) from the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_SmartphoneStatus</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the current status of the mobile</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_TaxiRequest</strong>: Data sent from the mobile to the service</p> <p>Dataset Description This dataset contains the requests for a taxi from the mobile phones</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_UrbanDriving_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>Dataset Description This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Vigo,Urban driving, GLOSA and VRU detection
<p><strong>Scenario description:</strong></p> <p>GLOSA and VRU detection. The autonomous vehicle makes several turns on the scenario adapting its speed to the state of the traffic light. At an intersection controlled by a camera connected via IoT, a VRU is introduced into one of the laps so that the autonomous vehicle brakes when it receives the information via IoT.</p> <p><strong>Session description:</strong></p> <p>Human factor tests performed at CTAG proving grounds.</p> <p><strong>Datasets descriptions:</strong><br> <br> <strong>AUTOPILOT_Vigo_UrbanDriving_Vehicle: </strong>Data extracted from the CAN of the vehicle. Contains data regarding the state of the vehicle, such as speed, engine speed or fuel consumption.</p> <p><strong>AUTOPILOT_Vigo_UrbanDriving_VehicleDynamics: </strong>Data extracted from the CAN of the vehicle.Contains data regarding the dynamic state of the vehicle, such as speed limit, acceleration or yaw rate.</p> <p><strong>AUTOPILOT_Vigo_UrbanDriving_DriverVehicleInteraction: </strong>Data extracted from the CAN of the vehicle. Contains all the information about the actions that the driver can perform, such as the state of the brake, the steering wheel and the throttle.</p> <p><strong>AUTOPILOT_Vigo_UrbanDriving_EnviromentSensorsAbsolute: </strong>Data extracted from the sensors of the vehicle in absolute coordinates.</p> <p><strong>AUTOPILOT_Vigo_UrbanDriving__EnviromentSensorsRelative: </strong>Data extracted from the sensors of the vehicle in relative coordinates.</p> <p><strong>AUTOPILOT_Vigo_UrbanDriving_Positioning:</strong> Data from the GPS of the vehicle, such as latitude longitude and heading.</p> <p><strong>AUTOPILOT_Vigo_UrbanDriving_IoT: </strong>Data of the communications via IoT, coming from the OBU of the vehicle, the IoT server and the RSU that controls the camera and the traffic light.<br> </p> <p> </p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.