Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “light-duty”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 127 records · Page 7

Atlanta—1991 Household Interview Survey

The Atlanta Regional Commission conducted a Household Travel Survey in 1991 to capture the reality of the locale, including infrastructure improvements—such as new highways, rail, and housing developments—additional households, income, trip chaining, and telecommuting, as well as other typical demographic characteristics. The survey collected demographic, socioeconomic, and travel information on work and non-work travel behavior. Travel data includes trip generation, trip distribution, and modal choice for 3,626 households that completed a travel log.

1Hz data↗

1993 Baltimore Household Travel Survey

The 1993 Baltimore Household Travel Survey is a detailed survey of demographic characteristics and travel patterns for 2,692 households in Baltimore, Maryland. The original goal of the survey was to collect an “ideal” dataset for disaggregate travel demand analysis.

1Hz data↗

1991 California Statewide Travel Survey

The California Statewide Travel Survey was conducted in 1991. Data were collected from 17,040 households throughout the state, with a minimum of 500 samples in any one region. The survey was primarily used to update trip generation rates.

1Hz data↗

1998 Dallas-Fort Worth Travel Survey

The 1998 Dallas-Fort Worth House Travel Survey accomplished two main goals: updating existing data for the North Central Texas Council of Governments regional travel demand models and providing new data to permit the models to be upgraded. The survey encompassed households within the Consolidated Metropolitan Statistical Area of Dallas-Fort Worth. A total of 4,641 households provided complete information. The survey revealed households' travel behavior preference with the collection of information about household characteristics and travel using a unique "travel as an activity" approach.

1Hz data↗

1999 Dallas-Fort Worth Travel Survey

The 1999 Dallas-Fort Worth House Travel Survey accomplished two main goals: updating the existing data for the North Central Texas Council of Governments regional travel demand models and providing new data to permit the models to be upgraded. The survey encompassed households within the Consolidated Metropolitan Statistical Area of Dallas-Fort Worth. A total of 4,641 households provided complete information. The survey revealed households' travel behavior preference with the collection of information about household characteristics and travel using a unique "travel as an activity" approach.

1Hz data↗

2000 Evansville Household Travel Survey

The Evansville Metropolitan Planning Organization conducted a household travel survey in 2000. This study aimed to produce a detailed analysis of travel behavior for the residents of the Evansville Metropolitan Area. The survey contains data from 1,737 participating households. From participants' travel records, a total of 20,096 trips were reported by 4,069 people for a 24-hour period.

1Hz data↗

1996 Tampa Bay Regional Travel Survey

This study was conducted on behalf of the Florida Department of Transportation. The purpose of the survey was to understand day-to-day travel across the Tampa Bay region. Demographic, socioeconomic, and travel data were gathered from 5,349 households that participated in the study, and a total of 31,465 trips were recorded.

1Hz data↗

1993 Tucson Household Travel Survey

The Arizona Department of Transportation (ADOT) conducted a Tucson Household Travel Survey in 1993. ADOT conducts such surveys every five to seven years, providing an essential snapshot of transportation behaviors and trends by asking how members of a household get around on a single day. The answers helped state, local, and federal officials decide when, where, and how to invest limited transportation funding to improve roads, public transportation, sidewalks, bike paths, and more. Demographic, socioeconomic, and travel information was gathered from 4,564 participants associated with 1,913 households. Participants received travel logs to record where members of their household went on an assigned travel day.

1Hz data↗

2000 Tucson Household Travel Survey

The Arizona Department of Transportation (ADOT) conducted a Tucson Household Travel Survey in 2000. ADOT conducts such surveys every five to seven years, providing an essential snapshot of transportation behaviors and trends by asking how members of a household get around on a single day. The answers helped state, local, and federal officials decide when, where, and how to invest limited transportation funding to improve roads, public transportation, sidewalks, bike paths, and more. Demographic, socioeconomic, and travel information was gathered from 4,882 participants associated with 2,076 households. Participants received travel logs to record where members of their household went on an assigned travel day.

1Hz data↗

1970 Home Interview Survey

The 1970 Home Interview Survey was conducted by Twin Cities Metropolitan Council, Saint Paul. This database was used to develop mathematical models to predict future regional travel patterns, which were used to develop appropriate regional transportation policies, plans, and programs. The 1970 survey did not specifically include walking or bicycling as options in the travel diary; instead, these trips are included in a broad “other” category.

1Hz data↗

EV Watts Public Database

With the rapid increase in vehicle electrification, there is a need for up-to-date, publicly available national data to understand end user charging and driving patterns, as well as vehicle and infrastructure performance, to inform research planning. Energetics worked with various partners to collect and analyze plug-in electric vehicle (PEV) and electric vehicle supply equipment (EVSE) data from 2019 to 2022. All sensitive attributes have been removed from this publicly available dataset. Researchers from one of the partner national labs under non-disclosure agreement (NDA) can request access to additional attributes by reaching out to evwattsdata@energetics.com.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

DOE EV Data Collection - Vehicle Data

Vehicle data consist of electric vehicle performance data collected directly from the vehicle during standard operations. Data were collected using onboard data loggers that were either installed by the project team or preinstalled by the original equipment manufacturer. Data recorded by the data loggers were made accessible via an online web portal or an application programming interface. Different data loggers were used (HEM, ViriCiti, and Geotab), and the method for each vehicle is defined in the vehicle attributes file. Some systems collected data on a “trip-level” basis, in which each row of a table represents a single trip (the period between a key-on and key-off event), whereas other data were collected on a per-day basis, in which each row represents a single day of operation. Data were collected over a range of data collection periods, depending on the project. Data have been anonymized by removing information or decreasing information resolution as necessary so that fleets are not identifiable. Due to the wide range of vehicle types represented and variation in data collection, data parameters and frequencies differ between vehicles and fleets The **Performance Data Daily/Trip Data Dictionaries** contain definitions for each available parameter associated with a vehicle’s operations, aggregated at either a daily or trip level. The parameters available will vary from vehicle to vehicle, but every possible parameter will be defined. The **Vehicle Attributes Data Dictionary** contains definitions for each available parameter associated with a vehicle’s physical and functional attributes and fleet context. The **Vehicle Attributes** table contains specific vehicle characteristics, coded to an anonymous Vehicle ID. This Vehicle ID can be used as a key between vehicle data and vehicle attribute tables. The **Vehicle Data** tables contain the data from each vehicle’s operations, aggregated at either a daily or trip level, coded to an anonymous Vehicle ID. This Vehicle ID can be used as a key between vehicle data and vehicle attribute tables. Data is being uploaded quarterly through 2023 and subject to change until the conclusion of the project.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

DOE EV Data Collection - Maintenance Data

Maintenance data includes information on maintenance performed on the electric vehicles, including preventive maintenance, service calls, and availability of the vehicles. The parameters collected, and their definitions, will vary due to the differences in maintenance tracking systems that exist between fleets. Parameter definitions are detailed in the data dictionary, and specific vehicle information is available in the vehicle attributes table. Vehicle ID can be used as a key between maintenance data and vehicle attribute tables. Data is being uploaded quarterly through 2023 and subject to change until the conclusion of the project.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

DOE EV Data Collection - Charging Data

Charging data are collected from one of three sources, each with varying levels of additional information. These sources, in approximate order from most to least additional information, are: • The electric vehicle supply equipment (charger) • Onboard the vehicle itself • From a utility submeter. Many chargers provide software that allows for the collection and reporting of charging session data. If unavailable, data may be recorded by the charging vehicle’s onboard systems. If neither of these options is available, data can be acquired from utility submeters that simply track the energy flowing to one or more chargers. Data collected directly from the electric vehicle supply equipment (EVSE) are typically the most accurate and highest frequency. However, it is not always possible to discern which exact vehicle is being charged during any one session. EVSE-side data can be identified where a single charger ID but a range of vehicle IDs are present (e.g., CH001, EV001-EV005). Data collected from the vehicle’s onboard systems usually does not provide information on which exact charger is being used. Vehicle-side data can be identified where a single Vehicle ID but a range of Charger IDs are present (e.g., EV001, CH001-CH005). Data collected from utility submeters provide no information on which specific vehicle is charging or which specific charger is in use. Submeter data can be identified where multiple Vehicle IDs and multiple Charger IDs are present, but only a single Fleet ID is present (e.g., EV001-EV005, CH001-CH005, Fleet01). The **Charge Data Daily/Session Dictionaries** contains definitions for each available parameter collected as part of an individual charging session, aggregated at either a daily or session level. The parameters available will vary between vehicles and chargers. The **Charger Attributes** table contains specific charger characteristics, coded to at least one anonymous Charger ID and linked to either a single or a range of Vehicle IDs. Vehicle ID can be used as a key between charging data and vehicle attribute tables. The **Charger Attributes Data Dictionary** contains definitions for each available parameter collected on the physical and operational characteristics of the charging hardware itself. The **Vehicle Attributes Data Dictionary** contains definitions for each available parameter associated with a vehicle’s physical and functional attributes and fleet context. The **Vehicle Attributes** table contains specific vehicle characteristics, coded to an anonymous Vehicle ID. This Vehicle ID can be used as a key between vehicle data and vehicle attribute tables, and in cases where charging data are supplied, links a vehicle with the charger(s) that supplied it power. The **Charging Data** tables contain the data from each charger’s operations, coded to at least one anonymous Charger ID and linked to either a single or a range of Vehicle IDs. Vehicle ID can be used as a key between charging data and vehicle attribute tables. Data is being uploaded quarterly through 2023 and subject to change until the conclusion of the project.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

DOE EV Data Collection - Facility Data

Facility data includes information on electricity consumption by larger-scale infrastructure, including buildings, solar arrays, and energy storage systems. Parameter definitions can be found in the data dictionary. If a connection between specific vehicle information and facility data exists, it will be available in the vehicle attributes table. Vehicle ID can be used as a key between vehicle data and vehicle attribute tables. Data is being uploaded quarterly through 2023 and subject to change until the conclusion of the project.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw Lidar and Camera Data Synchronized with Precipitation and Present Weather Data

As part of the sensor characterization task of the SMART 2.0 project, this dataset includes raw data from three spinning lidars ([Ouster OS2-128](https://ouster.com/products/scanning-lidar/os2-sensor/), [Velodyne Puck (VLP-16)](https://velodynelidar.com/products/puck/), and [Velodyne Ultra Puck (VLP-32)](https://velodynelidar.com/products/ultra-puck/)), one camera ([Mako G-319](https://www.alliedvision.com/en/camera-selector/detail/mako/g-319/)), and one present weather sensor ([Vaisala FD-70](https://www.vaisala.com/en/products/weather-environmental-sensors/forward-scatter-fd70)). All data were synchronized, with the log start time indicated in the file name (HHMMSS). The data can be filtered by date, log time (HHMMSS), sensor, frame ID, and weather classification. These data were gathered statically at the Argonne Testbed for Multiscale Observational Science (ATMOS). Two target stop signs were placed in view of the sensors to contribute a target for comparing sensor data under different conditions. The weather data for each day are stored in netCDF “.nc” files. The lidar data contain the X, Y, Z, intensity, reflectivity, and ring from Ouster OS2-128 rev6, Velodyne VLP-16, and Velodyne VLP-32 lidars. ![raw lidar image](LiDAR_pointcloud_ATMOS.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Individual Motorist Data - Ohio EV Ownership Trends

The individual motorist dataset contains data and analysis of consumer electric vehicle (EV) ownership trends in rural Appalachian Ohio in comparison with statewide trends. The data span four years, from Q1 2020 to Q2 2023 (partial). They are sourced from the Ohio Bureau of Motor Vehicles registration records and contain detail on drivetrain type (battery-electric vehicle [BEV] or plug-in hybrid electric vehicle [PHEV]); specific vehicle make and model; and registration location at county, city, and ZIP code levels of spatial resolution. Registration data are analyzed at the county level against such indicators as median income, poverty status, urban-rural status, and density of public charging infrastructure. In addition to tabular data, a GIS shapefile with many analysis fields joined is included.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Raw_data_Batch_I: Argonne to Shorewood via I-55

Date of collection: May 12, 2023 Location: Interstate 55, DuPage County, IL This data set contains lidar and vision data collected along a round trip between I-55 Exit 273A and Exit 253. The data contains the following Robot Operating System (ROS) topics: - /Central_Camera_blurred – Image flow from coaxial camera heading, vehicle front. - /Left_Camera_blurred – Image flow from left camera, 60° from central camera on the left side. - /Right_Camera_blurred – Image flow from right camera, 60° from central camera on the right side. - /camera0/camera_info – Intrinsic and distortion information of left camera. - /camera0/projection_matrix – Extrinsic matrix of left camera from lidar. - /camera2/camera_info – Intrinsic and distortion information of central camera. - /camera2/projection_matrix – Extrinsic matrix of central camera from lidar. - /camera5/camera_info – Intrinsic and distortion information of right camera. - /camera5/projection_matrix – Extrinsic matrix of right camera from lidar. - /novatel/oem7/bestpos – Latitude, longitude, and elevation information from NovAtel GNSS-INS system. - /points_raw – VLP-32 lidar point cloud. - /tf – Vehicle base frame. The data are organized into a data description file and one or more ROS .bag files, dependent on original file size. The data description file provides information about the data collection date, location, and detailed mapping, while the .bag file(s) contain the actual data. Please note that for the purpose of securing personally identifiable information, all license plates and faces included in this publication have been intentionally blurred during real-time processing. ![argonne shorewood image](argone-shorewood.png)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗