Read More
When a cross street order is defined in the streets manager, Intersection Magic assumes this is the entire list. As a result, it only shows the streets you've created in the order list.
Intersection Magic can maintain a list of intersections and volume studies. This article describes how to create the required volume data file, and how to let the program know to use it.
Read More
The volume data is handled in a new way starting with version 6.500. It is important to understand the new methodology.
Read More
To be able to draw a corridor diagram for the length of a ramp.
Read More
Intersection Magic has a margin of error when calculating sliding spot sections.
Read More
Intersection Magic's symbols to represent vehicles, fixed objects, dui, etc. reside in a symbol library that can be modified. Therefore, new symbols can be created and then introduced into the object table (.tbs) file and displayed in collision diagrams.
Read More
This problem occurs when your printer is set to a resolution higher than 300dpi. Intersection Magic is still printing to some internal coordinates that reflect 300dpi.
Read More
Changes made in v6.607 resulted in incorrect print when using Windows '95 or Windows '98.
Read More
When a corridor diagram is created for a street which is an alias to another street, not all the crashes will be shown. The crashes included may also not include those that occured on end-point cross streets if they are aliases as well.
Read More
Each diagram contains a number at the top that indicates how many crashes took place at that location. The number of graphics may not always match that number. However, the number of graphics plus the number of "records with insufficient data for display" listed at the bottom of the diagram should match.
Read More