Required and Recommended fields

Crash Magic was designed with the idea that collision data would not have to be modified to support the program, but some fields are required for analysis.

Required Data Structure:

Collision diagrams and studies in Crash Magic require a single record per collision. To accomplish this Crash Magic uses queries that flatten collision data from multiple tables into a single record for each collision. This means that a query must be able to extract collision information, vehicle one, vehicle two, vehicle three, pedestrian one, cyclist one and environmental information into a single crash record.

Data fields:

Crash Magic has no requirements for specific data types from collision data. It is possible to configure the program using text or numeric fields. However, any text fields must be consistent in order to produce reliable results. Non-validated, free-form data entry is not conducive to producing quality diagrams and reports. For example it can be impossible to determine a vehicle direction from an officer notes field. While large format fields are supported by Crash Magic(BLOBS and CLOBS), they should not be used for the required and recommended fields. The ideal structure is numeric or short text fields drawn from a predefined set of values like a 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 across the entire set of data(Primary Key). 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.

•Date: Date the collision occurred

•Location of crash (at least one of the following - all can be used simultaneously):

✓Primary and nearest cross street names: This is the most common means of identifying locations in urban and rural city settings. Jurisdiction information may be required for analysis on multiple locations with the same name. (For example jurisdiction information would be required for a database that contains information from the cities of Denver and Boulder, and both cities have an intersection location named Broadway and Arapahoe).

✓Intersection node number: This must be a unique value that identifies a specific collision location.

✓Route and Mile marker: Usually used in county or state DOT agencies

✓Street and hundred block: Usually used in urban settings as a supplement to "Primary and nearest cross street names".

✓XY coordinates: The XY location (Latitude and Longitude) for a collision.

•Vehicle sequence Crash Magic must be able to identify the first and second vehicles involved in a collision.

•Direction of travel for each of the involved vehicles.

Fields that are absolutely required to generate a minimal diagram:

•Type of collision: Is a field that indicates 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:

•Time of the collision: Users will not be able to use standard time charts without this field.

•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 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 with bicycle and pedestrian collisions. Otherwise a pedestrian or bike symbol is simply located in front of the first vehicle with no indication of direction or movement.

•Lighting condition: Used to render a "nighttime" 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.

Additional useful information:

•Distance and direction from the nearest cross street: These fields are used to place crashes in the appropriate positions in the diagram.  Without it, many assumptions need to be made about vehicles in or near an intersection.

•Lookup tables or files: These tables/Files will be used to convert raw data values to user readable values.

•Collision images: Scanned images of police reports, collision photos, and collision location photos can be included within Crash Magic.

•Roadway section order:  The creation of corridor diagrams schematics requires information to place roadway sections in their correct order. Street milepost studies order roadway sections by tenth of a mile sections based on the milepost number. Street address corridors order roadway sections by 100th block based on the block number.

•List of engineer-desired fields to be shown: Crash Magic diagrams and reports can be customized to display a default list of fields.