The Collision Diagram Wand is unique. Unlike Intersection Magic, Crash Magic and the other applications distributed by Pd' Programming, the Magic Wands components are designed to be used 'a la carte'. As a result, data that would be needed to identify crash locations; match GIS data; identify corridor information; etc. are not required.
However, there are still a number of pieces of data required by the component in order to render a proper diagram.
Note: In addidition to the required fields, it is often appropriate to include other fields relevent to analysis of the diagrams. These fields can be used for labeling and filtering. If this is not already handled by the calling application.
Diagram Wand Field Recommendations:
There are no specific data types required when using the Diagram Wand. It is possible to configure the program using text or numeric fields. However, any text fields must be consistant in order to produce reliable results. Non-validated, free-form data entry is not conducive to producing quality diagrams. Also, while BLOBS, CLOBS and other large format fields are supported by Wands, they should not be used for these requiered fields. The ideal structure is numeric or short text fields drawn from a validated lookup table.
Fields that are absolutely required to generate a minimal diagram:
Unique crash field name(s): A field or list of fields that can uniquely identify a crash within the entire database. This is used to be able to reference crashes within the diagram, as well as to provide feedback when "clicking on" a diagram graphic to obtain more information.
Direction of travel for each of the first 3 vehicles involved in the crash. Direction of travel is used to place the crashes on the diagram schematic. It is also used to align the graphic arrows within the collision graphic.
Fields that are required for an accurate, readable diagram:
Type of collision field that indicates that a collision was a sideswipe or rear-end. This is used when the first two vehicles are traveling in the same direction. Without it, all such crashes are rendered as rear-end collisions.
Vehicle movements for each of the first two vehicles involved in the collision. Values such as "left turn", "slowing", "backing", "straight", etc. are used to create the appropriate arrows for each graphic. Without this information, all vehicles will have to be represented with straight arrows.
Fields that are strongly recommended in order to properly annotate each collision graphic:
Crash severity. Used to render an injury or fatality symbol associated with a collision graphic. This field should indicate at least "property damage"; "injury"; "fatality" across the entire crash. (i.e. all vehicles combined) A less convenient means of determining this is by examining each vehicle individually.
Indication of pedestrian, bicycle or fixed object. Used to to render an appropriate annotation to the graphic. If these values are represented as vehicle types, and given direction and movement, a more accurate diagram can be created. Otherwise the graphic is simply located in front of the first vehicle with no indication of direction or movement.
Lighting condition. Used to render a "nightime" symbol associated with the collision graphic.
Driver or DUI condition(s). Used to a render DUI annotation on the crash, or for each appropriate vehicle.
Date field. Typically used for labeling graphics, also used for filtering and when a crash is clicked on.