Detailed information on atypical driving events on your road network
Based on millions of connected drivers, understand where and when road safety issues may arise by seeing atypical driving events alongside past crash data.
All information is easily integrated into geographic information systems, enhancing other data sets without requiring additional software.
Justify and allocate the right resources at the right time and place based on easily measurable safety information.
Monitor and quickly validate your actions through before / after analysis that you create directly on your GIS.
We offer 5 main events, potentially indicative of a near miss incident:
Our add-on service allows you to get detailed information on individual driving events such as:
And much more…
Combining expertise in data analysis and driving behavior, MICHELIN Mobility Intelligence creates solutions to go beyond crash data reports allowing you to act before they happen. Leveraging millions of connected vehicles and using machine learning and proprietary algorithms, our services allows road safety officials to detect, locate and assess atypical driving behaviors indicative of potential near miss incidents.
Critical insights that to go beyond past crash data. With near miss data comes the potential to identify risky zones and act before crashes occur to reach vision zero goals.
TitleDescriptionTypearc_index_hashArc Key for road map matched with OpenStreetMap. Linestring which designs a portion of the road with a specified direction. An arc can be referenced with a point of interest like a Stop or a Yieldstringmonth_start_dateMonth aggregationdatecontext_week_periodWeek Context aggregation. Depends on the day of week that the event(s) occur(s). Weekends are Saturday and Sunday, all other days are designated as Week.stringcontext_weather_simplifiedWeather Context aggregation. We use the the rain precipitation. If it’s greater than 0 we consider that it’s raining. Otherwise it’s considered Dry.stringcontext_solar_condition_simplifiedSolar context aggregation. We use the solar position calculated by the GPS position and timestamp: DAY and NIGHT.stringevent_typeEvents occurring during trips with intensities above the observed norms. If empty, no event occured on the arc during context combinationstringevent_levelEvent intensity calculated base on speed and acceleration variation and durationstringEvent_DateThe date and time of the event occured. This field is only filed for SUSPECT_COLLISION Event Type.DateTimenb_eventsThe number of events occurred for associated contexts. For Suspected Collision Event type, this value is 1.integerarc_geom_wktArc geometry (WKT format). First point represents the start of the line and the last point represents the end. It models the part of road (by a line) where events appear (https://wiki.openstreetmap.org/wiki/Way#Open_way_.28Open_polyline.29).stringarc_lengthArc length (in meters)decimalcountry_codeCountry codestringcountry_nameCountry namestringdepartment_or_county_codeCounty code. GNIS Code.stringdepartment_or_county_nameCounty namestringzip_codeZip codestringcity_nameCity namestringStateState namestringState_idState identifierstringroadtype_groupRoad Type Group defines the type of road.stringroadpriorityRoadPriority of the roadsintegerroad_name_european_or_interstateColumn for Interstate Highwaysstringroad_name_highwayColumn for US routesstringroad_name_region_or_stateColumn for State Routesstringroad_nameColumn for Road Namesstringroad_name_department_or_countyColumn for County Routesstringroad_name_national_or_federalColumn for Federal Roadsstring
