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.

9

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

9 results for “Car Detection”

Learn how ShareScore rates datasets ↗
zenodo40/100

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 --&gt; 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>

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

Brainport, Highway pilot, car in manual mode, camera detection

<p><strong>Scenario description</strong>:</p> <p>The detection car drives around the track in manual mode, with Camera detection ON.</p> <p><strong>Session description</strong>:</p> <p>25 laps with VW Tiguan on Automotive Campus Test Track</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_AdasCommand</strong>: Data from the automated driver assistance system</p> <p>Dataset Description This dataset contains the ADAS command in the vehicle</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_Anomaly</strong>: Data sent from detecting vehicle to the service, and from service to vehicles</p> <p>Dataset Description This dataset contains information about all the detected anomalies on the road</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_AnomalyImage</strong>: Data sent from detecting vehicle to service</p> <p>Dataset Description This dataset contains images of the detected anomalies</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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_HighwayPilot_Hazard</strong>: Data sent from service to vehicle</p> <p>Dataset Description This dataset contains specific information for a vehicle about anomalies and hazards</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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, Highway pilot, car in manual mode, IMU detection

<p><strong>Scenario description</strong>:</p> <p>The detection car drives around the track in manual mode, with IMU detection ON.</p> <p><strong>Session description</strong>:</p> <p>25 laps with VW Tiguan on Automotive Campus Test Track</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_AdasCommand</strong>: Data from the automated driver assistance system</p> <p>Dataset Description This dataset contains the ADAS command in the vehicle</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_Anomaly</strong>: Data sent from detecting vehicle to the service, and from service to vehicles</p> <p>Dataset Description This dataset contains information about all the detected anomalies on the road</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_AnomalyImage</strong>: Data sent from detecting vehicle to service</p> <p>Dataset Description This dataset contains images of the detected anomalies</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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_HighwayPilot_Hazard</strong>: Data sent from service to vehicle</p> <p>Dataset Description This dataset contains specific information for a vehicle about anomalies and hazards</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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, Highway pilot, detection car reference laps

<p><strong>Scenario description</strong>:</p> <p>The detection car drives around the track in manual mode, at an average speed close to laps for detections, but with all detections systems disabled.</p> <p><strong>Session description</strong>:</p> <p>25 laps with VW Tiguan on Automotive Campus Test Track</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_AdasCommand</strong>: Data from the automated driver assistance system</p> <p>Dataset Description This dataset contains the ADAS command in the vehicle</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_Anomaly</strong>: Data sent from detecting vehicle to the service, and from service to vehicles</p> <p>Dataset Description This dataset contains information about all the detected anomalies on the road</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_AnomalyImage</strong>: Data sent from detecting vehicle to service</p> <p>Dataset Description This dataset contains images of the detected anomalies</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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_HighwayPilot_Hazard</strong>: Data sent from service to vehicle</p> <p>Dataset Description This dataset contains specific information for a vehicle about anomalies and hazards</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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, Highway pilot, detection car, manual mode, camera and IMU detection on

<p><strong>Scenario description</strong>:</p> <p>The detection car drives around the track in manual mode, with Camera and IMU detection ON.</p> <p><strong>Session description</strong>:</p> <p>25 laps with VW Tiguan on Automotive Campus Test Track</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_AdasCommand</strong>: Data from the automated driver assistance system</p> <p>Dataset Description This dataset contains the ADAS command in the vehicle</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_Anomaly</strong>: Data sent from detecting vehicle to the service, and from service to vehicles</p> <p>Dataset Description This dataset contains information about all the detected anomalies on the road</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_AnomalyImage</strong>: Data sent from detecting vehicle to service</p> <p>Dataset Description This dataset contains images of the detected anomalies</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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_HighwayPilot_Hazard</strong>: Data sent from service to vehicle</p> <p>Dataset Description This dataset contains specific information for a vehicle about anomalies and hazards</p> <p><strong>AUTOPILOT_BrainPort_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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_HighwayPilot_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 →
dryad36/100

Detecting flying insects using car nets and DNA metabarcoding

Open the record for dataset details and reuse information.

publicMar 2021View details →
zenodo32/100

Livorno, Urban driving, Automated car detects pothole

<p><strong>Scenario description</strong>:</p> <p>Test session for connected car detecting potholes using the combination of one or more of the following sensors: smartphone, 6LoWPAN vibration sensor, IMU.<br> The information is sent to the cloud and can be sent back to other connected vehicles for warning.<br> The information is also transmitted via V2V to AD cars that can automatically adapt the speed.</p> <p><strong>Session description</strong>:</p> <p>Test session with only a connected car with smartphone based pothole detector, lap of 1,9 km on the harbour&#39;s public road. Goal is to record data for the technical evaluation.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_Livorno_UrbanDriving_Vehicle_all</strong>: Data generated from the vehicle sensors</p> <p>This dataset refers to the vehicle datasets generated from the vehicle sensors during Urban Driving in Livorno. This includes the data coming from the CAN bus and GPS. It includes following kind of dataset: Vehicle: general data (speed, battery); PositioningSystem: data from GPS; VehicleDynamics: data about dynamic (acceleration...); LateralControl: steering and lane control data</p> <p><strong>AUTOPILOT_Livorno_UrbanDriving_V2X_all</strong>: V2V messages during platooning sessions</p> <p>This dataset refers to the V2V messages exchanged between ITS stations (vehicles and RSUs) during the Urban Drining in Livorno.</p> <p><strong>AUTOPILOT_Livorno_UrbanDriving_IoT_all</strong>: Data extracted from IoT oneM2M platform</p> <p>This dataset refers to messages exchanged by Urban Driving devices, applications and services across the oneM2M platform.</p>

opencc-by-4.0Jan 2020View details →
ClinicalTrials.gov24/100

ePRO for the Timely Detection of Side Effects in Cancer Patients Undergoing CAR T Immunotherapy

ClinicalTrials.gov study NCT05354973. IPD Sharing: NO. Countries: 1. Publications: 0.

closedIPD-NOFeb 2026View details →
zenodo4/100

Car Position Detection (CPD)

<p>Car Position Detection</p>

restrictedAug 2023View 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