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

Table of Contents

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.


A problem in Intersection Magic detailed in knowledgebase article number 55 can cause erroneous output when querying a corridor type diagram that includes streets with multiple aliased names.

When upgrading an installation containing cross street lists, the program converts the cross street database by adding “root” street references to the cross street data. From that point forward, all cross streets functionality in the program accesses the root street values rather than the alias names. The alias names are preserved and used for display purposes.

In situations where a street has a list of cross streets, and an alias of that street also has a list of cross streets, those lists are merged during the conversion process. This is unlikely if the two names are simply aliases, but more likely when the two names reflect different parts of the same street. (i.e. “N. Broadway; Broadway; S.Broadway)

When this merging occurs, the cross streets from the aliased street names are “interleaved” and displayed together. They must be re-ordered for proper operation of the program.

New to this version of the program: When viewing or modifying the cross streets of a given primary street, the list will be the same for all aliases of that primary street. Also, while any cross street names may be selected, and will be preserved, the program will internally store the root names for consistent use during analysis.


Please examine all of these steps prior to proceeding with your upgrade.

  1. Before upgrading: Make a database backup.
  2. Before upgrading: If possible, prepare an export of your existing cross streets data. (Streets Manager / Export Ascii) Save this file for possible future use.
  3. Before upgrading: Go to the streets manager and select a street with no cross streets. The reason for this is to ensure that after upgrading, the “current” street will not be one that contains cross streets. This is helpful, but not critical.
  4. Download and unpack the upgrade. By default, it will unpack into c:magic. If you have installed the program elsewhere, or have a network installation, change this to the network drive and directory (i.e. e:magic)
  5. After upgrading: Run Intersection Magic. You will be prompted for a new key. Be sure that no one else is using the database, and that you are logged in as a user with rights to make changes to the database
  6. After upgrading: Proceed to the streets manager. You will be prompted to “update” the database. This process is fairly short. A reindex is not required or recommended. When complete, the streets manager will be presented.
  7. After upgrading: From within the streets manager, select Export Ascii. Save the file to a filename and location that you will remember. Close the streets manager
  8. After upgrading: In Intersection Magic, select Edit / Open edit window. Choose the file that you exported from the streets manager in the last step. When this file is displayed, select File / Launch as CSV. Excel will be launched.
  9. From Excel: Select Data / Sort. Choose column G for the first sort item, column A for the second, and column B for the last sort item.
    This file is now a tool that you can use to identify streets that had multiple cross street lists merged together. The columns have the following meanings:

    • A: On Street
    • B: Order of cross street
    • C: Cross street
    • D: Distance to next cross street
    • E: Distance units
    • F: Primary street orientation
    • G: On Street – ROOT name
    • H: Cross street – ROOT name
  10. From Excel: The resulting sort will group any aliased street orderings together. Look for situations where column B repeats the same number within the same ROOT street (column G). This indicates that two aliased streets have been merged.
  11. In Intersection Magic: Go to the streets manager. Using the information from the last step, re-order any streets that have had multiple aliases merged. Usually, this will mean taking every other, or every three streets and moving them up or down the list to their appropriate locations. To verify that the job is complete, repeat the steps of exporting the list and sorting it in Excel.
Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?