This article shows how to locate invalid time information in Intersection Magic
This article covers how to create a copy of the Intersection Magic database
Intersection Magic version 126.96.36.199 introduced new functionality to protect your data from incorrect entries in your streets changes file. The program will not process your street changes file when a problem is detected.
Some users may need to sort the files that are being imported. This article was created to show how to sort a file.
This article is a reference for users that import SWITRS data into Intersection Magic
Intersection Magic has been designed to support a wide variety of data formats. This data may originate on a mainframe, mini, or micro computer. In some areas data may be obtained directly from the state, California, Iowa, Oregon, Arizona and Idaho to name a few. In other areas, data is stored at police departments on mainframes. In still others, data is maintained on PC database programs. Intersection Magic supports all of these cases. This article describes the various options and requirements for preparing data to import into Intersection Magic.
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.
The State of Colorado has created a new form for reporting crashes. The new form is in effect as of 7/1/2006. This article describes changes that have occured that will probably affect your use of crash data in Intersection Magic.
To claify the behavior for Intersection Magic during Import.
We would like users to be able to take advantage of a new way to backup and copy their configurations.
This describes how to use the new Pd Data Extractor.
Some IMW configurations require that multiple ascii files be specified for import. When a configuration of this type is loaded (at import time) the "Data Source" button is grayed out and indicates "n/a".
Automated process to change incorrectly spelled street names.
CA CHP introduced a new structure for SWITRS data beginning with data send after June 2002 (although most of this new format didn't ship until 2003) Pd' Programming made available a new configuration to read this data free-of-charge to all current subscribers to our Intersection Magic software. On February 13, 2003 we identified a minor problem with the new configuration. The caseID format in this new CHP data structure is variable - it is different after 1/1/2000. This article describes how to correct your configuration and database if you downloaded the new configuration prior to 2/18/2003 and imported 2002 data using it.
Intersection Magic is 'configured' for a particular format of ASCII data. When you first purchased IMW, we probably prepared a custom configuration. This custom configuration defines, among other things, the order of the fields in the ASCII import file; the meanings of any coded fields; the method of parsing, or extracting the data from any given field. Periodically, states re-evaluate the crash report form that they are using. When this is done, they frequently add or remove fields. Occasionally, they add or remove codes for a particular fields. Rarely, and unfortunately, they change the value that a code represents in a particular field. This article describes some things to think about if you find that your data source is different than it was when we prepared your configuration.
Intersection Magic supports several ways of adding data to its database. This article describes the difference between updating data with regular importing, partial record importing and merging using imwedit.
On occasion, users have the need to supplement records in their database without removing data already stored for those records. An example would be if you have a data source that provides you all the crash data you need except for direction from intersection. You have another source that can provide direction from intersection and uses the same caseid number that the first data source uses. This is a use for Supplemental importing.
Dates may be represented may ways. Intersection Magic can handle most of them. This article describes which formats are supported and will be properly converted by the program.
The data in Intersection Magic is usually obtained from local city, county or state sources. In most cases, it is possible to query these sources to list the same data being reported by Intersection Magic. WeÕve found that when this is done, there may be discrepancies between the two systems. There can be several causes for these discrepancies. This document describes how we attempt to identify and resolve these differences when contacted by a concerned user of our software. While we welcome you to contact us, it is our hope that you can take the first steps yourself using the information provided here.
The California Highway Patrol (CHP) maintains the crash records that you use as SWITRS data. In January of 1998 they modified the format which had been used for many years. The format was changed to add the century to any dates in the data file. This makes the data y2k compatible. This requires special treatment of SWITRS data by Intersection Magic.
A very long street name exists in the database, but diagrams for locations on that street can not be generated, and sometimes the street itself is missing from high accident location lists.
The error "Number too great" is logged when a value being imported into a user-field is greater than the max allowed value of 254.