![]() |
| Environment | |
| Environmental Review Toolkit | |
| Home | Planning and Environment | NEPA and Project Development | Accelerating Project Delivery | Historic Preservation | Section 4(f) | Water, Wetlands, and Wildlife | |||||||||
|
Module 2: Statewide and Regional Planning Approach and Data NeedsCOLLECT STATEWIDE AND REGIONAL DATACollecting accurate data on the magnitude, trend, location, and type of WVCs can help to document the need for mitigation strategies and establish a procedure for prioritizing potential mitigation locations. Gathering data on collisions and wildlife movement is the best way to ensure that appropriate mitigations will be installed at the locations of greatest impact. WVC data are crucial to justify and prioritize mitigation locations. Module 6 describes strategies for monitoring installed WVC mitigation measures. Where to Find Crash DataThere are three primary sources of WVC data, including: 1) animal carcass counts; 2) insurance data; and 3) crash reports. Insurance data can provide information about the magnitude of the problem but these data are not spatially referenced and are rarely used on a local level. A good example of a carcass data collection program is the Maryland Department of Transportation's (MDOT) Large Animal Removal Reporting System (LARRS) program. The LARRS program is implemented and administered on a "top-down" basis to provide consistent, department-wide standards. Questions regarding carcass collection are included as part of a more extensive form that maintenance workers are required to complete for general maintenance tasks, increasing the likelihood of capturing the data. For more information on the Maryland LARRS carcass data collection method, contact William Branch (MDOT) at (410) 545-8626 or WBranch@sha.state.md.us.
Crash data from police crash reports and statewide crash databases are readily accessible and spatially referenced. Standardized reporting and recording methods make crash data fairly uniform within a State.
To provide feedback, suggestions, or comments for this training, contact Bill Ostrum at 202-366-4651 or at william.f.ostrum@dot.gov. |
|||||||||||