Internet Services - Plotting Collision Diagrams And Crash Locations (Item# E-01)  

Features
Screen Shots
Pricing
How It Works
How To Set Up Web Hosting
Risk-Free Offer
Sample Outputs
How To Download And Run Sample Outputs
Instructions On How To Display Collision Diagrams And Crash Locations
Mailing List Sign-Up
(Back to Internet Services or What's New)

Features:  (Note the new features in red, effective 7/7/08.)
1. We plot collision diagrams in Google Earth®. (Plot up to 100,000 records. New)
2. We also plot crash locations with our patented* 3 dimensional stacked symbols in Google Earth®. (Plot up to 100,000 records. New)
3. These plots are based on your data. You rarely need to change your data structure and coding definitions.
4. You may upload the plots to our web site or your web site for the public to access them.
5. The collision diagrams have these characteristics:
- It uses a yellow pin to denote injury collision and a red pin to denote fatal collision.
More... (New)
- It labels each collision with date, time, weather, lighting, road condition, etc. (up to eight fields from your data). More... (New)
- You can use different arrowhead colors to denote bicycles, buses, pedestrians, trucks and all other vehicles. More... (New)
-  It plots each collision with 1 or 2 arrows, representing vehicles' travel directions. 
-  It arranges the arrows into different collision types, including angle, fixed object, head on, left turn, rear end, right turn, sideswipe and other.
-  When you click a plotted arrow (or a pin), it displays the field names and field contents of a record on the screen. You can specify which fields to be displayed. 
-  If the fields you specified for displaying include collision type, travel directions and turning movements, you can easily verify if a collision is plotted correctly. Since you can add scanned accident report image, you can easily check the plotted collision against the original data.  
6. The crash locations have these characteristics:
-  Each location is plotted with a stack of symbols. The number of symbols in a stack corresponds to the number of crashes at that location. This provides a three dimensional view, such that the height of the symbols is proportional to the number of crashes. 
-  The  symbols within a stack have different letters and colors, representing different collision types. For example, a yellow "R" symbol represents rear end collision; a green "S" symbol represents sideswipe collision; and so on. 
-  By looking at the heights and colors of the symbols, you have an overview of the magnitudes and patterns of the crash locations. 
-  When you click a plotted symbol, it displays the field names and field contents of a record on the screen. You can specify which fields to be displayed.

-  As a result, it provides an overview of all the crashes as well the details of individual crash.
7. It plots up to one hundred thousand (100,000) records, up to ten thousand (10,000) locations, and up to one thousand (1,000) crashes per location. Hence you can plot your crashes once and use them again and again. (New) 
8. It has the built-in capability of displaying crash report image. This allows you to refer to the original data easily. It also allows you to check if our plotted symbols are correct. More... (New) 
9. It has the built-in capability of attaching a memo to a plotted symbol. Since each plotted symbol (or pin) relates to a crash record in the data, it allows you to add related information to a crash record. More...(New) 
10. It has the built-in capability of attaching an image to a plotted symbol. Since each plotted symbol (or pin) relates to a crash record in the data, it allows you to add a picture of the crash scene, or a scanned citation report, etc. to a crash record. More...(New) 
11. It has the ability to add HTML tags, using Google Earth's built-in functions. The reason is that when the contents of a record is displayed in Google Earth, it is displayed in a browser. A browser has many capabilities, including the capability of using HTML tags. You can use HTML tags, such as <a>, <a href>, <img src>, etc. to add additional links and files to associate with a plotted symbol. Since each plotted symbol (or pin) is associated with a crash record, hence you can add additional links and files to each crash record. These links and files include web pages, executable programs, images, sounds, videos, etc. These links and files may be in the internet or in your local computer. For example, you may add a link to a weather report in the Internet, a link to the driver's previous drunk-driving record in your intranet, a link to a temporally street closing file, etc.
     The built-in capabilities of displaying crash report image, attaching a memo, and attaching an image, as mentioned in items 8, 9 and 10, are just special applications of adding HTML tags. You can add almost an unlimited number of  tags to link to almost an unlimited number of resources. (New) 

*US Patent 6104410 

back to top

Screen Shots:
Figure 1: Internet Collision Diagram 
     This figure shows how a typical collision diagram looks like in Google Earth®.

Fatal crash has a red pin. Injury crash has a yellow pin.

How to get this view:
In Google Earth®, in the left side bar, under Places, double click Location 1.
     If left side bar is not shown, click View, then click Full Screen or Sidebar.

Figure 1A: Collision Diagram - Record Content Display 
     When you click a plotted symbol (or a yellow or red pin, it is present), it displays the field names and field contents of a record, as shown in this figure. You may choose which fields to be displayed.
     This enables you to access detail record of each plotted collision.
      If the fields you specified for displaying includes collision type, travel direction and turning movement, you can easily verify if the collision diagram is plotted according to the input data.
Figure 1B: Collision Diagram - Report Image Display 
      When you click a plotted symbol (or a pin), it displays a hyperlink called "Report Image ...". If you click this hyperlink, it displays the scanned crash report image, as shown here.
     As a result, you can easily access the original data. You can also verify the collision diagram with the original data.
Figure 2: Internet Crash Locations With Stacked Symbols
     This shows how a typical top 10 crash locations looks like on Google Earth®, at eye altitude of about 12 kilometers. 
     Each location is plotted with a stack of symbols. The number of symbols within a stack corresponds to the number of crashes at that location. Hence a higher stack of symbols means a higher number of crashes at that location.
     The  symbols within a stack have different letters and colors, representing different collision types. For example, a yellow "R" symbol represents rear end collision; a green "S" symbol represents sideswipe collision; and so on.
     By looking at the heights and colors of the symbols, you have an overview of the magnitudes and patterns of the crash locations.
Figure 2A: Crash Locations - Record Content Display 
     This figure is the same as Figure 2, except that it is at an eye altitude of about 600 meters.
   When you click a plotted symbol, it displays the field names and field contents of a record, as shown in this figure. You may choose which fields to be displayed.
     This enables you to examine detail individual records while having an overview of all crash locations at the same time.
Figure 2B: Crash Locations - Report Image Display 
      When you click a plotted symbol, it displays a hyperlink called "Report Image ...". If you click this hyperlink, it displays the scanned crash report image, as shown here.
     This enables you to examine the original data of an individual crash while having an overview of all crash locations at the same time.
Figure 3: Collision Diagrams and Crash Locations At Eye Altitude 600 Meters
    This figure displays the collision diagrams (from Figure 1) and the crash locations ( from Figure 2) together on the same Google Earth®. 
     If you put both Figures 1 and 2 on the same Google Earth, it will look like Figure 2 at eye altitude of 12 kilometer. It will look like Figure 3 at eye altitude of 600 meters. It will look like Figure 4 at eye altitude of 90 meters.
     You may check/uncheck in Google Earth®'s Place panel to display collision diagrams only, crash locations only, or both at any time.
Figure 4: Collision Diagrams and Crash Locations At Eye Altitude 90 Kilometers
    This figure displays the collision diagrams (from Figure 1) and the crash locations ( from Figure 2) together on the same Google Earth®. 
     If you put both Figures 1 and 2 on the same Google Earth, it will look like Figure 2 at eye altitude of 12 kilometer. It will look like Figure 3 at eye altitude of 600 meters. It will look like Figure 4 at eye altitude of 90 meters.
     You may check/uncheck in Google Earth®'s Place panel to display collision diagrams only, crash locations only, or both at any time.

back to top

Pricing: (New, Effective 7/7/08)

Number of Records

Price

Number of Records

Price
1 - 1,000 $598 10,001 - 12,000 $1,598
1,001 -2,000 $698 12,001 -14,000 $1,698
2,001 - 3,000 $798 14,001 - 16,000 $1,798
3,001 - 4,000 $898 16,001 - 18,000 $1,898
4,001 - 5,000 $998 18,001 - 20,000 $1,998
5,001 - 6,000 $1,098 20,001 - 40,000 $2,998
6,001 - 7,000 $1,198 40,001 - 60,000 $3,998
7,001 - 8,000 $1,298 60,001 - 80,000 $4,998
8,001 - 9,000 $1,398 80,001 - 100,000 $5,998
9,001 - 10,000 $1,498 Over 100,000 Call

- Second set of plots* = 30% of the price of the first set.
- Re-Plotting the same data due to error or modification = $99. If we plot your data incorrectly, we will re-plot them free.

- Using different symbols to denote bicycles, buses, pedestrians, trucks and all other vehicles: add $699

(Note: Google Earth® license is required and is not included. The license is free for personal use. For commercial use, the license of Google Earth® Pro is $400 per year (as of June1, 2008). Refer to http://earth.google.com/intl/en/

Credit card payment is welcome. Please call.

*The second set of plots is the same as the first set except that it displays limited contents from the data. For example, you may use the first set for internal use and the second set for public use. In the first set, you may specify all fields from data to be displayed when user clicks a plotted symbol (or a pin). In the second set, you may specify only limited fields, such as date, time, collision type, weather, etc. to be displayed when a user clicks a plotted symbol (or a pin). You may upload the second set to your web site or our web site for public access. 

back to top

How It Works
1. In order to plot collision diagrams and crash locations in Google Earth®, your data must contain location information. Location information may be latitudes and longitudes; addresses; main street names and cross street names; distances and directions from nearest intersections; mile points; etc. If the location information are not in latitudes and longitudes, we will geocode them. That is, we will convert the location information into latitudes and longitudes. We will use either your latitudes and longitudes, or the converted latitudes and longitudes (based on your other location information) to identify the locations in Google Earth®. 
2. To start working for you, we will ask you to email some or all your data to us. This is to make sure that your data have the proper location information. (We accept data with almost any data structure and coding definitions.) Save you data in one of the following file formats:
   - Access (MDB)
   - ASCII or Text (TXT), with tab or comma as delimiter
   - Comma Separated Values (CSV)
   - dBASE (DBF)
   - Excel (XLS)
   - XML
3. If you are not sure what data, or your data cannot be saved in one of the formats listed in 2, please send some existing data, in whatever format. We will be happy to look at them to determine if they have the proper location information and or format.    
4. If your data do not have the proper location information, we will discuss with you to see if there is alternative. If there is no alternative, we will not be able to take your order.
5. If your data have the proper location information, we will ask you to send us all your data, coding definitions for the fields related to plotting collision diagram (such as collision type, vehicle travel direction, turning movement, injury, fatality, etc.), and payment/purchase order.
6. We will create the collision diagrams and crash locations plots for you. The plots will include both intersection and mid-block collisions. We will save the plots in KMZ files and will send them to you.
7. Upon receiving the KMZ files, you can save them anywhere in your computer. When you double click a KMZ file, you will see the displays as shown in the Screen Shots above, if you have installed Google Earth® on your computer. You may use the KMZ files for any purpose, including emailing to others, uploading and posting in your web site, etc. If you post the KMZ files in your web site, when a visitor clicks a KMZ file link in your web site, the visitor will see the same displays as shown in Screen Shots above, if the visitor has installed Google Earth® in his/her computer (see How To Set Up Web Hosting below).
8. You may consider ordering two sets of KMZ files. The first set is for internal use. The second set is for public use and/ or for posting in your web site. Both sets are plotted from the same data and displaying the same symbols at the same locations. The differences are as follows:
a) The internal-use set:  
- When you click a plotted symbol (or a pin), it displays everything from your data.
- When you click a plotted symbol (or a pin), it displays a link to a scanned image of the crash report. When you click this link, you can see the original report form. More...
- When you click a plotted symbol (or a pin), it displays a link to a memo file. When you click this link, you can see the attached memo. More...
- When you click a plotted symbol (or a pin), it displays a link to an image file. When you click this link, you can see the attached image file. More...
- As a result, you can use this set for safety analysis and data management.
b) The public-use set:  
- When one clicks a plotted symbol (or a pin), it displays only limited information from your data. (You can specify which information to display.)
- When one clicks a plotted symbol (or a pin), it displays a link to a scanned image of the crash report. When one clicks this link, it will say unavailable.
- When one clicks a plotted symbol (or a pin), it displays a link to a memo file. When one clicks this link, it will say unavailable.
- When one clicks a plotted symbol (or a pin), it displays a link to an image file. When one clicks this link, it will say unavailable.
- As a result, you can use this set for public awareness.
The price for the second set is 30% of the first set.
8. Delivery of product will be about one week, after we have received your data and payment/purchase order.  2-day delivery and next-day delivery are available with additional cost.

back to top

How To Set Up Web Hosting
1. Using your data, we create the collision diagrams and save them in a KMZ file (see How It Works). 
2. Using your data, we create the crash location plots and save them in a KMZ file (see How It Works).
3. To host these plots, upload the KMZ files from 1 and 2 to the sever in your web site, then create a link in a web page to link to each KMZ file.
4. Ask the webmaster to set the web site's MIME type for KMZ file, such as setting the httpd.conf file to:
          application/vnd.google-earth.kmz .kmz
   For Apache, add this line to the httpd.conf file:
          AddType application/vnd.google-earth.kmz .kmz
   For more information, see http://code.google.com/apis/kml/documentation/kml_tut.html 
   or http://earth.google.com/support/bin/answer.py?answer=25094&topic=13334
5. That is it! When a person in the Internet goes to the web page and clicks the link, it will display the collision diagrams and/or  the crash location plots, as shown in figures 1 to 4 under "Screen Shots." 

back to top

Risk-Free Offer:
If you are not satisfied during the first 60 days (starting from the date you have received the plots), you will received full refund (less $100 handling fee). This offer applies to the first 10 public agencies in the United States and Canada only.

back to top

Sample Outputs:
(Starting July 7, 2008, we have added sample outputs with up to 33,000 records and up to 5,000 locations. To run these outputs smoothly, please refer to computer requirements in "How To Run And Download Sample Outputs"  below.)     

1. Washington, DC:
   - Top 10 collision diagrams, public use ----- Top 10 collision diagrams, internal use
   - Top 10 crash locations, public use ----- Top 10 crash locations, internal use
2. Houston, TX:
   - Collision diagrams from 3,100 records at 100 locations (0.4MB)
   - Collision diagrams from 7,600 records at 500 locations (0.9MB)
   - Collision diagrams from 10,700 records at 1,000 locations (1.3MB)
   - Collision diagrams from 17,000 records at 5,000 locations (2.2MB)
   - Crash locations from 3,100 records at 100 locations (0.2MB)
   - Crash locations from 7,600 records at 500 locations (0.4MB)
   - Crash locations from 10,700 records at 1,000 locations (0.6MB)
   - Crash locations from 17,000 records at 5,000 locations (1.1MB)
   - Top 10 collision diagrams, public use ----- Top 10 collision diagrams, internal use
   - Top 10 crash locations, public use ----- Top 10 crash locations, internal use
3. Florida State Department of Transportation, Districts 5 and 7:
   - Collision diagrams from 12,000 records at 2,100 locations (2.1MB)
   - Crash locations from 12,000 records at 2,100 locations (1.3MB)
   - Top 10 collision diagrams, public use ----- Top 10 collision diagrams, internal use
   - Top 10 crash locations, public use ----- Top 10 crash locations, internal use
4. New York, NY:
   - Collision diagrams from 33,000 records at 2,900 locations (3.8MB)
   - Crash locations from 33,000 records at 2,900 locations (1.5MB)
   - Top 10 collision diagrams, public use ----- Top 10 collision diagrams, internal use
   - Top 10 crash locations, public use ----- Top 10 crash locations, internal use
5. San Francisco, CA:
   - Top 10 collision diagrams, public use ----- Top 10 collision diagrams, internal use
   - Top 10 crash locations, public use ----- Top 10 crash locations, internal use
6. California State Department of Transportation:
   - Top 10 collision diagrams, public use ----- Top 10 collision diagrams, internal use
   - Top 10 crash locations, public use ----- Top 10 crash locations, internal use
7. Columbus, OH:
   - Top 10 collision diagrams, public use ----- Top 10 collision diagrams, internal use
   - Top 10 crash locations, public use ----- Top 10 crash locations, internal use
8. Tulsa, OK:
   - Top 10 collision diagrams, public use ----- Top 10 collision diagrams, internal use
   - Top 10 crash locations, public use ----- Top 10 crash locations, internal use
Notes:
- All sample outputs are for illustration only. They are not from real data.          
- For public use, it displays selected field names and field contents from a record in the data, when clicking a symbol (or a pin).
- For internal use, it displays all field names and field contents from a record in the data plus scanned crash report image, when clicking a symbol (or a pin).

back to top

How To Run Or Download Sample Outputs:
A. Run sample outputs:
1. Install Google Earth® in your computer first. (Install it from http://earth.google.com/intl/en/)
2. Click a sample under Sample Outputs, then click "Open".
3. Follow Instructions On How To Display Collision Diagrams And Crash Locations

B. Download sample outputs:
1. Click a sample under Sample Outputs, then click "Save As".
2. To run your downloaded file, refer to Instructions On How To Display Collision Diagrams And Crash Locations.

C. Computer Requirements:
To run all sample outputs smoothly, your computer should be equivalent to or better than the following:
  - Intel® Core Duo or Dual Core AMD® Opteron processor.
  - 2 GB of RAM for Windows® XP  (or 4GB of RAM for Windows® Vista)
  - 8 GB of free hard disk space.
(If your computer is less than the above, it still works, but may be slow.)

     
back to top

Instructions On How To Display Collision Diagrams And Crash Locations:
Refer to Instructions On How To Display Collision Diagrams And Crash Locations

back to top


Mailing List Sign-Up
Please enter your email below. We will keep you updated.
back to top

_________________________________________________________________
     Home     AIMS     Crime Mapping     About Us     Contact     Internet Services     What's New
Copyright © 2008, JMW Engineering, Inc. All rights reserved. Protected by U.S. Patent 6104410