Map Magic 2 for ArcMap is an add-in for ESRI ArcMap software (versions 10.3 and later). It allows you to create Crash Magic studies and reports from within ArcMap via Crash Magic's REST interface. This article includes information on the initial setup of Map Magic 2 for ArcMap, including how to configure the user login and advanced settings options.
Map Magic 2 for ArcMap is an Add-In for ESRI ArcMap software (versions 10.3 and later). It allows you to create Crash Magic studies and reports from within ArcMap via Crash Magic's REST interface. This article includes information on the process of installing Map Magic 2 for ArcMap.
Clients installing the Map Magic plugin may experince and error
New clients to the Map Magic rectangle selection tool will sometimes get results of no data or an incorrect number of collisions. However, this problem will not occur with the send selected collisions tool.
This article is to show how to create a pin map with Map Magic and Arc View version 3.x.
Clients with Map Magic CMO version 188.8.131.5238 or earlier may receive the error "Object reference not set to an instance of an object" when clicking send selection tool or Exception "GetFieldNames" when opening the settings window
A new version of Map Magic has been released to work with Arc Map 10
Map Magic makes it easy to copy a configuration for others to use.
This shows how to install Map Magic into ArcMap Version 9
Each time a diagram is created by Map Magic a new browser tab is created.
The Map Magic dll can be installed anywhere in a client directory. This article is intended to give users guidelines on the installation.
When Map Magic CMO is used from within ArcView, the user must be logged in to Crash Magic in order for a diagram to be created.
Sometimes Map Magic and ArcView do not communicate properly due to some automatic features not functioning.
For different tech support reasons, we periodically will need to recreate your maps here at Pd' Programming.
ArcView displays error "MSW call DeleteObject failed" when selecting an item from a map. This issue also opens an MS Dos window stating "invalid parameter".
In many cases, your GIS map street names will not match the names in your crash record database. If the difference is significant, (i.e. ArcView can't see them as being similar names) then that location will not be geocodable. This is common when a state highway runs through a city. The city may use a local street name when entering crash data, and the map may use the highway name.
When geocoding, if a location is not found, it can sometimes be challenging to select the blue dot created by clicking on a new intersection on the map.
Map Magic is an add on to ArcView GIS 3.x and Intersection Magic 6.x. All Arcview GIS 3.x versions have a problem with Windows XP that affects operation with Map Magic. We've experienced "Segment Violation" messages; we've heard of "Can not convert string to number" error messages.
ESRI has overhauled the ArcView and ArcInfo product lines. The new ArcView is v8.x. Intersection Magic is designed to work with v3.1 or v3.2, the most recent versions before 8 was released.
In order for Map Magic to work properly, certain requirements must be met in ArcView GIS first.
This article helps describe the steps necessary to verify your map works in ArcView GIS.
To illustrate the steps necessary to allow Map Magic to communicate with ArcView GIS
Location coordinates are not being stored in *.geo files after the size of the file has reached 64KB.
When calling ArcView / Map Magic from Intersection Magic, a dialog box reports that this is the incorrect version of Map Magic.
“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 […]
While waiting for Intersection Magic to launch ArcView, Intersection Magic stops responding. Usually this occurs in the final seconds (as indicated in the status bar) of loading.
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