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.
1,832
datasets available to search
ShareScore release 0.9.0
Dataset results
1,832 results for “Cameras”
Wildlife along the Salt River corridor of the greater Phoenix, Arizona, USA metropolitan area: results of a camera-trapping project (2020-2021)
The goal of this research project was to evaluate how wildlife populations responded to the gradient of urbanization, water, and vegetation. We deployed 43 wildlife cameras across the gradient of urbanization January 2021 to January 2022. We documented a suite of wildlife species, from small mammals and birds to large mammals. Data present whether a species was detected at a site during this time period.
Chimney Pole Marsh Erosion-Camera Images and Video 2009-2012
This data consists of a time series of image and video files showing erosion at the western edge of Chimney Pole Marsh, in Northampton Co. Virginia. Images depict the edge of a salt marsh as it erodes. Images and videos have a time stamp (YYYYmmdd_HHMMss) embedded in their file name and also in the upper left of the images themselves. All dates and times are in Eastern Standard Time. Images and videos are taken once ever 30 minutes at 25 and 55 minutes after the hour. Still image JPEG (.jpg) files are 1600x1200 pixels in size. Videos are encoded as MPEG-4 (.mp4) files with a resolution of 400x304 at 8.05 frames per second. They were collected by a 2 mega-pixel Vivotek IP7161 security camera attached to a post (approximately 3-m above the marsh surface). The camera was removed when the marsh was sufficiently eroded that the camera platform was imperiled. There are some gaps in the data caused by network and electrical problems.
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 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>
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, baseline test, camera detection
<p><strong>Scenario description</strong>:</p> <p>Base line test: no CEMA, no GeoFencing enabled. Vehicle only brakes on camera detection, when vehicle is blocked on its route by a crowd</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, 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>
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>
Brainport, Highway pilot, road side camera detection
<p><strong>Scenario description</strong>:</p> <p>The road side camera detects objects (obstacle) on the test track and publishes the ANO IoT message.</p> <p><strong>Session description</strong>:</p> <p>10 minute observation of a section of the 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>
Phenological time lapse images from landscape camera MC117-1 in Paljakka Spruce stand
<p>This record contains phenological time lapse images from camera Paljakka Spruce stand. Camera was mounted at landscape view level at location 64.677381;28.114014(N;E, WGS84).</p> <p>First set of images were taken between 02.11.2016--31.12.2016 (Version 1). Subsequent Versions extend the record with newer images, and the version number indicates the years covered by the record.<br> Cameras were set to fix white balance, brightness automatically adjusted by camera.Image have equal resolution throughout the time series, time indicated in UTC+2. Images are taken half-hourly during fixed day-time period over the year. Gaps in time series and dark images possibly exist.<br> More details on the camera installations and operation history can be found at doi 10.5281/zenodo.777952<br> The cameras were set up and images collected under EU Life+ (LIFE ENV/FI/000409) Monimet project, http://monimet.fmi.fi.<br> For further information contact Mikko Peltoniemi (mikko.peltoniemi@luke.fi)</p>
Phenological time lapse images from ground camera MC103 in Punkaharju Spruce stand
<p>This record contains phenological time lapse images from camera Punkaharju Spruce stand. Camera was mounted at ground view level at location 61.81364556; 29.31993611(N;E, WGS84).</p> <p>First set of images were taken between 17.06.2014--31.12.2016 (Version 1). Subsequent Versions extend the record with newer images, and the version number indicates the years covered by the record.<br> Cameras were set to fix white balance, brightness automatically adjusted by camera.Image have equal resolution throughout the time series, time indicated in UTC+2. Images are taken half-hourly during fixed day-time period over the year. Gaps in time series and dark images possibly exist.<br> More details on the camera installations and operation history can be found at 10.5281/zenodo.777952<br> The cameras were set up and images collected under EU Life+ (LIFE ENV/FI/000409) Monimet project, http://monimet.fmi.fi.<br> For further information contact Mikko Peltoniemi (mikko.peltoniemi@luke.fi)</p>
[Dataset] Spatial and temporal variability of the 365-nm albedo of Venus observed by the camera on board Venus Express
<p>This is the derived data, presented in a publication entitled "Spatial and temporal variability of the 365-nm albedo of Venus observed by the camera on board Venus Express" (JGR:Planet, doi: 10.1029/2019JE006271). See the paper for details. See 'Readme.txt' for the file descriptions.</p>
DoeDat Camera Trap Project 3837482 (Meise Botanic Garden)
A project on the <a href="https://www.doedat.be">DoeDat platform</a> of <a href="https://www.plantentuinmeise.be">Meise Botanic Garden</a>. Footage of camera traps is offered to volunteers for identification of the animals visible, if any. This deposition is an archive of the images in this project as well as the transcription results formatted in Darwin Core.
DoeDat Camera Trap Project 3954058 (Meise Botanic Garden)
A project on the <a href="https://www.doedat.be">DoeDat platform</a> of <a href="https://www.plantentuinmeise.be">Meise Botanic Garden</a>. Footage of camera traps is offered to volunteers for identification of the animals visible, if any. This deposition is an archive of the images in this project as well as the transcription results formatted in Darwin Core.
DoeDat Camera Trap Project 3818147 (Meise Botanic Garden)
A project on the <a href="https://www.doedat.be">DoeDat platform</a> of <a href="https://www.plantentuinmeise.be">Meise Botanic Garden</a>. Footage of camera traps is offered to volunteers for identification of the animals visible, if any. This deposition is an archive of the images in this project as well as the transcription results formatted in Darwin Core.
DoeDat Camera Trap Project 3954595 (Meise Botanic Garden)
A project on the <a href="https://www.doedat.be">DoeDat platform</a> of <a href="https://www.plantentuinmeise.be">Meise Botanic Garden</a>. Footage of camera traps is offered to volunteers for identification of the animals visible, if any. This deposition is an archive of the images in this project as well as the transcription results formatted in Darwin Core.
DoeDat Camera Trap Project 3340887 (Meise Botanic Garden)
A project on the <a href="https://www.doedat.be">DoeDat platform</a> of <a href="https://www.plantentuinmeise.be">Meise Botanic Garden</a>. Footage of camera traps is offered to volunteers for identification of the animals visible, if any. This deposition is an archive of the images in this project as well as the transcription results formatted in Darwin Core.
DoeDat Camera Trap Project 2103830 (Meise Botanic Garden)
A project on the <a href="https://www.doedat.be">DoeDat platform</a> of <a href="https://www.plantentuinmeise.be">Meise Botanic Garden</a>. Footage of camera traps is offered to volunteers for identification of the animals visible, if any. This deposition is an archive of the images in this project as well as the transcription results formatted in Darwin Core.
DoeDat Camera Trap Project 2174037 (Meise Botanic Garden)
A project on the <a href="https://www.doedat.be">DoeDat platform</a> of <a href="https://www.plantentuinmeise.be">Meise Botanic Garden</a>. Footage of camera traps is offered to volunteers for identification of the animals visible, if any. This deposition is an archive of the images in this project as well as the transcription results formatted in Darwin Core.
DoeDat Camera Trap Project 1062394 (Meise Botanic Garden)
A project on the <a href="https://www.doedat.be">DoeDat platform</a> of <a href="https://www.plantentuinmeise.be">Meise Botanic Garden</a>. Footage of camera traps is offered to volunteers for identification of the animals visible, if any. This deposition is an archive of the images in this project as well as the transcription results formatted in Darwin Core.
DoeDat Camera Trap Project 4035235 (Meise Botanic Garden)
A project on the <a href="https://www.doedat.be">DoeDat platform</a> of <a href="https://www.plantentuinmeise.be">Meise Botanic Garden</a>. Footage of camera traps is offered to volunteers for identification of the animals visible, if any. This deposition is an archive of the images in this project as well as the transcription results formatted in Darwin Core.
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.