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.
10
datasets available to search
ShareScore release 0.9.0
Dataset results
10 results for “electric cars”
Open synthetic data on travel and charging demand of battery electric cars: An agent-based simulation on three charging behavior archetypes
<p><strong>Background</strong></p> <p>Battery electric vehicles (BEVs) are crucial for a sustainable transportation system. As more people adopt BEVs, it becomes increasingly important to accurately assess the demand for charging infrastructure. However, much of the current research on charging infrastructure relies on outdated assumptions, such as the assumption that all BEV owners have access to home chargers and the "Liquid-fuel" mental model. To address this issue, we simulate the travel and charging demand on three charging behavior archetypes. We use a large synthetic population of Sweden, including detailed individual characteristics, such as dwelling types (detached house vs. apartment) and activity plans (for an average weekday). This data repository aims to provide the BEV simulation's input, assumptions, and output so that other studies can use them to study sizing and location design of charging infrastructure, grid impact, etc.</p> <p>A journal paper published in Transportation Research Part D: Transport and Environment details the method to create the data (particularly Section 2.2 BEV simulation).</p> <p><a href="https://doi.org/10.1016/j.trd.2023.103645">https://doi.org/10.1016/j.trd.2023.103645</a></p> <p><strong>Methodology</strong></p> <p>This data product is centered on the 1.7 million inhabitants of the Västra Götaland (VG) region, which includes the second largest city in Sweden, Gothenburg. We specifically simulated 284,000 car agents who live in VG, representing 35% of all car users and 18% of the total population in the region. They spend their simulation day (representing an average weekday) in a variety of locations throughout Sweden.</p> <p>This open data repository contains the core model inputs and outputs. The numbers in parentheses correspond to the data sets. We use individual agents' activity plans (1) and travel trajectories from MATSim simulation for the BEV simulation (2), in which we consider overnight charger access (3), car fleet composition referencing the current private car fleet in Sweden (4), and Swedish road network with slope information (5) with realistic BEV charging & discharging dynamics. For the BEV simulation, we tested ten scenarios of charging behavior archetypes and fast charging powers (6). The output includes the time history of travel trajectories and charging of the simulated BEVs across the different scenarios (7).</p> <p><strong>Data description</strong></p> <p>The current data product covers seven data files.</p> <p><strong>(1) Agents' experienced activity plans</strong></p> <p>File name: 1_activity_plans.csv</p> <table> <tbody> <tr> <td> <p><strong>Column</strong></p> </td> <td> <p><strong>Description</strong></p> </td> <td> <p><strong>Data type</strong></p> </td> <td> <p><strong>Unit</strong></p> </td> </tr> <tr> <td> <p>person</p> </td> <td> <p>Agent ID</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>act_id</p> </td> <td> <p>Activity index of each agent</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>deso</p> </td> <td> <p>Zone code of Demographic statistical areas (DeSO)<sup>1</sup></p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>POINT_X</p> </td> <td> <p>Coordinate X of activity location (SWEREF99TM)</p> </td> <td> <p>Float</p> </td> <td> <p>meter</p> </td> </tr> <tr> <td> <p>POINT_Y</p> </td> <td> <p>Coordinate Y of activity location (SWEREF99TM)</p> </td> <td> <p>Float</p> </td> <td> <p>meter</p> </td> </tr> <tr> <td> <p>act_purpose</p> </td> <td> <p>Activity purpose (work, home, other)</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>mode</p> </td> <td> <p>Transport mode to reach the activity location (car)</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>dep_time</p> </td> <td> <p>Departure time in decimal hour (0-23.99)</p> </td> <td> <p>Float</p> </td> <td> <p>hour</p> </td> </tr> <tr> <td> <p>trav_time</p> </td> <td> <p>Travel time to reach the activity location</p> </td> <td> <p>String</p> </td> <td> <p>hour:minute:second</p> </td> </tr> <tr> <td> <p>trav_time_min</p> </td> <td> <p>Travel time in decimal minute</p> </td> <td> <p>Float</p> </td> <td> <p>minute</p> </td> </tr> <tr> <td> <p>speed</p> </td> <td> <p>Travel speed to reach the activity location</p> </td> <td> <p>Float</p> </td> <td> <p>km/h</p> </td> </tr> <tr> <td> <p>distance</p> </td> <td> <p>Travel distance between the origin and the destination</p> </td> <td> <p>Float</p> </td> <td> <p>km</p> </td> </tr> <tr> <td> <p>act_start</p> </td> <td> <p>Start time of activity in minute (0-1439)</p> </td> <td> <p>Integer</p> </td> <td> <p>minute</p> </td> </tr> <tr> <td> <p>act_time</p> </td> <td> <p>Activity duration in decimal minute</p> </td> <td> <p>Float</p> </td> <td> <p>minute</p> </td> </tr> <tr> <td> <p>act_end</p> </td> <td> <p>End time of activity in decimal hour (0-23.99)</p> </td> <td> <p>Float</p> </td> <td> <p>hour</p> </td> </tr> <tr> <td> <p>score</p> </td> <td> <p>Utility score of the simulation day given by MATSim</p> </td> <td> <p>Float</p> </td> <td> <p>-</p> </td> </tr> </tbody> </table> <p>1 <a href="https://www.scb.se/vara-tjanster/oppna-data/oppna-geodata/deso--demografiska-statistikomraden/">https://www.scb.se/vara-tjanster/oppna-data/oppna-geodata/deso--demografiska-statistikomraden/</a></p> <p> </p> <p><strong>(2) Travel trajectories</strong></p> <p>File name: 2_input_zip</p> <p>Produced by MATSim simulation, the zip folder contains ten files (events_batch_X.csv.gz, X=1, 2, …, 10) of input events for the BEV simulation. They are the moving trajectories of the car agents in their simulation days.</p> <table> <tbody> <tr> <td> <p><strong>Column</strong></p> </td> <td> <p><strong>Description</strong></p> </td> <td> <p><strong>Data type</strong></p> </td> <td> <p><strong>Unit</strong></p> </td> </tr> <tr> <td> <p>time</p> </td> <td> <p>Time in second in a simulation day (0-86399)</p> </td> <td> <p>Integer</p> </td> <td> <p>Second</p> </td> </tr> <tr> <td> <p>type</p> </td> <td> <p>Event type defined by MATSim simulation<sup>2</sup></p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>person</p> </td> <td> <p>Agent ID</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>link</p> </td> <td> <p>Nearest road link consistent with (5)</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>vehicle</p> </td> <td> <p>Vehicle ID identical to person</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> </tbody> </table> <p><sup>2 </sup>One typical episode of MATSim simulation events: Activity ends (actend) -> Agent’s vehicle enters traffic (vehicle enters traffic) -> Agent’s vehicle moves from previous road segment to its next connected one (left link) -> Agent’s vehicle leaves traffic for activity (vehicle leaves traffic) -> Activity starts (actstart)</p> <p> </p> <p><strong>(3) Overnight charger access</strong></p> <p>File name: 3_home_charger_access.csv</p> <table> <tbody> <tr> <td> <p><strong>Column</strong></p> </td> <td> <p><strong>Description</strong></p> </td> <td> <p><strong>Data type</strong></p> </td> <td> <p><strong>Unit</strong></p> </td> </tr> <tr> <td> <p>person</p> </td> <td> <p>Agent ID</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>home_charger</p> </td> <td> <p>Whether an agent has access to a home garage charger/living in a detached house (0=no, 1=yes)</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> </tbody> </table> <p> </p> <p><strong>(4) Car fleet composition</strong></p> <p>File name: 4_car_fleet.csv</p> <table> <tbody> <tr> <td> <p><strong>Column</strong></p> </td> <td> <p><strong>Description</strong></p> </td> <td> <p><strong>Data type</strong></p> </td> <td> <p><strong>Unit</strong></p> </td> </tr> <tr> <td> <p>person</p> </td> <td> <p>Agent ID</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>income_class</p> </td> <td> <p>Income group (0=None, 1=below 180K, 2=180K-300K, 3=300K-420K, 4=above 420K)</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>car</p> </td> <td> <p>Car model class (B=40 kWh, C=60 kWh, D=100 kWh)</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> </tbody> </table> <p> </p> <p>(<strong>5) Road network with slope information</strong></p> <p>File name: 5_road_network_with_slope.shp (5 files in total)</p> <table> <tbody> <tr> <td> <p>Column</p> </td> <td> <p>Description</p> </td> <td> <p>Data type</p> </td> <td> <p>Unit</p> </td> </tr> <tr> <td> <p>length</p> </td> <td> <p>The length of road link</p> </td> <td> <p>Float</p> </td> <td> <p>meter</p> </td> </tr> <tr> <td> <p>freespeed</p> </td> <td> <p>Free speed</p> </td> <td> <p>Float</p> </td> <td> <p>km/h</p> </td> </tr> <tr> <td> <p>capacity</p> </td> <td> <p>Number of vehicles</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>permlanes</p> </td> <td> <p>Number of lanes</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>oneway</p> </td> <td> <p>Whether the segment is one-way (0=no, 1=yes)</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>modes</p> </td> <td> <p>Transport mode (car)</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>link_id</p> </td> <td> <p>Link ID</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>from_node</p> </td> <td> <p>Start node of the link</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>to_node</p> </td> <td> <p>End node of the link</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>count</p> </td> <td> <p>Aggregated traffic (number of cars travelled per day)</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>slope</p> </td> <td> <p>Slope in percent from -6% to 6%</p> </td> <td> <p>Float</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>geometry</p> </td> <td> <p>LINESTRING (SWEREF99TM)</p> </td> <td> <p>geometry</p> </td> <td> <p>meter</p> </td> </tr> </tbody> </table> <p> </p> <p><strong>(6) Simulation scenarios specifying the parameter sets</strong></p> <p>File name: 6_scenarios.txt</p> <table> <tbody> <tr> <td> <p><strong>Parameter set</strong></p> <p><strong>(paraset)</strong></p> </td> <td> <p><strong>Strategy 1</strong></p> </td> <td> <p><strong>Strategy 2</strong></p> </td> <td> <p><strong>Strategy 3</strong></p> </td> <td> <p><strong>Fast charging power (kW)</strong></p> </td> <td> <p><strong>Minimum parking time for charging (min)</strong></p> </td> <td> <p><strong>Intermediate charging power (kW)</strong></p> </td> </tr> <tr> <td> <p>0</p> </td> <td> <p>0.2</p> </td> <td> <p>0.2</p> </td> <td> <p>0.9</p> </td> <td> <p>150</p> </td> <td> <p>5</p> </td> <td> <p>22</p> </td> </tr> <tr> <td> <p>1</p> </td> <td> <p>0.2</p> </td> <td> <p>0.2</p> </td> <td> <p>0.9</p> </td> <td> <p>50</p> </td> <td> <p>5</p> </td> <td> <p>22</p> </td> </tr> <tr> <td> <p>2</p> </td> <td> <p>0.3</p> </td> <td> <p>0.3</p> </td> <td> <p>0.9</p> </td> <td> <p>150</p> </td> <td> <p>5</p> </td> <td> <p>22</p> </td> </tr> <tr> <td> <p>3</p> </td> <td> <p>0.3</p> </td> <td> <p>0.3</p> </td> <td> <p>0.9</p> </td> <td> <p>50</p> </td> <td> <p>5</p> </td> <td> <p>22</p> </td> </tr> </tbody> </table> <p> </p> <p><strong>(7) Time history of travel trajectories and charging of the simulated BEVs</strong></p> <p>File name: 7_output.zip</p> <p>Produced by the BEV simulation, the zip folder contains four files (parasetX.csv.gz, X=1, 2, 3, 4) corresponding to the four parameter sets specified in (6). They are the moving trajectories of the car agents with simulated energy and charging time history in their simulation days.</p> <table> <tbody> <tr> <td> <p><strong>Column</strong></p> </td> <td> <p><strong>Description</strong></p> </td> <td> <p><strong>Data type</strong></p> </td> <td> <p><strong>Unit</strong></p> </td> </tr> <tr> <td> <p>person</p> </td> <td> <p>Agent ID</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>home_charger</p> </td> <td> <p>Whether an agent has access to a home garage charger/living in a detached house (0=no, 1=yes)</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>car</p> </td> <td> <p>Car model class (B=40 kWh, C=60 kWh, D=100 kWh)</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>seq</p> </td> <td> <p>Sequence ID of time history by agent</p> </td> <td> <p>Integer</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>time</p> </td> <td> <p>Time (0-86399)</p> </td> <td> <p>Integer</p> </td> <td> <p>Second</p> </td> </tr> <tr> <td> <p>purpose</p> </td> <td> <p>Valid for activities (home, work, school, other)</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>type</p> </td> <td> <p>Event type defined by MATSim simulation</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>link</p> </td> <td> <p>Link ID (link_id in File 5)</p> </td> <td> <p>String</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>distance_driven</p> </td> <td> <p>Cumulative driven distance in the simulation day</p> </td> <td> <p>Float</p> </td> <td> <p>km</p> </td> </tr> <tr> <td> <p>energy_1</p> </td> <td> <p>Energy consumed while driving (-) or charging (+) (Strategy 1)</p> </td> <td> <p>Float</p> </td> <td> <p>kWh</p> </td> </tr> <tr> <td> <p>energy_2</p> </td> <td> <p>Energy consumed while driving (-) or charging (+) (Strategy 2)</p> </td> <td> <p>Float</p> </td> <td> <p>kWh</p> </td> </tr> <tr> <td> <p>energy_3</p> </td> <td> <p>Energy consumed while driving (-) or charging (+) (Strategy 3)</p> </td> <td> <p>Float</p> </td> <td> <p>kWh</p> </td> </tr> <tr> <td> <p>charger_1</p> </td> <td> <p>Power rating of the charger (Strategy 1)</p> </td> <td> <p>Float</p> </td> <td> <p>kW</p> </td> </tr> <tr> <td> <p>charger_2</p> </td> <td> <p>Power rating of the charger (Strategy 2)</p> </td> <td> <p>Float</p> </td> <td> <p>kW</p> </td> </tr> <tr> <td> <p>charger_3</p> </td> <td> <p>Power rating of the charger (Strategy 3)</p> </td> <td> <p>Float</p> </td> <td> <p>kW</p> </td> </tr> <tr> <td> <p>soc_1</p> </td> <td> <p>State of charge (0-1, Strategy 1)</p> </td> <td> <p>Float</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>soc_2</p> </td> <td> <p>State of charge (0-1, Strategy 2)</p> </td> <td> <p>Float</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p>soc_3</p> </td> <td> <p>State of charge (0-1, Strategy 3)</p> </td> <td> <p>Float</p> </td> <td> <p>-</p> </td> </tr> </tbody> </table> <p> </p>
Hybrid-electric passenger car energy utilization and emissions: Relationships for real-world driving conditions that account for road grade
<p>Past research showed on-road emissions patterns unique to hybrid electric vehicles (HEVs), indicating the need to account for them in emissions models as projected HEV sales increase over the coming decades. This work defines and characterizes a variable that quantifies HEV operating behavior to inform future development of new HEV emissions models based on current knowledge of conventional vehicle (CV) emissions patterns. Instantaneous hybridization factor (IHF), was quantified using on-road data collected from a 2010 Toyota Camry HEV. IHF is the ratio of electric system power to total system power and accounts for energy storage in the high voltage battery (IHF ranges from −1 to +1). Relationships between IHF and vehicle specific power (VSP), road type and road grade were examined. Negative VSP resulted in regenerative braking operation (IHF = −0.01 to −1) 90% of the time. IHF identified the VSP range where HEV operation was highly variable (VSP = −1 to 8 kW/ton) when driving at speeds below the ICE-off threshold (42 mph). VSP and IHF together account for 76–86% of the variability in HEV CO<sub>2</sub> emissions in this study. CO<sub>2</sub> model results using VSP computed with the measured real-world road grade (R<sup>2</sup> = 0.86) gave improved fits over the no-grade VSP model (R<sup>2</sup> = 0.69). This study establishes one framework for calculating the instantaneous HEV power split, confirms the need to include road grade in VSP for accurate modeling of vehicle emissions, and identified the need for significant improvements in on-board diagnostic (OBD) scantool measurement requirements for HEVs in three areas: (1) temporal resolution (sub-second to capture transient events such as ICE restarts); (2) simultaneous data logging capability for multiple controller area networks (i.e., engine and HEV parameters together); and (3) improved data precision.</p>
Dataset: Electric car parameters over 29 months
<p>This dataset contains the full data acquired over 29 month using a data logger installed on an electric car (Renault Zoe) that can be used for research and simulation for electric vehicle efficiency and charging strategies. Specifically the dates are from 01-01-2019 to 29-05-2021. The data from 01-01-2019 to 19-01-2020 have a sampling frequency per minute while from 20-01-2020 to 29-05-2021 the sampling frequency is per second. The parameters considered are:</p> <p>Date <br> Time <br> Available_Energy (kWh)<br> Consumption (kW)<br> Electric_Engine_RPM (Rpm * 100)<br> Mean_Effective_Torque (Nm)<br> Odometer (km)<br> Speed (km/h)<br> State_Of_Charge_High_Definition (%)<br> Throttle (%)<br> Available_Charging_Power (kW)<br> Charging_Power (kW)<br> Electric_Engine_RPM (Rpm)</p>
Electric car subsidies in social media and parliament 2022–2023: analysis results
<p>Electric car subsidies in social media and the Finnish parliament 2022–2023: comparative analysis results obtained using three methods for qualitative classification of textual data.</p>
Hybrid-electric passenger car energy utilization and emissions: Relationships for real-world driving conditions that account for road grade
Open the record for dataset details and reuse information.
SPARCS-WP3_Espoo_City_Number of electric cars registered in Espoo
<p>Number of fully electric cars that are registered in the Espoo area.</p>
Effectivness of Distraction by Electric ride-on Cars for Peri Operative Anxiety in Ambulatory Pediatric Surgery
ClinicalTrials.gov study NCT03961581. IPD Sharing: Not stated. Countries: 1. Publications: 1.
The Effect of Electric Ride-On Cars Use During Transport to the Operating Theatre
ClinicalTrials.gov study NCT06303843. IPD Sharing: Not stated. Countries: 1. Publications: 0.
SPARCS_WP4_Leipzig_City_Total amount of electric cars
<p>The number of electric cars in the city of Leipzig with annually captured data covering the period between 2016 and 2023.</p>
EMI and CIED: Is High Power Charging of Battery Electric Car Safe?
ClinicalTrials.gov study NCT05361681. IPD Sharing: Not stated. Countries: 1. Publications: 0.
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.