We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Crash Data Sample Clauses

Crash Data. WSB will utilize MnDOT’s CMAT website to collect and summarize crash rates for the intersection. This information will be included in the ICE report.
Crash DataThe CONSULTANT will obtain the most recent five (5) years of available data from the DEPARTMENT's crash database and other local sources for this Project. The crash data will include the number and type of crashes, crash locations, number of fatalities and injuries, and estimates of property damage and economic loss.
Crash DataThe consultant shall analyze the crash data for the latest three-years available to identify discernible crash patterns. The consultant shall also develop collision diagrams intersection/ corridor using any automated crash mapping tool. Such automated tool shall be presented to the FDOT project manager for approval prior to utilizing it for any project. The consultant shall also develop and implement a QA/QC process for automated collision diagrams. At a minimum the consultant shall create the following histograms and tables as part of the crash analysis: • Crashes by type • Crashes by contributing cause • Crashes by time of day • Crashes by lighting condition • Crashes by surface condition • Crashes by weather condition • Crashes by day of the week • Crashes by month of the year • Crashes by age group at fault • Crashes by alcohol/drug involvement • High crash spots • High crash segments • Crash summary by type • Crash summary by contributing cause • Crash summary by location
Crash Data. Stantec engineers will request collision information for the study intersections. 4) Forecasted Traffic Volumes: Stantec will review recent traffic studies and establish projections of traffic based on the Town’s Comprehensive Plan and data available from NCTCOG and TxDOT for the area to determine short- and long-term traffic volume forecasts for the intersection after Legacy is extended.
Crash Data. Provide pertinent motor vehicle crash data (fatalities and injuries) for each of the previous three (3) years.
Crash Data. For crash related data, the type of motor vehicle, its configuration and identifiers are also provided, alongside crash details containing the count of injuries, fatalities, vehicles involved and outcome containing but not limited to Hazmat involvement, towaway or citations were issued to said driver. Crash inspection data provides location, weather conditions, road surface conditions and light conditions pertaining to the crash incident.
Crash Data. The MPO shall provide technical resources and data.
Crash Data. The Branch completed a two-year staff supplement contract that employed 16 temporary staff to eliminate the crash-records quality review and assurance backlog of 3.5 years. At present, all historical on-system crash records are processed and available for use. Currently received crash records in 2012—both on and off-system—are processed within four months of receipt from the Department of Revenue. The only remaining backlog is for the 2008-2011 off-system crash records, which will be processed once the Future Staffing of the Traffic Records Unit is addressed and resolved by Management. The Branch is working to achieve all current records with our permanent staff supplemented by a small group of temporary staff who will be with us until late 2013. Prior to their departure CDOT will develop a staffing model to implement in order to keep crash record processing—both for on-system and off-system crashes—within the safety performance measure of six months or less. Colorado does not have a primary seat-belt law. This actually comes from the Governor's Office to FHWA, not through OTS. Colorado is in compliance. Colorado is in compliance.

Related to Crash Data

  • Device Data We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.

  • User Data We will maintain certain data that you transmit to the Services for the purpose of managing the performance of the Services, as well as data relating to your use of the Services. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Services. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.

  • Customer Data 8.1 You, not bookinglab or JRNI, have sole responsibility for the entry, deletion, correction, accuracy, quality, integrity, legality, reliability, appropriateness, and right to use the Customer Data. bookinglab and JRNI is not responsible for any of the foregoing or for any destruction, damage, loss, or failure to store any Customer Data beyond its reasonable control or resulting from any failure in data transmission or operation of the Booking Service by you. 8.2 As of the MSA Start Date, JRNI is certified under ISO 27001 and shall maintain an information security program for the Services that complies with the ISO 27001 standards or such other standards as are substantially equivalent to ISO 27001. 8.3 If JRNI and/or bookinglab processes any Personal Data on your behalf when performing its obligations under this Agreement, the Parties acknowledge that you shall be the Data Controller and JRNI and/or bookinglab shall be a Data Processor and in any such case: (a) you shall ensure that you are entitled to transfer the relevant Customer Personal Data to JRNI and/or bookinglab so that they may lawfully use, process and transfer the Customer Personal Data in accordance with this Agreement on your behalf; (b) you shall ensure that the relevant third parties have been informed of, and have given their consent to, such use, processing, and transfer as required by all applicable Data Protection Laws; (c) each Party shall take appropriate technical and organisational measures against unauthorised or unlawful processing of the personal data or its accidental loss, destruction or damage; and (d) notwithstanding any other provision of this Agreement, but subject always to Appendix B(1) Data Protection and B(2) Data Processing Activities, nothing shall prevent JRNI or bookinglab from disclosing Customer Personal Data or Customer Data to their Group Companies, Affiliates and third party service providers as necessary to provide the Services in accordance with clause 3, and otherwise in order to comply with Applicable Law or at the request of a governmental, regulatory or supervisory authority. 8.4 From the MSA Start Date the Parties shall comply with Appendix B(1) Data Protection and Appendix B(2) Data Processing Activities 8.5 ensure that Customer Data and Personal Data deemed as a special category of Data under GDPR is not given to us in any form unless pre-agreed by us in writing 8.6 You are solely responsible and liable for any transfer of Customer Data made by you (or made by JRNI or bookinglab at your request) from the Booking Service to a third party and for ensuring that such transfer is in compliance with the Parties' obligations under the Data Protection Laws.

  • Sensitive data Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Site Data (i) The Contractor shall be deemed to have inspected and examined the Site and its surroundings and to have satisfied himself before entering into the Agreement in all material respects including but not limited to: (a) the form and nature of the Site (including, inter-alia, the surface and sub- surface conditions and geo-technical factors); (b) the hydrological and climatic conditions; (c) the extent and nature of the works already completed and Materials necessary for the execution and completion of the Works and the remedying of any defects that includes already executed part also. (d) the suitability and the adequacy of the Site for the execution of the Works; (e) the means of access to the Site and the accommodation the Contractor may require; (f) arranging permits as required as per [.] of the Agreement. (g) the requirements of operation and maintenance; and (h) all other factors and circumstances affecting the Contractor's rights and obligations under the Agreement, the Contract Price and Time for Completion.

  • Licensee Data Licensee acknowledges and agrees that Licensee will be solely responsible for backing-up, and taking all appropriate measures to protect and secure, Licensee Data. Licensee acknowledges that Nuix may make, store and maintain back up copies of Licensee Data, but is not obliged to do so. Nuix will not be liable for any loss or corruption of Licensee Data.

  • Client Data The Subrecipient shall maintain client data demonstrating client eligibility for services provided. Such data shall include, but not be limited to, client name, address, income level or other basis for determining eligibility, and description of service provided. Such information shall be made available to Grantee monitors or their designees for review upon request.

  • Data The statistical, industry-related and market-related data included in the Registration Statement and the Prospectus are based on or derived from sources which the Company reasonably and in good faith believes are reliable and accurate, and such data agree with the sources from which they are derived. The Company has obtained the written consent to the use of such data from such sources to the extent necessary.

  • Customer Materials Subject to Section 4(a), all right, title and interest (including all Intellectual Property Rights) in and to the Customer Materials are owned by Customer or Customer’s suppliers.