Choosing a schematic
|Top Previous Next|
The default schematic that will be used every time a diagram is generated is a four-leg intersection that is capable of representing crashes at varying distances and directions from the intersection. This default can be changed at any time by choosing Utilities / Configuration Defaults / File names and clicking the ‘schematic’ button.
A different schematic may be selected for a diagram by choosing it from the diagram panel settings tab.
The 100 or so available pre-defined schematics are arranged by type of location. A number of different sub categories provide representation of different directions, as well as lanes.
The basic pre-defined categories are:
•Address – These schematics are dynamically generated based on the address range of the study. Each section of the schematic represents a hundred block range. Collisions are then placed based on the value from the _BlockAddress field in the P_Default calculated fields. The _BlockAddress field will be set to 0 for collision data that does not contain address information. The two characters at the end of Address indicate the direction of the block range.
•Approach – These schematics represent just one leg of an intersection. (i.e. the north approach) These schematics provide a high degree of detail related to the distance from the intersection. Since more room is available for crash graphics in the approach leg than in a 4 leg diagram, more areas are defined. Collision data must have distance from intersection and direction from intersection defined in the _DistFromInt and _DirFromInt of the P_Default calculated field. Collision data that lacks this information will default to 0 distance from intersection and a null direction from intersection.
•Corridor – These schematics are designed to represent crashes that contain address, hundred block data or other reference location information. They can depict the relative position of each crash along the given corridor. A number of different corridor options provide greater resolution / spacing between the end points.
•Corridor/Part/ – These are various sections of the Address, Corridor and Milepost schematics. Dynamic schematics are built from these parts. Users should avoid selecting these schematics.
•Int_4 – These are the most commonly used schematics. They depict 4 leg intersections of many types. Intersections with 1, 2, 3 and 4 turn bays. There are also boulevard schematics and schematics which provide special support for distance and direction from the intersection.
•Int_T – These are ‘T’ intersections. They are available in most of the same varieties as the Int_4 category. As would be expected, they are available for each approach direction.
•Int_Y – These are ‘Y’ intersection templates. In order for them to be used, they must first be customized to reflect the data available that indicates which street(s) the crash occurred on.
•Mid_blck – These schematics depict locations which include crashes which occurred between intersections. There are a variety of these which can also include lanes when such data is available.
•Milepost These schematics are dynamically generated based on the milepost range of the study. Each section of the schematic represents a tenth of a mile section. Collisions are then placed based on the value from the _Milepost field in the P_Default calculated field. The _Milepost field will be set to 0 for collision data that does not contain milepost information. The two characters at the end of Milepost indicate the direction of the range.
•Mult_int – These are diagram template(s) that depict more than one intersection in the same diagram. These will need to be modified to support data.
•old – This category contains all of the pre-version 6.0 schematics. Since the schematics changed fairly substantially in version 6, and some users may be attached to the original ones, we’ve provided updated versions of the original schematics.
•RoundAbout – These schematics are designed to display roundabout intersections.