Skip to main content
Powered by ShareScore

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.

12

datasets available to search

ShareScore release 0.7.1

Reset

Dataset results

12 results for “Automated parking”

Learn how ShareScore rates datasets ↗
zenodo40/100

Brainport, Automated valet parking, dropoff scenario TNO vehicle

<p><strong>Scenario description</strong>:</p> <p>The AD-vehicle receives parking command message (AutoPilot.VehicleCommand) containing the destination parking spot and the free obstacle route and drives from the drop-off position and parks to the destination parking spot. During the parking process the vehicle send two type of messages (AutoPilot.PositionEstimate and AutoPilot.VehicleAVPStatus)</p> <p><strong>Session description</strong>:</p> <p>The dropoff scenario with TNO vehicle. TNO vehicle parks autonomously from the dropoff location to the selected parking spot at the parking area on the automotive campus.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
zenodo40/100

Brainport, Automated valet parking, autonomous parking after dropoff

<p><strong>Scenario description</strong>:</p> <p>The Vehicle received parking command message (AutoPilot.VehicleCommand) containing the destination parking spot and the free obstacle route and drives from the drop-off position and parks to the destination parking spot. During the parking process the vehicle send the two type of messages (AutoPilot.PositionEstimate and AutoPilot.VehicleAVPStatus)</p> <p><strong>Session description</strong>:</p> <p>The TNO vehicle parks autonomously from the dropoff to the selected parking spot in the parking place at the automotive campus.&nbsp;</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
zenodo40/100

Brainport, Automated valet parking, TNO vehicle, automated pickup

<p><strong>Scenario description</strong>:</p> <p>The AD-vehicle receives parking command message (AutoPilot.VehicleCommand) containing the destination pickup location and the free obstacle route and drives from the parking spot and parks to the destination pickup location. During the collection process the vehicle sends two type of messages (AutoPilot.PositionEstimate and AutoPilot.VehicleAVPStatus)</p> <p><strong>Session description</strong>:</p> <p>The pickup Scenario with TNO vehicle. TNO vehicle parks autonomously from the parking spot to the pickup location at the parking area on the automotive campus.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
zenodo40/100

Brainport, Automated valet parking, RS camera parking spot occupancy

<p><strong>Scenario description</strong>:</p> <p>RS Camera parking spot occupancy detection and publication of the iot message from type AutoPilot.ParkingSpotDetection to the PMS via IoT platforms</p> <p><strong>Session description</strong>:</p> <p>A AD-car parks to the selected parking spot&nbsp; the rs camera detect the car at the parking spot and publish the occupancy information to the PMS for parking management purpose</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
zenodo40/100

Brainport, Automated valet parking, dropoff scenario, DLR vehicle

<p><strong>Scenario description</strong>:</p> <p>The AD-vehicle receives parking command message (AutoPilot.VehicleCommand) containing the destination parking spot and the free obstacle route and drives from the drop-off position and parks to the destination parking spot. During the parking process the vehicle send two type of messages (AutoPilot.PositionEstimate and AutoPilot.VehicleAVPStatus)</p> <p><strong>Session description</strong>:</p> <p>The dropoff scenario with DLR vehicle. DLR vehicle parks autonomously from the dropoff location to the selected parking spot at the parking area on DLR test area in Brunswick.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
zenodo40/100

Brainport, Automated valet parking, pickup DLR automated vehicle

<p><strong>Scenario description</strong>:</p> <p>The AD-vehicle receives parking command message (AutoPilot.VehicleCommand) containing the destination pickup spot and the free obstacle route and drives from the parking spot and parks to the destination pickup spot. During the collection process the vehicle send two type of messages (AutoPilot.PositionEstimate and AutoPilot.VehicleAVPStatus)</p> <p><strong>Session description</strong>:</p> <p>The pickup scenario with DLR vehicle. DLR vehicle parks autonomously from the parking spot to the destination pickup spot at the parking area on DLR test site in Brunswick.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
zenodo40/100

Brainport, Automated valet parking, dropoff automated DLR vehicle

<p><strong>Scenario description</strong>:</p> <p>The AD-vehicle receives parking command message (AutoPilot.VehicleCommand) containing the destination parking spot and the free obstacle route and drives from the drop-off position and parks to the destination parking spot. During the parking process the vehicle send two type of messages ( AutoPilot.PositionEstimate and AutoPilot.VehicleAVPStatus)</p> <p><strong>Session description</strong>:</p> <p>The dropoff scenario with DLR vehicle. DLR vehicle parks autonomously from the dropoff location to the selected parking spot at the parking area on DLR test area in Brunswick.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
zenodo40/100

Vigo, Automated Valet Parking, Drop off and Pick up

<p><strong>Scenario description:</strong></p> <p>The vehicle starts parked in the drop off area. A drop off request is made to the parking service through the mobile phone application. Once the parking manoeuvre is finished, a pick up request is made. The test ends when the vehicle has been parked in the pick up area and the app informs the user.</p> <p><strong>Session description:</strong></p> <p>Human factor tests performed at Praza do Rei parking in Vigo.&nbsp;It is an enclosed area with no GPS coverage, so a LIDAR indoor positioning system is used.</p> <p><strong>Datasets descriptions:</strong><br> <br> <strong>AUTOPILOT_Vigo_UrbanDriving_Vehicle:&nbsp;</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:&nbsp;</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:&nbsp;</strong>Data extracted from the CAN of the vehicle.&nbsp;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:&nbsp;</strong>Data extracted from the&nbsp;sensors of the vehicle in absolute coordinates.</p> <p><strong>AUTOPILOT_Vigo_UrbanDriving__EnviromentSensorsRelative:&nbsp;</strong>Data extracted from the&nbsp;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 and the IoT server that contains the Parking Service.</p> <p>&nbsp;</p>

opencc-by-4.0Jan 2020View details →
zenodo32/100

Brainport, Automated valet parking, RS camera object detection

<p><strong>Scenario description</strong>:</p> <p>RS Camera object detection and publication of the iot message from type AutoPilot.ObjectDetection to the PMS via IoT platforms</p> <p><strong>Session description</strong>:</p> <p>A car drive on the AVP road segment and stop and the RS camera detect the car as obstacle and send the obstacle information to the PMS for free obstacle route calculation for AD-car</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
zenodo32/100

Brainport, Automated valet parking, parking spot detected by drone

<p><strong>Scenario description</strong>:</p> <p>The drone receives AVP command message (Message type AutoPilot.DroneAVPCommand) from PMS via the IBM IoT Platfom. The command message contains the instruction about the selected parking spots to be checked. The drone takes off and fly to the corresponding parking spots detects the occupancy (FREE or OCCUPIED) of the parking spot and publishes the message from type AutoPilot.ParkingSpotDetection to the PMS via IBM Watson IoT platform und return to the lading position and landed. During the flight the drone sends continuously the message about it current position and some status information as message from type AutoPilot.PositionEstimate to the PMS via IoT Platform.</p> <p><strong>Session description</strong>:</p> <p>Selection of one free parking spot to be check (see command message contain), the drone detects the parking spot and publish the occupancy information to the PMS for parking management purpose</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
zenodo32/100

Brainport, Automated valet parking, pickup scenario with DLR vehicle

<p><strong>Scenario description</strong>:</p> <p>The AD-vehicle receives parking command message (AutoPilot.VehicleCommand) containing the destination pickup spot and the free obstacle route and drives from the parking spot and parks to the destination pickup spot.During the collection process the vehicle send two type of messages (AutoPilot.PositionEstimate and AutoPilot.VehicleAVPStatus)</p> <p><strong>Session description</strong>:</p> <p>The pickup scenario with DLR vehicle. DLR vehicle parks autonomously from the parking spot to the destination pickup spot at the parking area on DLR test site in Brunswick.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_DroneAvpCommand</strong>: Data sent from drone</p> <p>Dataset Description This dataset contains route information for a vehicle to a designated parking spot</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_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_AutomatedValetParking_ParkingSpotDetection</strong>: Data sent from drone to parkingService</p> <p>Dataset Description This dataset contains informaton about detected parking spots</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_PositioningSystemResampled</strong>: Data from GPS on the vehicle</p> <p>Dataset Description This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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_AutomatedValetParking_VehicleAvpCommand</strong>: Data sent from ParkingService to vehicle</p> <p>Dataset Description This dataset contains route to parkingspot, and some other environmental information</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_VehicleAvpStatus</strong>: Data sent from vehicle to ParkingService</p> <p>Dataset Description This dataset contains information about the current status and parkingstatus of the vehicle</p> <p><strong>AUTOPILOT_BrainPort_AutomatedValetParking_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>

opencc-by-4.0Jan 2020View details →
dryad28/100

Automated vehicles and central business district parking: the effects of drop-off-travel on traffic flow and vehicle emissions

Open the record for dataset details and reuse information.

publicMar 2020View details →

ScienceDex guides

Understand access before you commit

These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.

Compare curated 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.

allen-brain-atlas
neuroscienceopenDocumentation, web resources, and API references are available online.
Last verified 2026-04-30Open record

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.

abode-home-cage
behavioral-neuroscienceopenThe DataShare record exposes download links for annotations, documentation, license text, and the zipped per-snippet data directory.
Last verified 2026-04-30Open record

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.

dandi-nwb
electrophysiologyopenPublished Dandiset metadata and archive endpoints are available through the production DANDI API.
Last verified 2026-04-30Open record

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.

ibl
behavioral-neuroscienceopenPublic sessions can be searched and loaded from the IBL public data server through ONE.
Last verified 2026-04-29Open record

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.

openneuro
neuroscienceopenPublished datasets are available on demand over the internet.
Last verified 2026-04-29Open record