Description:
The TCLS is a module of MS2’s cloud-based Transportation Data Management System (TDMS). It is both a software application and database. For agencies, the TCLS helps store and manage traffic crash data within their jurisdictions. Spatial information is mapped and monitored to reveal crash trends along road segments and at intersections. The TCLS is a tool for the management of the following:
- Crash data processing (entry/geocoding)
- Crash data details
- Scanned police reports
- Intersection and road segment listing
- Crash rate calculation and reporting
- Severity rate calculation and reporting
- Automated intersection collision diagram
- Spatial maps that illustrate crash patterns
- Sharing of crash data and analytics
The TCLS also allows agencies to share the data with stakeholders including the public. With many agencies having used this tool for managing and sharing their data, it also serves as a database for users to collect data for safety analyses.
Tool Type:
DatabaseSoftware
Owner Source:
private_company
Sponsor/Owner:
- MS2
Published:
Availability:
The information guide is free of charge at the following link: Traffic Crash Location System (TCLS)
It can be used as a data sources and data collection tool at the following link:
MS2’s Client (select agency for available data)
Related Resources
MS2 Transportation Data Management System: This brochure provides a brief introduction of MS2, its products and their functionalities, including TCLS.
Disclaimer:
This information is disseminated under the sponsorship of the U.S. Department of Transportation in the interest of information exchange. The U.S. Government assumes no liability for the use of the information contained herein. This information does not constitute a standard, specification, or regulation. The U.S. Government does not endorse products or manufacturers. Trademarks or manufacturer's names appear in this information only because they are considered essential to the objective of this publication.
Any opinions, findings, and conclusions or recommendations, and translations thereof, expressed in this publication are those of the author(s) and do not necessarily reflect the views of the Federal Highway Administration.