custom applications knowledge centers products ontrac corporate contact us  


 
 
OnTRAC Collision FAQS You are in: TRIMAP > products > ontrac > collision faqs

  1. Who is using it?
  2. How has it evolved?
  3. What is happening now?
  4. Does it integrate traffic volume data?
  5. How do you ensure that estimates of volume exist for all links and nodes in the road network?
  6. How are network evaluations completed?
  7. How is the map functionality provided?
  8. Can I use my maps?
  9. Can I salvage my historic data?
  10. What happens if I get my raw collision data from someone else?
  11. How can I share my information with others?
  12. Where can OnTRAC be implemented?
  13. What is involved in a typical deployment?
  14. What issues can be expected in typical deployment?
  15. Can I deploy this application as a hosted and managed solution?

  1. Who is using it?

    The OnTRAC system is based on original research completed by a TRIMAP founder, based on his experience deploying a solution used by the Metropolitan Toronto Police Department in the City of Toronto.

    OnTRAC has been deployed in the Region of Durham and the Cities of Ottawa, Brampton, Winnipeg, Sault St. Marie, Sudbury and Vaughan. It has also been used by the City of Winnipeg Police Department and the Manitoba Public Insurance Corporation. It is currently being deployed in the City of Calgary.

    >> top

  2. How has it evolved?

    The first version of OnTRAC introduced in 1998 captured coded data from the standard Ontario police accident report form. It was a map-enabled application that provided standard adhoc reporting, and querying functionality. It also enabled users to create a detailed scene diagram for a specific collision. A tool was created to import historic data and manage this information within a relational database model.

    In 1999, OnTRAC was enhanced to include the ability to generate a comprehensive publication-quality annual report. Other enhancements included a comprehensive quality assurance program, the ability to view raster data as well as vector map data, comprehensive intersection analysis-related functionality and advanced adhoc query functionality using the ability to create and manage SQL queries. It also provided functionality where raster images such as scanned images of the typical collision report form could be managed. OnTRAC was also deployed in an environment where the back-end relational database was Oracle.

    In 2000, OnTRAC was modified to capture coded data from the standard Manitoba police accident report form. It also integrated with OnTRAC Traffic Volume application that generates annual ADDT values, by year, for all links and nodes in the road network. This allowed customers to complete evaluations using more complex analyses techniques. Other functionality was developed that facilitated the import of data coded captured using other text-based systems and the ability to append spatial references to this type of collision data.
    >> top

  3. What is happening now?

    At this time, we are working on development of browser-based solution that can be deployed as web-based solution. This involves a GIS vendor-neutral solution for data capture and standard analysis, detailed network evaluations based on safety performance functions and improvements to how data can be communicated to a larger audience of stakeholders.
    >> top

  4. Does it integrate traffic volume data?

    Traffic data can be managed within the OnTRAC application or be imported from other systems. In the latter case, users must ensure that the traffic volume data is spatially referenced using the same base map used by OnTRAC.
    >> top

  5. How do you ensure that estimates of volume exist for all links and nodes in the road network?

    As part of configuring OnTRAC, we typically lead a process where users reference all sources of their traffic volume data and then generate estimates of traffic volume for each segment. Once this is completed, volume estimates for each intersection in the road network are made as part of an automated procedure.
    >> top

  6. How are network evaluations completed?

    Users have a range of tools available to evaluate safety issues on the road network. To target enforcement-related programs, they may choose to identify locations based on the simple frequency of collisions. Where traffic volume data is available, rate reports may provide a better indication of where problems may exist. Where the road network can be classified in other ways (traffic volume, road class and other similar characteristics), OnTRAC can be used to group similar locations to evaluate how a specific location may be performing. Where more advanced analyses are desired, reports based on safety performance functions and other analytical techniques can be generated. In addition, users can also select collisions they are interested in based on almost any collision or network-related criteria.
    >> top

  7. How is the map functionality provided?

    MapInfo’s MapX product is used to deliver the map-related functionality in the client-server based OnTRAC product. TRIMAP’s vgMapper product is used to deliver the map-related functionality in the Web-based version of OnTRAC.
    >> top

  8. Can I use my maps?

    Vector-based street centre line maps are the core of the OnTRAC product. OnTRAC has successfully been deployed in environments where the maps are created and updated using products from MapInfo, ESRI and Intergraph. The application can also utilize additional map data that may be available such as raster data in MrSID format or other basemapping-related information.
    >> top

  9. Can I salvage my historic data?

    As part of configuring OnTRAC, we often lead a process where historic data is salvaged. In most cases this means converting historic text-based data into OnTRAC’s relational database model. Several other automated and manual techniques are used to spatially reference historic data based on the best available current information.
    >> top

  10. What happens if I get my raw collision data from someone else?

    Collision data can entered directly within the OnTRAC application. As part of this process, new collisions are spatially referenced and go through a comprehensive validation process. Collision data can also be imported from other systems as part of a batch process. In this case, data is uploaded, parsed and converted into OnTRAC’s relational database structure. Other functionality is provided to validated and spatially referencing this data.
    >> top

  11. How can I share my information with others?

    The recommended solution to being able to share information with a range of different stakeholders is to deploy the new Web-based version of OnTRAC. This allows maximum flexibility and functionality to be delivered.
    >> top

  12. Where can OnTRAC be implemented?

    OnTRAC can be implemented in a number of different ways. It can be deployed within a police environment or be deployed within a road authority. The road authority (typically a City's transportation engineering department) may either use the OnTRAC application to capture all information contained in the police accident report or data may be imported from other sources where the text-based data is captured. In the latter example, use of the OnTRAC application would be limited to spatially referencing an incident that has previously been coded.
    >> top

  13. What is involved in a typical deployment?

    As part of the deployment of OnTRAC, resources are typically spent on licensing of the OnTRAC Collision System; installation, user training, administrator training; creation and validation of appropriate basemaps and lookup tables; conversion, spatial referencing and validation of historic data; customization, minor modifications and validation of the reporting functions; and integration of traffic volume and road infrastructure data. Several options are available to appropriately service the OnTRAC application. The most applicable method is typically determined as part of discussions with each client on a case-by-case basis.
    >> top

  14. What issues can be expected in a typical deployment?

    A fundamental component of the OnTRAC is the ability to spatially reference, query and display collision information using a map. This provides an unparalleled opportunity to understand the distribution of collisions within a jurisdiction. It also allows users to readily integrate other sources of data describing the road network and its use. By combining data describing the infrastructure and traffic volume, users have the ability to address issues such as exposure to risk and use multiple techniques to evaluate the safety performance of the network. An issue associated with this ability is that a process must be in place to integrate data sources and manage the process of how the environment changes. This involves the map editing and change control process. To deal with this issue, we have addressed many possible difficulties as part of the overall design of the application, we have developed supplemental tools and we also have defined business processes that will ensure that the application is maintainable and supportable over time.
    >> top

  15. Can I deploy this application as a hosted and managed solution?

    Yes. To address training issues, minimize the cost of an overall application and provide a solution to a process where base maps are updated and changed, OnTRAC can be delivered as part of a hosted and managed solution. Details of this model must be defined on a case-by case basis with an OnTRAC user.
    >> top



accident analysis, accident investigation, accident reconstruction, accident record, arcview, asset management, autocad map, automated mapping, collision analysis, collision diagram, collision investigation, collision reconstruction, collision record, crash record, crime, damage, development, diagramming software, digital map, eai, electronic map, ems, esri, fatal, fatalities, fatality, fleet, gba master series, geographic information system, geomedia, gis, hansen, highway, highway safety, hsa, ims, infrastructure management, injury, intelligent map, intergraph, intersection, investigate, investigation, investigators, itx stanley, law enforcement, magic, mapinfo, mapobjects, mapping, mapscenes, mapx, mj harden, mv, ontrac, ontrac2, orthophoto, orthophotos, police software, policing, psi, public safety, public works, reconstruction, rqc, sheriff, sheriffs, spatial analysis, spatial attributes, spatial data, svg, traffic accident, traffic investigation software, traffic safety, transportation, trimap, truck, vector graphics, vehicle