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.
User should be able to provide Pd' Programming access to their collision data. This can be done by uploading a copy of the database to our web site, providing access through a VPN connection or in the case of hosted solutions the files to be imported(.txt, .csv and .del files must have header rows that label each field). The data at a minimum should contain a years' worth of collision data. A sample of hard copy collision reports are also required to confirm that collision diagrams are being displayed correctly.
While most databases are self documented through table names and field names the following information must also be provided for a Crash Magic configuration:
The following information would enhance collision diagrams in Crash Magic:
In addition to the database of files we also request reports from the data for the configuration:
These reports will be compared to the Crash Magic output to ensure they are being correctly rendered.
© 1999-2019 Pd' Programming, Inc -
Lafayette, CO USA