Query parameters

Top  Previous  Next

Each study definition must specify a study type and a query that it will use to gather data from the database.  Each study type has parameters it requires. These parameters are obtained from the study query's normalized fields. The study types and required parameters are shown here.


Study type:


Required parameters:

All Data


The all data study gathers collisions by date range. It is not specific to a location.

Date (DateTime)




The Address study gathers collisions by date range, route and address range.

Date (DateTime)

PrimaryStreet (String)

Address1 (Integer)

Address2 (Integer) (optional)

Case Id


The CID study provides the ability to query the database for case id's that have been populated in the crash magic system tables. This query  uses the user group id, user id, project id and the study id of the user that is logged in.

CaseId (String)




The Intersection study provides the ability to query the database by date range plus primary and cross streets.  This is the standard study for urban areas and rural areas where mileposts don't exist.

tDate (DateTime)

PrimaryStreet (String)

CrossStreet (String)


Intersection corridor

The intersection corridor study provides the ability to query a sequence of intersections on a single street.


This study type also provides the ability to specify parameters to include/exclude crashes occurring at intersections, off the corridor, and beyond the ends of the corridor.

tDate (DateTime)

PrimaryStreet (String)

CrossStreet (String)

_DistFromInt calculated field

_DirFromInt calculated field



X,Y Coordinate




The xyrect study gathers crashes by prompting for a date range plus a rectangular area (X min/max and Y min/max values) that indicates a coordinate range from a GIS system.

Date (DateTime)

XCoordinate (Float) (e.g. longitude)

YCoordinate (Float) (e.g. latitude)





The Node study uses a date range,  and optionally a node identifier, up to two additional unique identifiers.  These unique identifiers might specify a county, city, zip code, etc.  The unique identifiers are only needed if multiple, non-unique instances of the node number occur in the database.

Date (DateTime)

Node queries currently utilize the node field specified in the node normalizer.  Node is expected to become a normalized field in the future.


Route + Milepost




The milepost study uses a date range plus a route name/id and milepost range.  

Date (DateTime)

Route (String)

Milepost (Float)