For many years, traffic management systems (TMSs) have shared still images of traffic cameras with the public to support sharing travel-condition information. More recently, this practice has evolved into providing live streaming videos. Meanwhile, individuals and private companies have begun recording these video streams along with the state’s 511 data feeds. Using various software and technologies, these third parties extract and resell information on notable events (e.g., dramatic crashes) to television media, social media, and others (e.g., wholesale purchasers of large quantities of recorded video).

Given this evolving trend, it is increasingly important for agencies to consider the potential implications of third-party use of traffic video and traveler information data. These considerations should inform the development and review of regulations, policies, procedures, legal frameworks, and operational decisions around data sharing. Agencies must also anticipate possible downstream impacts, such as increased public records requests or the need to respond to legal inquiries when video is recorded and archived, considering the Freedom of Information Act (FOIA).

Most TMSs do not record videos from their traffic cameras because of concerns about the administrative burden of responding to information requests, risk of a sensitive information leak, potential liability from information misuse, and complications sharing data with other government entities (e.g., law enforcement). Additionally, states have seen dramatic increases in the telecommunication and data storage costs involved with receiving, saving, sharing, and managing video from traffic cameras.

This project aims to provide guidelines for agencies’ decision-making regarding whether and how to share, enhance, or discontinue sharing TMS traffic video with the public or third parties. The range of issues to be covered may include the following:

·       The objectives, requirements, and performance measures for TMS traffic monitoring and surveillance functions;

·       TMS traffic monitoring and surveillance functions for operational strategies and other functions, actions, and services supported by TMSs;

·       A range of agency regulations, policies, procedures, and issues associated with collecting, archiving, using, and sharing video collected by TMS cameras (e.g., enforcement actions);

·       Other legal, policy, or institutional challenges that may limit unauthorized and unintended use of traffic camera video collected by TMSs and lessons that can be learned from other industries (e.g., public transportation) to help protect personally identifiable information (PII) and limit the access for unauthorized and unintended use (e.g., prevent or time out video feeds to third-party recording, technologies to screen sensitive information such as license plates);

·       Issues to consider in support of linking agency policies and procedures with sharing video and the requirements and performance measures in the procurement and selection of surveillance cameras and the associated video;

·       The options and considerations (e.g., cost, bandwidth) involved in evaluating and selecting different methods for agencies to share video with various third-party interests (e.g., emergency service providers, other public agencies, the general public); 

·       Emerging technologies, methods, or techniques (e.g., video anonymization, facial blurring, redaction techniques) that agencies may implement to ensure PII is addressed prior to sharing any videos;

·       Issues to consider if TMSs do not share traffic surveillance video in support of sharing video in response to the FOIA requests to ensure released information complies with agency regulations, policies, and procedures and does not contain any PII or other information unique to individuals or vehicles; and

·       Technologies, methods, or techniques that agencies are using to automate and streamline responses to requests for video from TMSs.