Graph and download economic data for Vehicle Miles Traveled (TRFVOLUSM227SFWA) from Jan 2000 to Apr 2025 about miles, travel, vehicles, and USA.

National Highway Traffic Safety Administration releases data on highway fatalities in the Fatality Analysis Reporting System (FARS). Data for the most recent year are preliminary estimates.

Graph and download economic data for Moving 12-Month Total Vehicle Miles Traveled (M12MTVUSM227NFWA) from Dec 1970 to Apr 2025 about miles, travel, vehicles, and USA.

United States US: Road Fatalities: Per One Million Vehicle-km data was reported at 7.805 Ratio in 2023. This records a decrease from the previous number of 8.265 Ratio for 2022. United States US: Road Fatalities: Per One Million Vehicle-km data is updated yearly, averaging 8.404 Ratio from Dec 1994 (Median) to 2023, with 30 observations. The data reached an all-time high of 10.731 Ratio in 1994 and a record low of 6.725 Ratio in 2014. United States US: Road Fatalities: Per One Million Vehicle-km data remains active status in CEIC and is reported by Organisation for Economic Co-operation and Development. The data is categorized under Global Database’s United States – Table US.OECD.ITF: Road Traffic and Road Accident Fatalities: OECD Member: Annual. [COVERAGE] ROAD FATALITIES A road fatality is any person killed immediately or dying within 30 days as a result of an injury accident, excluding suicides. A killed person is excluded if the competent authority declares the cause of death to be suicide, i.e. a deliberate act to injure oneself resulting in death. For countries that do not apply the threshold of 30 days, conversion coefficients are estimated so that comparison on the basis of the 30-day definition can be made. ROAD TRAFFIC Road traffic is any movement of a road vehicle on a given road network. When a road vehicle is being carried on another vehicle, only the movement of the carrying (active mode) is considered. [COVERAGE] ROAD TRAFFIC IRTAD - Data refer to road motor vehicle traffic of motorised two-wheelers, passenger cars, goods road motor vehicles and buses. [STAT_CONC_DEF] ROAD TRAFFIC IRTAD - Data are calculated using automatic and manual roadside traffic counts.

This dataset provides detailed information on road surfaces from OpenStreetMap (OSM) data, distinguishing between paved and unpaved surfaces across the region. This information is based on road surface prediction derived from hybrid deep learning approach. For more information on Methods, refer to the paper

Roughly 0.0 million km of roads are mapped in OSM in this region. Based on AI-mapped estimates the share of paved and unpaved roads is approximately 0.0 and 0.0 (in million kms), corressponding to nan% and nan% respectively of the total road length in the dataset region. 0.0 million km or nan% of road surface information is missing in OSM. In order to fill this gap, Mapillary derived road surface dataset provides an additional 0.0 million km of information (corressponding to nan% of total missing information on road surface)

It is intended for use in transportation planning, infrastructure analysis, climate emissions and geographic information system (GIS) applications.

This dataset provides comprehensive information on road and urban area features, including location, surface quality, and classification metadata. This dataset includes attributes from OpenStreetMap (OSM) data, AI predictions for road surface, and urban classifications.

AI features:

• pred_class: Model-predicted class for the road surface, with values "paved" or "unpaved."

• pred_label: Binary label associated with pred_class (0 = paved, 1 = unpaved).

• osm_surface_class: Classification of the surface type from OSM, categorized as "paved" or "unpaved."

• combined_surface_osm_priority: Surface classification combining pred_label and surface(OSM) while prioritizing the OSM surface tag, classified as "paved" or "unpaved."

• combined_surface_DL_priority: Surface classification combining pred_label and surface(OSM) while prioritizing DL prediction pred_label, classified as "paved" or "unpaved."

• n_of_predictions_used: Number of predictions used for the feature length estimation.

• predicted_length: Predicted length based on the DL model’s estimations, in meters.

• DL_mean_timestamp: Mean timestamp of the predictions used, for comparison.

OSM features may have these attributes(Learn what tags mean here):

• name: Name of the feature, if available in OSM.

• name:en: Name of the feature in English, if available in OSM.

• name:* (in local language): Name of the feature in the local official language, where available.

• highway: Road classification based on OSM tags (e.g., residential, motorway, footway).

• surface: Description of the surface material of the road (e.g., asphalt, gravel, dirt).

• smoothness: Assessment of surface smoothness (e.g., excellent, good, intermediate, bad).

• width: Width of the road, where available.

• lanes: Number of lanes on the road.

• oneway: Indicates if the road is one-way (yes or no).

• bridge: Specifies if the feature is a bridge (yes or no).

• layer: Indicates the layer of the feature in cases where multiple features are stacked (e.g., bridges, tunnels).

• source: Source of the data, indicating the origin or authority of specific attributes.

Urban classification features may have these attributes:

• continent: The continent where the data point is located (e.g., Europe, Asia).

• country_iso_a2: The ISO Alpha-2 code representing the country (e.g., "US" for the United States).

• urban: Binary indicator for urban areas based on the GHSU Urban Layer 2019. (0 = rural, 1 = urban)

• urban_area: Name of the urban area or city where the data point is located.

• osm_id: Unique identifier assigned by OpenStreetMap (OSM) to each feature.

• osm_type: Type of OSM element (e.g., node, way, relation).

The data originates from OpenStreetMap (OSM) and is augmented with model predictions using images downloaded from Mapillary in combination with the GHSU Global Human Settlement Urban Layer 2019 and AFRICAPOLIS2020 urban layer.

This dataset is one of many HeiGIT exports on HDX. See the HeiGIT website for more information.

We are looking forward to hearing about your use-case! Feel free to reach out to us and tell us about your research at communications@heigit.org – we would be happy to amplify your work.

This dataset provides detailed information on road surfaces from OpenStreetMap (OSM) data, distinguishing between paved and unpaved surfaces across the region. This information is based on road surface prediction derived from hybrid deep learning approach. For more information on Methods, refer to the paper

Roughly 0.4783 million km of roads are mapped in OSM in this region. Based on AI-mapped estimates the share of paved and unpaved roads is approximately 0.0081 and 0.3254 (in million kms), corressponding to 1.6908% and 68.0296% respectively of the total road length in the dataset region. 0.1448 million km or 30.2796% of road surface information is missing in OSM. In order to fill this gap, Mapillary derived road surface dataset provides an additional 0.0001 million km of information (corressponding to 0.067% of total missing information on road surface)

It is intended for use in transportation planning, infrastructure analysis, climate emissions and geographic information system (GIS) applications.

This dataset provides comprehensive information on road and urban area features, including location, surface quality, and classification metadata. This dataset includes attributes from OpenStreetMap (OSM) data, AI predictions for road surface, and urban classifications.

AI features:

• pred_class: Model-predicted class for the road surface, with values "paved" or "unpaved."

• pred_label: Binary label associated with pred_class (0 = paved, 1 = unpaved).

• osm_surface_class: Classification of the surface type from OSM, categorized as "paved" or "unpaved."

• combined_surface_osm_priority: Surface classification combining pred_label and surface(OSM) while prioritizing the OSM surface tag, classified as "paved" or "unpaved."

• combined_surface_DL_priority: Surface classification combining pred_label and surface(OSM) while prioritizing DL prediction pred_label, classified as "paved" or "unpaved."

• n_of_predictions_used: Number of predictions used for the feature length estimation.

• predicted_length: Predicted length based on the DL model’s estimations, in meters.

• DL_mean_timestamp: Mean timestamp of the predictions used, for comparison.

OSM features may have these attributes(Learn what tags mean here):

• name: Name of the feature, if available in OSM.

• name:en: Name of the feature in English, if available in OSM.

• name:* (in local language): Name of the feature in the local official language, where available.

• highway: Road classification based on OSM tags (e.g., residential, motorway, footway).

• surface: Description of the surface material of the road (e.g., asphalt, gravel, dirt).

• smoothness: Assessment of surface smoothness (e.g., excellent, good, intermediate, bad).

• width: Width of the road, where available.

• lanes: Number of lanes on the road.

• oneway: Indicates if the road is one-way (yes or no).

• bridge: Specifies if the feature is a bridge (yes or no).

• layer: Indicates the layer of the feature in cases where multiple features are stacked (e.g., bridges, tunnels).

• source: Source of the data, indicating the origin or authority of specific attributes.

Urban classification features may have these attributes:

• continent: The continent where the data point is located (e.g., Europe, Asia).

• country_iso_a2: The ISO Alpha-2 code representing the country (e.g., "US" for the United States).

• urban: Binary indicator for urban areas based on the GHSU Urban Layer 2019. (0 = rural, 1 = urban)

• urban_area: Name of the urban area or city where the data point is located.

• osm_id: Unique identifier assigned by OpenStreetMap (OSM) to each feature.

• osm_type: Type of OSM element (e.g., node, way, relation).

The data originates from OpenStreetMap (OSM) and is augmented with model predictions using images downloaded from Mapillary in combination with the GHSU Global Human Settlement Urban Layer 2019 and AFRICAPOLIS2020 urban layer.

This dataset is one of many HeiGIT exports on HDX. See the HeiGIT website for more information.

We are looking forward to hearing about your use-case! Feel free to reach out to us and tell us about your research at communications@heigit.org – we would be happy to amplify your work.

The number of road traffic fatalities per one million inhabitants in the United States was forecast to continuously increase between 2024 and 2029 by in total 18.5 deaths (+13.81 percent). After the tenth consecutive increasing year, the number is estimated to reach 152.46 deaths and therefore a new peak in 2029. Depicted here are the estimated number of deaths which occured in relation to road traffic. They are set in relation to the population size and depicted as deaths per 100,000 inhabitants.The shown data are an excerpt of Statista's Key Market Indicators (KMI). The KMI are a collection of primary and secondary indicators on the macro-economic, demographic and technological environment in up to 150 countries and regions worldwide. All indicators are sourced from international and national statistical offices, trade associations and the trade press and they are processed to generate comparable data sets (see supplementary notes under details for more information).Find more key insights for the number of road traffic fatalities per one million inhabitants in countries like Mexico and Canada.

This dataset provides detailed information on road surfaces from OpenStreetMap (OSM) data, distinguishing between paved and unpaved surfaces across the region. This information is based on road surface prediction derived from hybrid deep learning approach. For more information on Methods, refer to the paper

Roughly 0.3072 million km of roads are mapped in OSM in this region. Based on AI-mapped estimates the share of paved and unpaved roads is approximately 0.0337 and 0.0178 (in million kms), corressponding to 10.9845% and 5.798% respectively of the total road length in the dataset region. 0.2557 million km or 83.2175% of road surface information is missing in OSM. In order to fill this gap, Mapillary derived road surface dataset provides an additional 0.0017 million km of information (corressponding to 0.6463% of total missing information on road surface)

It is intended for use in transportation planning, infrastructure analysis, climate emissions and geographic information system (GIS) applications.

This dataset provides comprehensive information on road and urban area features, including location, surface quality, and classification metadata. This dataset includes attributes from OpenStreetMap (OSM) data, AI predictions for road surface, and urban classifications.

AI features:

• pred_class: Model-predicted class for the road surface, with values "paved" or "unpaved."

• pred_label: Binary label associated with pred_class (0 = paved, 1 = unpaved).

• osm_surface_class: Classification of the surface type from OSM, categorized as "paved" or "unpaved."

• combined_surface_osm_priority: Surface classification combining pred_label and surface(OSM) while prioritizing the OSM surface tag, classified as "paved" or "unpaved."

• combined_surface_DL_priority: Surface classification combining pred_label and surface(OSM) while prioritizing DL prediction pred_label, classified as "paved" or "unpaved."

• n_of_predictions_used: Number of predictions used for the feature length estimation.

• predicted_length: Predicted length based on the DL model’s estimations, in meters.

• DL_mean_timestamp: Mean timestamp of the predictions used, for comparison.

OSM features may have these attributes(Learn what tags mean here):

• name: Name of the feature, if available in OSM.

• name:en: Name of the feature in English, if available in OSM.

• name:* (in local language): Name of the feature in the local official language, where available.

• highway: Road classification based on OSM tags (e.g., residential, motorway, footway).

• surface: Description of the surface material of the road (e.g., asphalt, gravel, dirt).

• smoothness: Assessment of surface smoothness (e.g., excellent, good, intermediate, bad).

• width: Width of the road, where available.

• lanes: Number of lanes on the road.

• oneway: Indicates if the road is one-way (yes or no).

• bridge: Specifies if the feature is a bridge (yes or no).

• layer: Indicates the layer of the feature in cases where multiple features are stacked (e.g., bridges, tunnels).

• source: Source of the data, indicating the origin or authority of specific attributes.

Urban classification features may have these attributes:

• continent: The continent where the data point is located (e.g., Europe, Asia).

• country_iso_a2: The ISO Alpha-2 code representing the country (e.g., "US" for the United States).

• urban: Binary indicator for urban areas based on the GHSU Urban Layer 2019. (0 = rural, 1 = urban)

• urban_area: Name of the urban area or city where the data point is located.

• osm_id: Unique identifier assigned by OpenStreetMap (OSM) to each feature.

• osm_type: Type of OSM element (e.g., node, way, relation).

The data originates from OpenStreetMap (OSM) and is augmented with model predictions using images downloaded from Mapillary in combination with the GHSU Global Human Settlement Urban Layer 2019 and AFRICAPOLIS2020 urban layer.

This dataset is one of many HeiGIT exports on HDX. See the HeiGIT website for more information.

We are looking forward to hearing about your use-case! Feel free to reach out to us and tell us about your research at communications@heigit.org – we would be happy to amplify your work.

The number of road accidents per one million inhabitants in the United States was forecast to continuously decrease between 2024 and 2029 by in total 2,490.4 accidents (-14.99 percent). After the eighth consecutive decreasing year, the number is estimated to reach 14,118.78 accidents and therefore a new minimum in 2029. Depicted here are the estimated number of accidents which occured in relation to road traffic. They are set in relation to the population size and depicted as accidents per one million inhabitants.The shown data are an excerpt of Statista's Key Market Indicators (KMI). The KMI are a collection of primary and secondary indicators on the macro-economic, demographic and technological environment in up to 150 countries and regions worldwide. All indicators are sourced from international and national statistical offices, trade associations and the trade press and they are processed to generate comparable data sets (see supplementary notes under details for more information).Find more key insights for the number of road accidents per one million inhabitants in countries like Mexico and Canada.

Graph and download economic data for Total Construction Spending: Highway and Street in the United States (TLHWYCONS) from Jan 2002 to May 2025 about expenditures, construction, and USA.

United States US: Road Fatalities: Per One Million Road Motor Vehicles data was reported at 120.615 Ratio in 2019. This records a decrease from the previous number of 123.083 Ratio for 2018. United States US: Road Fatalities: Per One Million Road Motor Vehicles data is updated yearly, averaging 165.059 Ratio from Dec 1994 (Median) to 2019, with 26 observations. The data reached an all-time high of 212.199 Ratio in 1995 and a record low of 118.903 Ratio in 2014. United States US: Road Fatalities: Per One Million Road Motor Vehicles data remains active status in CEIC and is reported by Organisation for Economic Co-operation and Development. The data is categorized under Global Database’s United States – Table US.OECD.ITF: Road Traffic and Road Accident Fatalities: OECD Member: Annual. VEHICLES The stock of road motor vehicles is the number of road motor vehicles registered at a given date in a country and licenced to use roads open to public traffic. This includes road vehicles exempted from annual taxes or licence fee; it also includes imported second-hand vehicles and other road vehicles according to national practices. It should not include military vehicles.; ROAD FATALITIES A road fatality is any person killed immediately or dying within 30 days as a result of an injury accident, excluding suicides. A killed person is excluded if the competent authority declares the cause of death to be suicide, i.e. a deliberate act to injure oneself resulting in death. For countries that do not apply the threshold of 30 days, conversion coefficients are estimated so that comparison on the basis of the 30-day definition can be made. VEHICLES A road motor vehicle is a road vehicle fitted with an engine whence it derives its sole means of propulsion, which is normally used for carrying persons or goods or for drawing, on the road, vehicles used for the carriage of persons or goods.; VEHICLES Motor vehicle refers to any motorised (mechanically or electronically powered) road vehicle not operated on rail.

United States US: Goods Road Motor Vehicles: Per One Million Units of Current USD GDP data was reported at 7.450 Ratio in 2019. This records a decrease from the previous number of 7.498 Ratio for 2018. United States US: Goods Road Motor Vehicles: Per One Million Units of Current USD GDP data is updated yearly, averaging 7.954 Ratio from Dec 1994 (Median) to 2019, with 26 observations. The data reached an all-time high of 9.067 Ratio in 1994 and a record low of 7.450 Ratio in 2019. United States US: Goods Road Motor Vehicles: Per One Million Units of Current USD GDP data remains active status in CEIC and is reported by Organisation for Economic Co-operation and Development. The data is categorized under Global Database’s United States – Table US.OECD.ITF: Motor Vehicles Statistics: OECD Member: Annual. GOODS VEHICLES The stock of road motor vehicles is the number of road motor vehicles registered at a given date in a country and licenced to use roads open to public traffic. This includes road vehicles exempted from annual taxes or licence fee; it also includes imported second-hand vehicles and other road vehicles according to national practices. It should not include military vehicles.; GOODS VEHICLES A goods road vehicle is any single road motor vehicle designed to carry goods (e.g. a lorry), or any coupled combination of road vehicles designed to carry goods (i.e. lorry with trailer(s), or road tractor with or without semi-trailer and with or without trailer).; GOODS VEHICLES Data refer to vehicles other than motorised two-wheelers, passenger cars and buses.

Sample Data: https://cloud.drivertechnologies.com/shared?s=146&t=4:03&token=0f469c88-d578-4b4f-80b2-f53f195683b2

At Driver Technologies, we are dedicated to harnessing advanced technology to gather anonymized critical driving data through our innovative dash cam app, which operates seamlessly on end users' smartphones. Our Speed Over Limit Driver Behavior Data offering is a key resource for understanding driver behavior and improving safety on the roads, making it an essential tool for various industries.

What Makes Our Data Unique? Our Speed Over Limit Driver Behavior Data is distinguished by its real-time collection capabilities, utilizing our built-in computer vision technology to identify and capture instances where a driver nearly gets into an accident. This data reflects critical safety events that are indicative of potential risks and non-compliance with traffic regulations. By providing data on these significant events, our dataset empowers clients to perform in-depth analysis.

How Is the Data Generally Sourced? Our data is sourced directly from users who utilize our dash cam app, which harnesses the smartphone’s camera and sensors to record during a trip. This direct sourcing method ensures that our data is unbiased and represents a wide variety of conditions and environments. The data is not only authentic and reflective of current road conditions but is also abundant in volume, offering millions of miles of recorded trips that cover diverse scenarios. For our Speed Over Limit Driver Behavior Data, we leverage computer vision models to read speed limit signs as the driver drives past them, then compare that to speed data captured using the phone's sensor.

Primary Use-Cases and Verticals Driver Behavior Analysis: Organizations can leverage our dataset to analyze driving habits and identify trends in driver behavior. This analysis can help in understanding patterns related to rule compliance and potential risk factors.

Training Computer Vision Models: Clients can utilize our annotated data to develop and refine their own computer vision models for applications in autonomous vehicles, ensuring better decision-making capabilities in complex driving environments.

Improving Risk Assessment: Insurers can utilize our dataset to refine their risk assessment models. By understanding the frequency and context of significant events, they can better evaluate driver risk profiles, leading to more accurate premium pricing and improved underwriting processes.

Integration with Our Broader Data Offering The Speed Over Limit Driver Behavior Data is a crucial component of our broader data offerings at Driver Technologies. It complements our extensive library of driving data collected from various vehicles and road users, creating a comprehensive data ecosystem that supports multiple verticals, including insurance, automotive technology, and smart city planning.

In summary, Driver Technologies' Speed Over Limit Driver Behavior Data provides a unique opportunity for data buyers to access high-quality, actionable insights that drive innovation across mobility. By integrating our Speed Over Limit Driver Behavior Data with other datasets, clients can gain a holistic view of transportation dynamics, enhancing their analytical capabilities and decision-making processes.

At Driver Technologies, we specialize in collecting high-quality, highly-anonymized, driving data crowdsourced using our dash cam app. Our Speed Limit Sign Video Data is built from the millions of miles of driving data captured and is optimized to be trained for whatever computer vision models you need and enhancing various applications in transportation and safety.

What Makes Our Data Unique? What sets our Speed Limit Sign Video Data apart is its comprehensive approach to road object detection. By leveraging advanced computer vision models, we analyze the captured video to identify and classify various road objects encountered during an end user's trip. This includes road signs, pedestrians, vehicles, traffic signs, and road conditions, resulting in rich, annotated datasets that can be used for a range of applications.

How Is the Data Generally Sourced? Our data is sourced directly from users who utilize our dash cam app, which harnesses the smartphone’s camera and sensors to record during a trip. This direct sourcing method ensures that our data is unbiased and represents a wide variety of conditions and environments. The data is not only authentic and reflective of current road conditions but is also abundant in volume, offering millions of miles of recorded trips that cover diverse scenarios.

Primary Use-Cases and Verticals The Speed Limit Sign Geographic Video Data is tailored for various sectors, particularly those involved in transportation, urban planning, and autonomous vehicle development. Key use cases include:

Training Computer Vision Models: Clients can utilize our annotated data to develop and refine their own computer vision models for applications in autonomous vehicles, ensuring better object detection and decision-making capabilities in complex road environments.

Urban Planning and Infrastructure Development: Our data helps municipalities understand road usage patterns, enabling them to make informed decisions regarding infrastructure improvements, safety measures, and traffic light placement. Our data can also aid in making sure municipalities have an accurate count of signs in their area.

Integration with Our Broader Data Offering The Speed Limit Sign Geographic Video Data is a crucial component of our broader data offerings at Driver Technologies. It complements our extensive library of driving data collected from various vehicles and road users, creating a comprehensive data ecosystem that supports multiple verticals, including insurance, automotive technology, and computer vision models.

In summary, Driver Technologies' Speed Limit Sign Geographic Video Data provides a unique opportunity for data buyers to access high-quality, actionable insights that drive innovation across mobility. By integrating our Speed Limit Sign Geographic Video Data with other datasets, clients can gain a holistic view of transportation dynamics, enhancing their analytical capabilities and decision-making processes.

At Driver Technologies, we are dedicated to harnessing advanced technology to gather anonymized critical driving data through our innovative dash cam app, which operates seamlessly on end users' smartphones. Our Near Accident Traffic Data offering is a key resource for understanding driver behavior and improving safety on the roads, making it an essential tool for various industries.

What Makes Our Data Unique? Our Near Accident Traffic Data is distinguished by its real-time collection capabilities, utilizing our built-in computer vision technology to identify and capture instances where a driver nearly gets into an accident. This data reflects critical safety events that are indicative of potential risks and non-compliance with traffic regulations. By providing data on these significant events, our dataset empowers clients to perform in-depth analysis.

How Is the Data Generally Sourced? Our data is sourced directly from users who utilize our dash cam app, which harnesses the smartphone’s camera and sensors to record during a trip. This direct sourcing method ensures that our data is unbiased and represents a wide variety of conditions and environments. The data is not only authentic and reflective of current road conditions but is also abundant in volume, offering millions of miles of recorded trips that cover diverse scenarios.

Primary Use-Cases and Verticals Driver Behavior Analysis: Organizations can leverage our dataset to analyze driving habits and identify trends in driver behavior. This analysis can help in understanding patterns related to rule compliance and potential risk factors.

Training Computer Vision Models: Clients can utilize our annotated data to develop and refine their own computer vision models for applications in autonomous vehicles, ensuring better decision-making capabilities in complex driving environments.

Improving Risk Assessment: Insurers can utilize our dataset to refine their risk assessment models. By understanding the frequency and context of significant events, they can better evaluate driver risk profiles, leading to more accurate premium pricing and improved underwriting processes.

Integration with Our Broader Data Offering The Near Accident Traffic Data is a crucial component of our broader data offerings at Driver Technologies. It complements our extensive library of driving data collected from various vehicles and road users, creating a comprehensive data ecosystem that supports multiple verticals, including insurance, automotive technology, and smart city planning.

In summary, Driver Technologies' Near Accident Traffic Data provides a unique opportunity for data buyers to access high-quality, actionable insights that drive innovation across mobility. By integrating our Near Accident Traffic Data with other datasets, clients can gain a holistic view of transportation dynamics, enhancing their analytical capabilities and decision-making processes.

This dataset provides detailed information on road surfaces from OpenStreetMap (OSM) data, distinguishing between paved and unpaved surfaces across the region. This information is based on road surface prediction derived from hybrid deep learning approach. For more information on Methods, refer to the paper

Roughly 0.5791 million km of roads are mapped in OSM in this region. Based on AI-mapped estimates the share of paved and unpaved roads is approximately 0.023 and 0.1669 (in million kms), corressponding to 3.9642% and 28.8242% respectively of the total road length in the dataset region. 0.3892 million km or 67.2116% of road surface information is missing in OSM. In order to fill this gap, Mapillary derived road surface dataset provides an additional 0.0021 million km of information (corressponding to 0.5353% of total missing information on road surface)

It is intended for use in transportation planning, infrastructure analysis, climate emissions and geographic information system (GIS) applications.

This dataset provides comprehensive information on road and urban area features, including location, surface quality, and classification metadata. This dataset includes attributes from OpenStreetMap (OSM) data, AI predictions for road surface, and urban classifications.

AI features:

• pred_class: Model-predicted class for the road surface, with values "paved" or "unpaved."

• pred_label: Binary label associated with pred_class (0 = paved, 1 = unpaved).

• osm_surface_class: Classification of the surface type from OSM, categorized as "paved" or "unpaved."

• combined_surface_osm_priority: Surface classification combining pred_label and surface(OSM) while prioritizing the OSM surface tag, classified as "paved" or "unpaved."

• combined_surface_DL_priority: Surface classification combining pred_label and surface(OSM) while prioritizing DL prediction pred_label, classified as "paved" or "unpaved."

• n_of_predictions_used: Number of predictions used for the feature length estimation.

• predicted_length: Predicted length based on the DL model’s estimations, in meters.

• DL_mean_timestamp: Mean timestamp of the predictions used, for comparison.

OSM features may have these attributes(Learn what tags mean here):

• name: Name of the feature, if available in OSM.

• name:en: Name of the feature in English, if available in OSM.

• name:* (in local language): Name of the feature in the local official language, where available.

• highway: Road classification based on OSM tags (e.g., residential, motorway, footway).

• surface: Description of the surface material of the road (e.g., asphalt, gravel, dirt).

• smoothness: Assessment of surface smoothness (e.g., excellent, good, intermediate, bad).

• width: Width of the road, where available.

• lanes: Number of lanes on the road.

• oneway: Indicates if the road is one-way (yes or no).

• bridge: Specifies if the feature is a bridge (yes or no).

• layer: Indicates the layer of the feature in cases where multiple features are stacked (e.g., bridges, tunnels).

• source: Source of the data, indicating the origin or authority of specific attributes.

Urban classification features may have these attributes:

• continent: The continent where the data point is located (e.g., Europe, Asia).

• country_iso_a2: The ISO Alpha-2 code representing the country (e.g., "US" for the United States).

• urban: Binary indicator for urban areas based on the GHSU Urban Layer 2019. (0 = rural, 1 = urban)

• urban_area: Name of the urban area or city where the data point is located.

• osm_id: Unique identifier assigned by OpenStreetMap (OSM) to each feature.

• osm_type: Type of OSM element (e.g., node, way, relation).

The data originates from OpenStreetMap (OSM) and is augmented with model predictions using images downloaded from Mapillary in combination with the GHSU Global Human Settlement Urban Layer 2019 and AFRICAPOLIS2020 urban layer.

This dataset is one of many HeiGIT exports on HDX. See the HeiGIT website for more information.

We are looking forward to hearing about your use-case! Feel free to reach out to us and tell us about your research at communications@heigit.org – we would be happy to amplify your work.

At Driver Technologies, we specialize in collecting high-quality, highly-anonymized, driving data crowdsourced using our dash cam app. Our Pedestrian Crossing Sign Computer Vision Video Data is built from the millions of miles of driving data captured and is optimized to be trained for whatever computer vision models you need and enhancing various applications in transportation and safety.

What Makes Our Data Unique? What sets our Pedestrian Crossing Sign Computer Vision Video Data apart is its comprehensive approach to road object detection. By leveraging advanced computer vision models, we analyze the captured video to identify and classify various road objects encountered during an end user's trip. This includes road signs, pedestrians, vehicles, traffic signs, and road conditions, resulting in rich, annotated datasets that can be used for a range of applications.

How Is the Data Generally Sourced? Our data is sourced directly from users who utilize our dash cam app, which harnesses the smartphone’s camera and sensors to record during a trip. This direct sourcing method ensures that our data is unbiased and represents a wide variety of conditions and environments. The data is not only authentic and reflective of current road conditions but is also abundant in volume, offering millions of miles of recorded trips that cover diverse scenarios.

Primary Use-Cases and Verticals The Pedestrian Crossing Sign Computer Vision Video Data is tailored for various sectors, particularly those involved in transportation, urban planning, and autonomous vehicle development. Key use cases include:

Training Computer Vision Models: Clients can utilize our annotated data to develop and refine their own computer vision models for applications in autonomous vehicles, ensuring better object detection and decision-making capabilities in complex road environments.

Urban Planning and Infrastructure Development: Our data helps municipalities understand road usage patterns, enabling them to make informed decisions regarding infrastructure improvements, safety measures, and traffic light placement. Our data can also aid in making sure municipalities have an accurate count of signs in their area.

Integration with Our Broader Data Offering The Pedestrian Crossing Sign Computer Vision Video Data is a crucial component of our broader data offerings at Driver Technologies. It complements our extensive library of driving data collected from various vehicles and road users, creating a comprehensive data ecosystem that supports multiple verticals, including insurance, automotive technology, and computer vision models.

In summary, Driver Technologies' Pedestrian Crossing Sign Computer Vision Video Data provides a unique opportunity for data buyers to access high-quality, actionable insights that drive innovation across mobility. By integrating our Pedestrian Crossing Sign Computer Vision Video Data with other datasets, clients can gain a holistic view of transportation dynamics, enhancing their analytical capabilities and decision-making processes.

This dataset provides detailed information on road surfaces from OpenStreetMap (OSM) data, distinguishing between paved and unpaved surfaces across the region. This information is based on road surface prediction derived from hybrid deep learning approach. For more information on Methods, refer to the paper

Roughly 1.8582 million km of roads are mapped in OSM in this region. Based on AI-mapped estimates the share of paved and unpaved roads is approximately 0.1766 and 0.1278 (in million kms), corressponding to 9.5052% and 6.877% respectively of the total road length in the dataset region. 1.5538 million km or 83.6178% of road surface information is missing in OSM. In order to fill this gap, Mapillary derived road surface dataset provides an additional 0.0237 million km of information (corressponding to 1.5266% of total missing information on road surface)

It is intended for use in transportation planning, infrastructure analysis, climate emissions and geographic information system (GIS) applications.

This dataset provides comprehensive information on road and urban area features, including location, surface quality, and classification metadata. This dataset includes attributes from OpenStreetMap (OSM) data, AI predictions for road surface, and urban classifications.

AI features:

• pred_class: Model-predicted class for the road surface, with values "paved" or "unpaved."

• pred_label: Binary label associated with pred_class (0 = paved, 1 = unpaved).

• osm_surface_class: Classification of the surface type from OSM, categorized as "paved" or "unpaved."

• combined_surface_osm_priority: Surface classification combining pred_label and surface(OSM) while prioritizing the OSM surface tag, classified as "paved" or "unpaved."

• combined_surface_DL_priority: Surface classification combining pred_label and surface(OSM) while prioritizing DL prediction pred_label, classified as "paved" or "unpaved."

• n_of_predictions_used: Number of predictions used for the feature length estimation.

• predicted_length: Predicted length based on the DL model’s estimations, in meters.

• DL_mean_timestamp: Mean timestamp of the predictions used, for comparison.

OSM features may have these attributes(Learn what tags mean here):

• name: Name of the feature, if available in OSM.

• name:en: Name of the feature in English, if available in OSM.

• name:* (in local language): Name of the feature in the local official language, where available.

• highway: Road classification based on OSM tags (e.g., residential, motorway, footway).

• surface: Description of the surface material of the road (e.g., asphalt, gravel, dirt).

• smoothness: Assessment of surface smoothness (e.g., excellent, good, intermediate, bad).

• width: Width of the road, where available.

• lanes: Number of lanes on the road.

• oneway: Indicates if the road is one-way (yes or no).

• bridge: Specifies if the feature is a bridge (yes or no).

• layer: Indicates the layer of the feature in cases where multiple features are stacked (e.g., bridges, tunnels).

• source: Source of the data, indicating the origin or authority of specific attributes.

Urban classification features may have these attributes:

• continent: The continent where the data point is located (e.g., Europe, Asia).

• country_iso_a2: The ISO Alpha-2 code representing the country (e.g., "US" for the United States).

• urban: Binary indicator for urban areas based on the GHSU Urban Layer 2019. (0 = rural, 1 = urban)

• urban_area: Name of the urban area or city where the data point is located.

• osm_id: Unique identifier assigned by OpenStreetMap (OSM) to each feature.

• osm_type: Type of OSM element (e.g., node, way, relation).

The data originates from OpenStreetMap (OSM) and is augmented with model predictions using images downloaded from Mapillary in combination with the GHSU Global Human Settlement Urban Layer 2019 and AFRICAPOLIS2020 urban layer.

This dataset is one of many HeiGIT exports on HDX. See the HeiGIT website for more information.

We are looking forward to hearing about your use-case! Feel free to reach out to us and tell us about your research at communications@heigit.org – we would be happy to amplify your work.

This dataset provides detailed information on road surfaces from OpenStreetMap (OSM) data, distinguishing between paved and unpaved surfaces across the region. This information is based on road surface prediction derived from hybrid deep learning approach. For more information on Methods, refer to the paper

Roughly 1.2175 million km of roads are mapped in OSM in this region. Based on AI-mapped estimates the share of paved and unpaved roads is approximately 0.1437 and 0.0911 (in million kms), corressponding to 11.805% and 7.4802% respectively of the total road length in the dataset region. 0.9827 million km or 80.7148% of road surface information is missing in OSM. In order to fill this gap, Mapillary derived road surface dataset provides an additional 0.0113 million km of information (corressponding to 1.1482% of total missing information on road surface)

It is intended for use in transportation planning, infrastructure analysis, climate emissions and geographic information system (GIS) applications.

This dataset provides comprehensive information on road and urban area features, including location, surface quality, and classification metadata. This dataset includes attributes from OpenStreetMap (OSM) data, AI predictions for road surface, and urban classifications.

AI features:

• pred_class: Model-predicted class for the road surface, with values "paved" or "unpaved."

• pred_label: Binary label associated with pred_class (0 = paved, 1 = unpaved).

• osm_surface_class: Classification of the surface type from OSM, categorized as "paved" or "unpaved."

• combined_surface_osm_priority: Surface classification combining pred_label and surface(OSM) while prioritizing the OSM surface tag, classified as "paved" or "unpaved."

• combined_surface_DL_priority: Surface classification combining pred_label and surface(OSM) while prioritizing DL prediction pred_label, classified as "paved" or "unpaved."

• n_of_predictions_used: Number of predictions used for the feature length estimation.

• predicted_length: Predicted length based on the DL model’s estimations, in meters.

• DL_mean_timestamp: Mean timestamp of the predictions used, for comparison.

OSM features may have these attributes(Learn what tags mean here):

• name: Name of the feature, if available in OSM.

• name:en: Name of the feature in English, if available in OSM.

• name:* (in local language): Name of the feature in the local official language, where available.

• highway: Road classification based on OSM tags (e.g., residential, motorway, footway).

• surface: Description of the surface material of the road (e.g., asphalt, gravel, dirt).

• smoothness: Assessment of surface smoothness (e.g., excellent, good, intermediate, bad).

• width: Width of the road, where available.

• lanes: Number of lanes on the road.

• oneway: Indicates if the road is one-way (yes or no).

• bridge: Specifies if the feature is a bridge (yes or no).

• layer: Indicates the layer of the feature in cases where multiple features are stacked (e.g., bridges, tunnels).

• source: Source of the data, indicating the origin or authority of specific attributes.

Urban classification features may have these attributes:

• continent: The continent where the data point is located (e.g., Europe, Asia).

• country_iso_a2: The ISO Alpha-2 code representing the country (e.g., "US" for the United States).

• urban: Binary indicator for urban areas based on the GHSU Urban Layer 2019. (0 = rural, 1 = urban)

• urban_area: Name of the urban area or city where the data point is located.

• osm_id: Unique identifier assigned by OpenStreetMap (OSM) to each feature.

• osm_type: Type of OSM element (e.g., node, way, relation).

The data originates from OpenStreetMap (OSM) and is augmented with model predictions using images downloaded from Mapillary in combination with the GHSU Global Human Settlement Urban Layer 2019 and AFRICAPOLIS2020 urban layer.

This dataset is one of many HeiGIT exports on HDX. See the HeiGIT website for more information.

We are looking forward to hearing about your use-case! Feel free to reach out to us and tell us about your research at communications@heigit.org – we would be happy to amplify your work.