Map Magic not installed properly

adminMap Magic > Errors / crashes

Intersection Magic communicates with ArcView using Map Magic. If Map Magic is not properly installed, ArcView will complain that it can't find the required scripts (im_a_displaycrashes, im_a_displayints, im_a_displayspots, im_a_geocode)


 Individual Crashes Error

adminMap Magic > Mapping

“Error in reading shape record length for record 1” When trying to get Individual Crashes shown on a map, and you get the message “Error in reading shape record length for record 1” after selecting the Go button. This is because the accident list text file that was created in Intersection Magic wasn’t a comma […]


 A(n) Theme object does not recognize request IsMatchable

adminMap Magic > Mapping

When geocoding individual or aggregate crashes using Map Magic, a call is made to each theme checking for "IsMatchable" to see if that layer is geocoded. Unfortunately, some themes don't know if they are matchable and the program will stop with an error message. This article describes why and how to get around this problem


 SWITRS crash data is imported incorrectly

adminStandard configurations > California (SWITRS)

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.