Figure 1. |
Graphic. How agency traffic management centers integrate private sector data. |
Figure 2 |
Diagram. Examples of Waze event types and subtypes. |
Figure 3. |
Screenshots. Red boxes highlight the coverage differences in the Waze data versus the Virginia Department of Transportation data. |
Figure 4. |
Screenshot. Many agencies filter out Waze data that has a lower reliability level. |
Figure 5. |
Realtime Waze data integrated into the Regional Integrated Transportation Information System platform. |
Figure 6. |
Screenshot. Waze smartphone app. |
Figure 7. |
Chart. Waze events and vehicle miles traveled by State (excluding jams). |
Figure 8. |
Screenshot. A small portion of the MATOC Twitter monitoring system. |
Figure 9. |
Photo. The MATOC Operations room with TweetDeck prominently displayed on the upper-right media wall panel. |
Figure 10. |
Screenshot. The Denver Police Department uses the #Traffic hashtag to alert the public (and other agencies) about traffic events. |
Figure 11. |
Screenshot. Example of a crowdsourcing event. |
Figure 12. |
Screenshot. Utah Department of Transportation's Click'n Fix widget accompanies the Click'n Fix application. |
Figure 13. |
Illustration. Utah Department of Transportation's smartphone app empowers citizens and the agency to resolve maintenance and safety issues more quickly. |
Figure 14. |
Illustration. U.S. Department of Transportation connected vehicle and connected infrastructure concept. |
Figure 15. |
Illustration. The Pikalert concept. |
Figure 16. |
Diagram. Vehicle Data Translator Architecture. |
Figure 17. |
Map. Example trajectory data for a single trip. |
Figure 18. |
Illustration. Snapping waypoints to routes can sometimes be a challenge. |
Figure 19. |
Illustration. The CATT Lab's Origin-Destination Data Suite uses trajectory data to conduct midblock analyses. |
Figure 20. |
Screenshot. The CATT Lab's Origini-Destination Data Suite provides ranked intersection movements by zip code and date range based on trajectory data. |
Figure 21. |
Screenshot. Example data feeds. |
Figure 22. |
Screenshot. The Origin-Destination Analytics suite illustrates the origins for trips that passed over a very specific road segment. |
Figure 23. |
Screenshot. Example OpenStreetMap. |
Figure 24. |
Screenshot. Example of OpenStreetMap data in XML format. |
Figure 25. |
Screenshot. License rules for OpenStreetMap. |
Figure 26. |
Screenshot. The Virginia Department of Transportation 511 home page. |
Figure 27. |
Screenshot. Example of a MapBox map visualizing trees in New York City. |
Figure 28. |
Screenshot. Inputs panel on the Waze Map Editor. |
Figure 29. |
Screenshot. Google Map. |
Figure 30. |
Screenshot. Google StreetView. |
Figure 31. |
Screenshot. Example routing result code from Google Maps. |
Figure 32. |
Diagram. Toll tag travel time calculation. |
Figure 33. |
Screenshot. Probe data provides ubiquitous coverage. |
Figure 34. |
Screenshot. Bottleneck ranking. |
Figure 35. |
Screenshot. Trend map compares performance before, during, and after a major event. |
Figure 36. |
Screenshot. User delay cost resulting from a major event. |
Figure 37. |
Screenshot. Example of a performance dashboard travel time widget. |
Figure 38. |
Screenshot. Example performance report. |
Figure 39. |
Screenshot. Example of an interstate travel forecast for the Baltimore, MD region during the week of Thanksgiving in 2016. |
Figure 40. |
Screenshot. Example of INRIX traffic management center-based metadata. |
Figure 41. |
Screenshot. Example speed and travel time data. |
Figure 42. |
Screenshot. Extreme Definition metadata. |
Figure 43. |
Screenshot. Example speed and travel time data for Extreme Definition format. |
Figure 44. |
Screenshot. HERE speed data in Orlando, FL. |
Figure 45. |
Screenshot. Example HERE traffic message channel per-lane data. |
Figure 46. |
Screenshot. Example HERE sub-segment per-lane data. |
Figure 47. |
Screenshot. Example TomTom data. |
Figure 48. |
Illustrations. Examples of point clouds and Asset Mapping. |
Figure 49. |
Illustration. Deep learning object identification presented. |
Figure 50. |
Illustration. Third-party, connected-vehicle events from the Washington, D.C. region. |
Figure 51. |
Screenshot. A California Highway Patrol computer-aided dispatch message. |
Figure 52. |
Screenshot. Prince George's County Maryland computer-aided dispatch system message. |
Figure 53. |
Screenshot. California Highway Patrol computer-aided dispatch log example. |
Figure 54. |
Diagram. Virginia Department of Transportation Realtime Traffic Incident Management Information System high level architecture diagram. |