Normalizer - Streets (normalize-streets)
|Top Previous Next|
The streets normalizer in Crash Magic is used by the program to provide a list of standard street names. Any time a street is selected in a study the streets normalizer has provided the list of streets for the user to select. The streets normalizer defines which fields should be used from the Streets query to define a standard list of streets.
Name: This is the name of the streets normalizer.
Description: This field contains a description of the streets normalizer.
Unique Delimiter: This value is used to separate the Street names from the unique 1 and 2 values when displayed to the user.
Unique Starters: This value is used to enclose the unique 1 and 2 values when displayed to the user.
Distinct Query: Query that will return an entire list of streets
Case Sensitive: Indicates that this normalizer should respect the case of street names
Street: Field from the Distinct query that returns the name of the street
Unique1: Field from the streets query that indicates the street is unique to an area. For example a street may cross several counties. This field could be used to specify the county. This field should be left blank if this information does not exist in the collision data. Along with specify the field from the distinct query the type of field needs to be selected. A drop down menu of lookup queries is also provided. The drop down menu on the far left allows the user to select a lookup for this field. This means that if the field from the streets query contains a number that represents the location. The lookup query selected in this drop down menu will be used to display the readable value to the user. Study queries that use Unique1 must have PrimaryStreetUnique1, CrossStreetUnique1 and/or RouteUnique1 fields flagged in the study query.
Unique2: Field from the Distinct query that indicates the street is unique to an area within the Unique 1 area. For example a street may cross cities within a county. This field could be used to specify the city where the street is located. This field should be left blank Unique 1 is not in use. The middle drop down box on this page also allows the data type for the field to be specified. The drop down menu on the left allows a dependent query to be specified. The dependent lookup query allows Crash Magic to retrieve a street using the street name and the value in Unique1. Study queries that use Unique1 must have PrimaryStreetUnique2 , CrossStreetUnique2 and/or RouteUnique2 fields flagged in the study query.
Note: Unique 1 and Unique 2 are not required fields but are often needed if the database contains more than one municipality. The Unique 2 field relies on the Unique 1 field, and is always a subset of the Unique 1 field. The most common use for these fields would be Unique 1 as "county" and Unique 2 as "city".
StreetID: ID for the street selected. This field should be left blank if street names do not have a corresponding value to identify the street.
Alias Groups: Allows clients to define street alias names for a location. As an example HWY 93 could cross a town where it is call Main St. Alias groups enable the ability to define a street using a single street name. An Alias Group must be created to store the alias information before this feature can be used.
Enable: This enables the Alias Group selected to be used by the normalizer.
Visible: This makes the Alias Group streets visible to users in the street selection boxes.