You must agree to the NVIDIA Autonomous Vehicle Dataset License Agreement to access this dataset.

This repository is publicly accessible, but you have to accept the conditions to access its files and content.

NVIDIA Autonomous Vehicle Dataset License Agreement

This NVIDIA Autonomous Vehicle Dataset License Agreement ("Agreement") is a legal agreement between you, whether an individual or entity ("you") and NVIDIA Corporation with address 2788 San Tomas Expressway, Santa Clara, California 95051 ("NVIDIA") and governs the use of certain datasets, including any annotations and metadata attached to the datasets, provided by NVIDIA ("Dataset").

This Agreement can be accepted only by an adult of legal age of majority in the country in which the Dataset are used.

If you don't have the required age or authority to accept this Agreement or if you don't accept all the terms and conditions of this Agreement, do not use the Dataset.

You agree to use the Dataset only for purposes expressly permitted by this Agreement and in accordance with any applicable law or regulation in the relevant jurisdictions.

  1. License Grant. Subject to the terms of this Agreement, NVIDIA grants you a non-exclusive, revocable, non-transferable, non-sublicensable (except as expressly granted in Sections 1 and 2 of this Agreement, license to download, use, modify, and reproduce the Dataset, in each case solely for your internal development of autonomous vehicles and automated driving assisted systems using NVIDIA technology ("Purpose"). NVIDIA may from time to time update the Dataset. If requested by NVIDIA, you will use the updated version of any such Dataset and delete any prior versions upon NVIDIA's written request.

  2. Authorized Users. You may allow your Affiliates' employees and contractors (all such users collectively "Authorized Users") to access and use the Dataset from your secure network for the Purpose on your behalf. You are responsible for the compliance with the terms of this Agreement by your authorized users. Any act or omission by your authorized users that if committed by you would constitute a breach of this Agreement will be deemed to constitute a breach of this Agreement. "Affiliates" means an entity that owns or controls, is owned or controlled by, or is under common ownership or control with you, where "control" is the possession, directly or indirectly, of the power to direct or cause the direction of the management and policies of an entity, whether through ownership of voting securities, by contract or otherwise.

  3. Confidentiality. You agree that you will not use, nor authorize others to use, NVIDIA Confidential Information, other than for the Purpose, and that you will not disclose NVIDIA Confidential Information to any third party, except to Authorized Users under this Agreement that have a need to know such Confidential Information for the Purpose, provided that each such recipient is subject to a written agreement that includes confidentiality obligations consistent with the terms. You will protect the NVIDIA Confidential Information with at least the same degree of care that you use to protect your own similar confidential and proprietary information, but no less than a reasonable degree of care, including any appropriate technical, organizational and contractual measures. "Confidential Information" means the Dataset including its features and functionality, output, and any results of benchmarking or other competitive analysis or regression or performance data relating to the Dataset.

  4. Limitations. Your license to use the Dataset is restricted as follows:

4.1 You will not use the Dataset for the purpose of any surveillance program, service and/or product of public authorities, corporations and/or citizens that monitors the behavior of an individual person or groups of persons in any unethical manner. You will not use the Dataset to directly or indirectly enable law enforcement or any public authority to enforce any rules or regulations including any road traffic laws.

4.2 You may not change or remove copyright or other proprietary notices in the Dataset.

4.3 The rights granted to you in Section 1 and 2 are for the Purpose only. You may not use the Dataset for any other purpose.

4.4 You may not identify or attempt to identify or profile any individual (including by way of license plate numbers) in the Dataset or de-anonymize or attempt to de-anonymize any Dataset. This includes prohibition against processing of license plate numbers for purpose of tracking or collecting data about a vehicle over time and across different frames.

4.5 You may not: (a) infer, measure, detect or otherwise label the race, ethnicity, gender, age or health (or any other sensitive attributes) of individuals in the Dataset, (b) perform biometric processing of the Dataset, (c) analyze faces, gazes, eye movements, gait, or body movements to uniquely identify persons, or (d) use the Dataset to develop or evaluate any identity, emotion recognition technology or social scoring technology.

4.6 You may not create derivative works of the Dataset, sell, rent, sublicense, transfer, distribute, embed, or host the Dataset (in whole or in part), or otherwise make the Dataset (in whole or in part) available to others.

4.7 You may not bypass, disable or circumvent any technical limitation, encryption, security, digital rights management or authentication mechanism relating to the Dataset.

4.8 You must keep track of any copies of the Dataset. You will keep track of where the Dataset or portions of it are stored to ensure these restrictions follow such Dataset.

4.9 While NVIDIA has exercised reasonable efforts to anonymize the Dataset, you must cooperate with NVIDIA to honor any data subject rights where applicable. You will delete the Dataset upon written notice by NVIDIA and you will promptly notify NVIDIA at https://www.nvidia.com/en-us/support/submit-security-vulnerability/ if you notice that any portion of the Dataset is not sufficiently anonymized.

  1. AI Ethics.

5.1 Ethical Use. NVIDIA is committed to safety, trust and transparency in AI development. NVIDIA encourages you to (a) ensure that the product or service you develop, use, offer as a service or distribute meets the legal and ethical requirements of the relevant industry or use case, (b) take reasonable measures to address unintended bias and to mitigate harm to others, including underrepresented or vulnerable groups, and (c) inform users of the nature and limitations of the product or service.

5.2 Prohibited Uses. NVIDIA expressly prohibits the use of its products or services for any purpose in violation of applicable law or regulation, including but not limited to (a) illegal surveillance, (b) illegal collection or processing of biometric information without the consent of the subject where required under applicable law, or (c) illegal harassment, abuse, threatening or bullying of individuals or groups of individuals or intentionally misleading or deceiving others.

  1. Ownership. The Dataset, including all intellectual property rights, is and will remain the sole and exclusive property of NVIDIA or its licensors. Except as expressly granted in this Agreement, (i) NVIDIA reserves all rights, interests and remedies in connection with the Dataset, and (ii) no other license or right is granted to you by implication, estoppel or otherwise.

  2. Feedback. You may, but are not obligated to, provide suggestions, requests, fixes, modifications, enhancements, or other feedback regarding or in connection with your use of the Dataset (collectively, "Feedback"). Feedback, even if designated as confidential by you, will not create any confidentiality obligation for NVIDIA or its affiliates. If you provide Feedback, you hereby grant NVIDIA, its affiliates and its designees a nonexclusive, perpetual, irrevocable, sublicensable, worldwide, royalty-free, fully paid-up and transferable license, under your intellectual property rights, to publicly perform, publicly display, reproduce, use, make, have made, sell, offer for sale, distribute (through multiple tiers of distribution), import, create derivative works of and otherwise commercialize and exploit the Feedback at NVIDIA's discretion.

  3. Term and Termination. This Agreement expires twelve (12) months after the date of initial delivery or download of the Dataset. This Agreement will automatically terminate (a) if you fail to comply with any of the terms in this Agreement or (b) if you commence or participate in any legal proceeding against NVIDIA with respect to the Dataset. Upon termination, you must stop using and destroy all copies of the Dataset. Upon written request, you will certify in writing that you have complied with your commitments under this section. All provisions will survive termination, except for the licenses granted to you.

  4. Disclaimer of Warranties. THE DATASET IS PROVIDED BY NVIDIA AS-IS AND WITH ALL FAULTS. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NVIDIA DISCLAIMS ALL WARRANTIES AND REPRESENTATIONS OF ANY KIND, WHETHER EXPRESS, IMPLIED OR STATUTORY, RELATING TO OR ARISING UNDER THIS AGREEMENT, INCLUDING, WITHOUT LIMITATION, THE WARRANTIES OF TITLE, NONINFRINGEMENT, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, USAGE OF TRADE AND COURSE OF DEALING.

  5. Limitations of Liability. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, WILL NVIDIA BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY TYPE ARISING OUT OF OR AS A RESULT OF THIS AGREEMENT OR THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR LOSSES), EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

  6. Governing Law and Jurisdiction. This Agreement will be governed in all respects by the laws of the United States and the laws of the State of Delaware, without regard to conflict of laws principles or the United Nations Convention on Contracts for the International Sale of Goods. The state and federal courts residing in Santa Clara County, California will have exclusive jurisdiction over any dispute or claim arising out of or related to this Agreement, and the parties irrevocably consent to personal jurisdiction and venue in those courts; except that either party may apply for injunctive remedies or an equivalent type of urgent legal relief in any jurisdiction.

  7. Indemnity. You agree to defend, indemnify and hold harmless NVIDIA and its affiliates, and their respective employees, contractors, agents, officers and directors, from and against any and all claims, damages, obligations, losses, liabilities, costs or debt, fines, restitutions and expenses (including but not limited to attorney's fees and costs incident to establishing the right of indemnification) arising out of or related to your use of the Dataset outside of the scope of this Agreement, or not in compliance with its terms.

  8. General.
    13.1 No Assignment. NVIDIA may assign, delegate or transfer its rights or obligations under this Agreement by any means or operation of law. You may not, without NVIDIA's prior written consent, assign, delegate or transfer any of your rights or obligations under this Agreement by any means or operation of law, and any attempt to do so is null and void.

13.2 No Waiver. No waiver of any term of the Agreement will be deemed a further or continuing waiver of such term or any other term, and NVIDIA's failure to assert any right or provision under the Agreement will not constitute a waiver of such right or provision.

13.3 Trade and Compliance. You agree to with all applicable export, import, trade and economic sanctions laws and regulations, as amended, including without limitation U.S. Export Administration Regulations and Office of Foreign Assets Control regulations. Any violation of such laws by you will void any warranty for the associated products and technologies. You confirm (a) your understanding that export or reexport of certain NVIDIA products or technologies may require a license or other approval from appropriate authorities and (b) that you will not export or reexport any products or technology, directly or indirectly, without first obtaining any required license or other approval from appropriate authorities, (i) to any countries that are subject to any U.S. or local export restrictions (currently including, but not necessarily limited to, Belarus, Cuba, Iran, North Korea, Russia, Syria, the Region of Crimea, Donetsk People's Republic Region and Luhansk People's Republic Region); (ii) to any end-user who it knows or has reason to know will utilize them in the design, development or production of nuclear, chemical or biological weapons, missiles, rocket systems, unmanned air vehicles capable of a maximum range of at least 300 kilometers, regardless of payload, or intended for military end-use, or any weapons of mass destruction; (iii) to any end-user who has been prohibited from participating in the U.S. or local export transactions by any governing authority; or (iv) to any known military or military-intelligence end-user or for any known military or military-intelligence end-use in accordance with U.S. trade compliance laws and regulations..

13.4 Notices. Please direct your legal notices or other correspondence to NVIDIA Corporation, 2788 San Tomas Expressway, Santa Clara, California 95051, United States of America, Attention: Legal Department, with a copy emailed to legalnotices@nvidia.com. If NVIDIA needs to contact you about the Dataset, you consent to receive the notices by email and agree that such notices will satisfy any legal communication requirements.

13.5 Force Majeure. Neither party will be liable during any period where an event or circumstance prevents or delays that party from performing its obligations under this Agreement and that event or circumstance: (i) is not within the reasonable control of that party and is not the result of that party's negligence, and (ii) cannot be overcome or avoided by that party using reasonably diligent efforts.

13.6 Severability and Amendment. If a court of competent jurisdiction rules that a provision of this Agreement is unenforceable, that provision will be deemed modified to the extent necessary to make it enforceable and the remainder of this Agreement will continue in full force and effect. Any amendment to this Agreement must be in writing and signed by authorized representatives of both parties.

13.7 Independent Contractors. The parties are independent contractors, and this Agreement does not create a joint venture, partnership, agency or other form of business association between the parties. Neither party will have the power to bind the other party or incur any obligation on its behalf without the other party's prior written consent.

13.8 Construction. The headings in the Agreement are included solely for convenience and are not intended to affect the meaning or interpretation of the Agreement. As required by the context of the Agreement, the singular of a term includes the plural and vice versa.

13.9 Entire Agreement. Regarding the subject matter of this Agreement, the parties agree that (i) this Agreement constitutes the entire and exclusive agreement between the parties and supersedes all prior and contemporaneous communications and (ii) any additional or different terms or conditions, whether contained in purchase orders, order acknowledgments, invoices or otherwise, will not be binding and are null and void.

Log in or Sign Up to review the conditions and access this dataset content.

PhysicalAI Autonomous Vehicles

Dataset Description

The PhysicalAI-Autonomous-Vehicles dataset provides one of the largest, most geographically diverse collections of multi-sensor data empowering AV researchers to build the next generation of Physical AI based end-to-end driving systems.

mosaic_4x4

This dataset has a total of 1727 hours of driving recorded from planned data-collection drives in 25 countries and 2500+ cities. The data captures diverse traffic, weather conditions, obstacles, and pedestrians in the environment. It consists of 310,895 clips that are each 20 seconds long. The sensor data includes multi-camera and LiDAR coverage for all clips, and radar coverage for 163,850 clips.

Geographic Coverage

Approximately 50% of the data comes from throughout the US and the remaining 50% comes from 24 EU countries.

USA EU

country count
United States 155360
Germany 45673
France 10911
Italy 9082
Sweden 7451
Spain 6815
Portugal 6220
Greece 6123
Austria 5586
Finland 5237
Netherlands 5048
Croatia 4990
Denmark 4688
Slovenia 4341
Estonia 4186
Slovakia 4165
Belgium 3951
Czechia 3706
Lithuania 3426
Poland 3340
Romania 2807
Luxembourg 2652
Latvia 2187
Hungary 1996
Bulgaria 954

Environmental and Traffic Diversity

  • Traffic density patterns: no traffic, light traffic, medium traffic, and heavy traffic
  • Road types: highways, urban, residential, and rural roads
  • Weather: clear, rain, snow, fog
  • Surface conditions: dry, wet, snow/ice
  • Time-of-day: daytime, nighttime
  • Infrastructure elements such as tunnels, bridges, roundabouts, railway crossings, toll booths, inclines, and more

Dataset Owner(s)

NVIDIA Corporation

Dataset Creation Date

10/28/2025

License/Terms of Use

NVIDIA Autonomous Vehicle Dataset License Agreement

Intended Usage

This dataset can be used for autonomous vehicle related use cases only which can be both commercial or non-commercial as long as the mentioned license terms are abided by. The size and diversity of this multi-sensor dataset makes it great for research on end-to-end driving, neural reconstruction, synthetic data generation, scenario mining, and many other autonomous vehicle applications.

Dataset Characterization

  • Data Collection Method

    • Automatic/Sensor
  • Labeling Method

    • Automatic/Sensor

Data Format

We store the data separately for each sensor (camera, LiDAR and radar). Besides these sensors we also provide ego motion, calibration data, autogenerated (non-GT) machine labels, and other metadata.

Because of the significant size of this dataset, we provide all features (sensor data and autolabels) in chunks of up to 100 clips each. The exception to this chunking is clip-level metadata which we intend for researchers to use to identify which subset of chunks they are interested in downloading according to their target application. Significant storage space and bandwidth savings may be achieved by downloading only chunks corresponding to a subset of sensors, country of collection, dataset split, etc.

A python developer kit to support such workflows and additional data format documentation will be made available at https://github.com/NVlabs/physical_ai_av (COMING SOON).

Camera Data

This sensor captures visual RGB data (i.e., videos) from multiple viewpoints around the vehicle. In our dataset the following seven cameras are included:

  • Cross left 120 fov
  • Cross right 120 fov
  • Front wide 120 fov
  • Front tele 30 fov
  • Rear left 70 fov
  • Rear right 70 fov
  • Rear tele 30 fov

Directory structure

camera/
β”œβ”€ camera_front_wide_120fov/
β”‚  β”œβ”€ camera_front_wide_120fov.chunk_0000.zip  
β”‚  └─ ...
└─ camera_cross_left_120fov/
└─ ...

Each chunk_xxxx.zip contains approximately 100 1080p mp4 files recorded at 30fps. Each mp4 will be named <clip_uuid>.camera_<field_of_view>.mp4. Users can use this UUID to map across different corresponding views and sensors (provided there is coverage) under the designated sensor directories. The chunks also contain frame timestamps parquets corresponding to the camera mp4 files with a UUID tag in the name.

LiDAR Data

This directory contains 3D point cloud data recorded using a top 360 degree rotating LiDAR.

β”œβ”€ lidar/
     └─ lidar_top_360fov/
            β”œβ”€ lidar_top_360fov_clip_0000.zip
            β”œβ”€ ...
            └─ lidar_top_360fov_clip_XXXX.zip

Inside lidar_top_360fov_clip_0000.zip, there are approximately 100 lidar parquet files. Each parquet will be named <clip_uuid>.lidar_top360_fov.parquet and contains approximately 200 lidar spins (i.e. 10Hz capture rate for a 20sec clip).

Parquet Schema

{   
    'spin_index': int64,                 # Spin number (0, 1, 2, ...199)
    'reference_timestamp': int64,        # Reference timestamp (microseconds)
    'draco_encoded_pointcloud': binary,  # Draco-encoded point cloud
}

The point cloud can be decoded, e.g., by using the DracoPy library.

Radar Data

This folder contains 3D radar point clouds data recorded using (up to) 10 radars located in the front bumper center, front left corner, front right corner, left side, right side, rear left corner, rear right corner, rear left, and rear right.

 radar/
   β”œβ”€ radar_corner_front_left_srr_0/
   β”‚  β”œβ”€ radar_corner_front_left_srr_0.chunk_0000.zip  
   β”‚  β”œβ”€ ...
   β”‚  └─ radar_corner_front_left_srr_0.chunk_xxxx.zip
   β”œβ”€ radar_corner_front_right_srr_0/   
   └─ ...

Inside chunk_XXXX.zip, there are approximately 100 radar parquet files. Each parquet will be named <clip_uuid>.radar_<field_of_view>_<configuration>.parquet. The letters srr stand for short range radar, mrr for medium range radar, and lrr for long range radar.

Unlike other sensors, for a clip with radar data coverage, the radar sensors for each field of view can have varying model types, depending on the clip. Therefore, the zip files accompany the numerical reference like in srr_0, srr_3 at the end to denote the radar model reference.

Parquet Schema

{
    # Index
    'scan_index': int64,           # Sequential scan number
    
    # Timestamps
    'timestamp': int64,            # System timestamp in microseconds
    'sensor_timestamp': int64,     # Sensor timestamp in microseconds
    
    # Scan Information
    'num_returns': int64,          # Number of detections in scan
    'doppler_ambiguity': float32,  # Doppler ambiguity value
    'max_returns': float64,        # Maximum # of returns (NaN if inapplicable)
    'detection_index': int64,      # Detection index within scan
    'radar_model': uint8,          # Radar model identifier 
    
    # Detection Spatial Data
    'azimuth': float32,            # Horizontal angle in radians
    'elevation': float32,          # Vertical angle in radians
    'distance': float32,           # Distance to target in meters
    
    # Detection Kinematics
    'radial_velocity': float32,    # Radial velocity in m/s 
    
    # Detection Quality
    'rcs': float32,                # Radar cross-section in dBsm
    'snr': float32,                # Signal-to-noise ratio in dB
    'exist_probb': uint8,          # Existence probability
}

Calibration Data

Camera intrinsics: Parquet files which contain parameters including f-theta camera model polynomial coefficients.

{
    # Index (multi-level)
    'clip_id': str,                    # Unique clip identifier UUID
    'camera_name': str,                # Camera sensor name (7 types)
    
    # Image Dimensions
    'width': int64,                    # Image width in pixels 
    'height': int64,                   # Image height in pixels 
    
    # Principal Point (optical center)
    'cx': float64,                     # Principal point X coordinate (pixels)
    'cy': float64,                     # Principal point Y coordinate (pixels)
    
    # Backward (Undistortion) f-theta Polynomial Coefficients
    'bw_poly_0': float64,              # Distortion polynomial coefficient 0 
    'bw_poly_1': float64,              # Distortion polynomial coefficient 1
    'bw_poly_2': float64,              # Distortion polynomial coefficient 2
    'bw_poly_3': float64,              # Distortion polynomial coefficient 3
    'bw_poly_4': float64,              # Distortion polynomial coefficient 4
    
    # Forward (Distortion) f-theta Polynomial Coefficients
    'fw_poly_0': float64,              # Distortion polynomial coefficient 0 
    'fw_poly_1': float64,              # Distortion polynomial coefficient 1 (focal length)
    'fw_poly_2': float64,              # Distortion polynomial coefficient 2
    'fw_poly_3': float64,              # Distortion polynomial coefficient 3
    'fw_poly_4': float64,              # Distortion polynomial coefficient 4
}

Sensor extrinsics: sensor pose, i.e., quaternion rotation and x,y,z position, for 7 cameras, 1 LiDAR, and (up to) 10 radars.

{
  'qx': float64   # Quarternions
  'qy': float64
  'qz': float64
  'qw': float64
  'x' : float64   # x,y,z positions for rig coordinate frame
  'y' : float64
  'z' : float64
}

#Rig coordinate origin: Center of the rear axle, projected onto the ground plane. 
#X-axis: Points forward
#Y-axis: Points left (when looking forward)
#Z-axis: Points up

Vehicle dimensions for respective clips in each chunk.

{
    # Index
    'clip_id': str,                       # Unique clip identifier UUID

    # Vehicle Dimensions (all in meters)
    'length': float64,                    # Vehicle length (front to back)
    'width': float64,                     # Vehicle width (left to right)
    'height': float64,                    # Vehicle height (bottom to top)
    'rear_axle_to_bbox_center': float64,  # Distance from rear axle to geometric center
    'wheelbase': float64,                 # Distance between front/rear axles
    'track_width': float64,               # Wheel track width (left to right)
}

Labels

Ego Motion: in a local coordinate frame consistent across all timestamps with the origin located at the ego vehicle's position at timestamp 0, oriented such that there is 0 yaw at timestamp 0 but otherwise attitude (pitch and roll) are estimated with respect to gravity.

{
    # Timing
    'timestamp': int64,                 # Absolute timestamp in microseconds
    
    # Pose - Orientation (Quaternion)
    'qx': float64,                      # Quaternion X component for orientation
    'qy': float64,                      # Quaternion Y component for orientation
    'qz': float64,                      # Quaternion Z component for orientation
    'qw': float64,                      # Quaternion W (scalar) for orientation
    
    # Pose - Position in World Frame (meters)
    'x': float64,                       # X position
    'y': float64,                       # Y position
    'z': float64,                       # Z position
    
    # Velocity in World Frame (m/s)
    'vx': float64,                      # X velocity
    'vy': float64,                      # Y velocity
    'vz': float64,                      # Z velocity
    
    # Acceleration in World Frame (m/sΒ²)
    'ax': float64,                      # X acceleration
    'ay': float64,                      # Y acceleration
    'az': float64,                      # Z acceleration
    
    # Vehicle Rotation
    'curvature': float64,               # Path curvature (1/meters, inverse radius)
}

Objects and Road Elements: (COMING SOON)

Metadata

Sensor presence parquet: captures the sensor availability per clip

{
    # Index
    'clip_id': str,                            # Unique clip identifier UUID
    
    # Camera Sensors (all bool - True = present, False = absent)
    'camera_cross_left_120fov': bool,          # Left cross-traffic camera (120Β° FOV)
    'camera_cross_right_120fov': bool,         # Right cross-traffic camera (120Β° FOV)
    'camera_front_tele_30fov': bool,           # Front telephoto camera (30Β° FOV)
    'camera_front_wide_120fov': bool,          # Front wide camera (120Β° FOV)
    'camera_rear_left_70fov': bool,            # Rear left camera (70Β° FOV)
    'camera_rear_right_70fov': bool,           # Rear right camera (70Β° FOV)
    'camera_rear_tele_30fov': bool,            # Rear telephoto camera (30Β° FOV)
    
    # LiDAR Sensor (bool)
    'lidar_top_360fov': bool,                  # Top-mounted 360Β° LiDAR
    
    # Radar Sensors - Corner (SRR = Short Range Radar)
    'radar_corner_front_left_srr_0': bool,     # Front left corner radar (model type 0)
    'radar_corner_front_left_srr_3': bool,     # Front left corner radar (model type 3)
    'radar_corner_front_right_srr_0': bool,    # Front right corner radar (model type 0)
    'radar_corner_front_right_srr_3': bool,    # Front right corner radar (model type 3)
    'radar_corner_rear_left_srr_0': bool,      # Rear left corner radar (model type 0)
    'radar_corner_rear_left_srr_3': bool,      # Rear left corner radar (model type 3)
    'radar_corner_rear_right_srr_0': bool,     # Rear right corner radar (model type 0)
    'radar_corner_rear_right_srr_3': bool,     # Rear right corner radar (model type 3)
    
    # Radar Sensors - Front Center (LRR = Long Range Radar, MRR = Medium Range Radar)
    'radar_front_center_imaging_lrr_1': bool,  # Front imaging LRR (model type 1)
    'radar_front_center_mrr_2': bool,          # Front MRR (model type 2)
    'radar_front_center_srr_0': bool,          # Front center SRR (model type 0)
    
    # Radar Sensors - Rear
    'radar_rear_left_mrr_2': bool,             # Rear left medium range (model type 2)
    'radar_rear_left_srr_0': bool,             # Rear left short range (model type 0)
    'radar_rear_right_mrr_2': bool,            # Rear right medium range (model type 2)
    'radar_rear_right_srr_0': bool,            # Rear right short range (model type 0)
    
    # Radar Sensors - Side
    'radar_side_left_srr_0': bool,             # Left side short range (model type 0)
    'radar_side_left_srr_3': bool,             # Left side short range (model type 3)
    'radar_side_right_srr_0': bool,            # Right side short range (model type 0)
    'radar_side_right_srr_3': bool,            # Right side short range (model type 3)
    
    # Radar Configuration Level
    'radar_config': str,                       # Radar config ('NA', 'low', 'med', 'high')
}

The final "radar_config" column summarizes the fact that there are 4 possible instantiations of row values for the radar sensors collectively, specifically

  • NA (no radars present)
  • low (all srr_0 radars)
  • med (all srr_3 radars except for side radars, all mrr_2 and lrr_1 radars)
  • high (all srr_3 radars, all mrr_2 and lrr_1 radars)

Data collection parquet: contains fields to filter clips by, e.g. country where clip was recorded, the month of the year and time of day.

{
    # Index
    'clip_id': str,                     # Unique clip identifier UUID
    
    # Geographic Information
    'country': str,                     # Country where data was collected
    
    # Temporal Information
    'month': int64,                     # Month of collection (1-12)
    'hour_of_day': int64,               # Hour when clip recorded (0-23)
    
    # Vehicle Platform
    'platform_class': str,              # Vehicle platform type (hyperion_8/8.1)
}

Dataset Quantification

  • Record Count: 1727 hours / 310,895 clips of driving data organized into 20s long clips
  • Feature Count: 7 cameras, 1 lidar, (up to) 10 radar, ego motion, calibration, machine labels
  • Measurement of Total Data Storage: ~100TB

References

Ethical Considerations

NVIDIA believes Trustworthy AI is a shared responsibility and we have established policies and practices to enable development for a wide array of AI applications. When downloaded or used in accordance with our terms of service, developers should work with their internal model team to ensure this model meets requirements for the relevant industry and use case and addresses unforeseen product misuse.

Please report security vulnerabilities or NVIDIA AI Concerns here.

Downloads last month
1,363

Collection including nvidia/PhysicalAI-Autonomous-Vehicles