Y2K compatibility information

adminIntersection Magic Windows > Data

Every version of Intersection Magic ever shipped stores all of its dates as julian numbers. This means that we shouldn't have any date problems for as long as cars skid on pavement. However, your source data may not be year 2000 compatible.


 Copying an Intersection Magic database

adminIntersection Magic Windows > Data

The Intersection Magic database is contained in a number of files. This article describes which of these files should be copied when moving or copying the database to a new location.
NOTE: Beginning with version 6.x of the program, there is an option called "copy" under the Utilities / Database menu. This is the preferred method of copying databases in Intersection Magic.










 How to prepare data for use in Intersection Magic

adminIntersection Magic Windows > Data

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.






















 Manual update / verification required after upgrading from v6.5x to a newer version.

adminIntersection Magic Windows > Data

Changes made in version 6.615 require user verification of cross-street data. Note that because the changes only affect cross street ordering associated with the use of aliases, this information only applies to users who have prepared cross street listings using the streets manager. Also, if aliases have never been used, this information does not apply.





 Performing supplemental data imports

adminIntersection Magic Windows > Configuration

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.





 Differences between in-house and Intersection Magic data

adminIntersection Magic Windows > Configuration

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.


 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.