This article is for our Arizona clients who are using the DOT's ALISS / ACIS system for their Crash Magic database.
With the redesign of the ADOT crash form some fields were preserved, and others were removed or consolidated. During this process, new lookup values were added to ADOT's database to standardize and accommodate for the changes to the form. ADOT will not be converting old data to match with the new format, some fields and or values could be blank. ADOT's internal database lookup values DO NOT MATCH with the current crash form.
Reference for editing
Arizona DOT provides data to jurisdictions to use with Crash Magic. If you would like to request this data, you will need request access and fill out a contract with the DOT, that information is provided below.
Crash data can be imported from many sources. This article describes the case where the data is provided as an ASCII file or other files that can be read by MS ADO such as MS Access or DBF.
Crash data can be imported from many sources. This article describes the case where the data is provided as an XML file. If your data is being provided in XML format, you also have the option to FTP the data to our servers rather than using the browser interface. That process is described in the Automated import using FTP knowledge base article.
In Arizona, crash data is available to participating agencies through the ALISS Safety Data Mart. By following the steps included here, you can create data files suitable for import into Crash Magic.
Each year, Pd' Programming attends the AZ Spring ITE-IMSA conference. Sometimes we also hold user group meetings or trainings. Let us know what you might be interested in. Please respond by this Friday, Jan 13. Thanks!
Clients using data from ADOT cannot create accurate corridor studies.
The State of Arizona has created a new form for reporting crashes. This article describes changes that have occurred that will affect your crash data in Intersection Magic.