error

  • KB
  • error

Map Magic not installed properly

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)
Read More

A(n) Theme object does not recognize request IsMatchable

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
Read More

Differences between in-house and Intersection Magic data

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.
Read More

SWITRS crash data is imported incorrectly

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.
Read More