This page gives information regarding the Passenger Only data entry form for Colorado DR3447.
If you are importing data, please contact us before editing data with the Crash Magic data entry program. Otherwise any changes may be lost with a future import.
If you are only doing data entry into Crash Magic (no importing), you must include all passengers that had any injury on this form.
Knowledge Base
Crash Magic Online > Data
Crash Magic provides a lot of analysis tools that can be helpful to planners and engineers. However, like any software, we can't do it all. This article provides one method for sending some data from Crash Magic to another program for further analysis or reporting. Specifically, we will specify a list of fields and select them for export to a CSV, Excel or KML file.
This page gives information regarding the new DR3447 data for the technical user.
The State of Arizona provides access to their crash data through a Citrix (remote desktop) portal. In order to download data, a user must log in to a Citrix remote desktop; access the ACIS website; and initiate a download of the data to your local computer.
Note: This document is provided as-is. Pd’ Programming does not have special knowledge of or direct access to the ACIS system. We have captured the screens below with the assistance of a local agency that does have access. Please follow any instructions provided by the DOT.
Crash Magic hosted on GovernmentTools.com provides a number of options for importing new crash data. This article describes those options.
Colorado has adopted a new crash report form DR 3447. As agencies slowly move over to the new form, we will be updating Crash Magic with a new configuration to match.
Directions for adding and deleting Aliases in Crash Magic.
With the updates to Crash Magic, also came an update to the data entry / edit program.
Crash Magic users selecting a date field my see the wrong time associated with the date, and users selecting a time field may see the wrong date with the time field.
Crash Magic GIS Services require spatial database functionality. This article describes requirements for Oracle database servers.
Crash Magic will generate an error when rendering a diagram that indicates there is a duplicate case number. This is a little misleading because the program is not capable of importing a duplicate record into the database. In reality, this error more than likely means that there is an error in a crash record that is causing our query to generate multiple rows for a single crash. A common example is when a crash has two drivers for the same vehicle.
In order to read and/or compare XML files it can be handy to format them in a common way. This article describes one method for doing this. It relies on a free 3rd party product that needs to be downloaded first.
Selecting a street where a collision occurred does not allow the user to select the cross street
When Crash Magic Online is first set up user may not have any streets available to select in the street selectors of a study
Users upgrading their configuration may receive the error EcmRA_Base: RALoadDEDefinition EcmRA_Analysis: Failed to load data entry definition PSRattr (Name of data entry definition)