Introduction
This page covers the general details used for all highways rules. Depending on the rule type, certain settings may not be available. Be aware that the rule editor is very flexible and allows you to configure many different rules. You should give thought to how these rules are reported to external systems. The primary mechanism for categorising rules is by using the Rule Sub-Type setting. This ensures external systems will always understand what type of alarm is being raised regardless of how many different rule configurations are used.
...
Severity: Defines how a target should be marked when it breaks a rule. Such markings allow targets which present a warning or threat to be easily differentiated from friendly and unclassified targets.
Unknown
Friend
Warning
Threat
Action: Defines the action that should be taken when a rule is broken.
...
Full Resolution
Half Resolution
Quarter Resolution
Eighth Resolution
...
The following grid shows the space required for each image for the Image Capture:
Resolution | Width | Height | Size (Kb) |
Full | 1920 | 1080 | 541 |
Half | 960 | 540 | 197 |
Quarter | 480 | 270 | 51 |
Eighth | 240 | 135 | 13 |
Alarm Description: Determines the text that will be presented to the operator (and entered in the activity log) when the rule is broken and an alarm is raised. Note that you can use the follow place holders which will automatically be populated with the relevant data when the alarm is raised. The place holders are as follows:
...
Severity: Defines how a target should be marked when it breaks a rule. Such markings allow targets which present a warning or threat to be easily differentiated from friendly and unclassified targets.
Unknown
Friend
Warning
Threat
Action: Defines the action that should be taken when a rule is broken.
...
| Info |
|---|
For an image captured at full resolution for a full 1080P HD camera will use about 135KB of storage in the database. The images are compressed using the JPEG standard to save space. |
Alarm Description: Determines the text that will be presented to the operator (and entered in the activity log) when the rule is broken and an alarm is raised. Note that you can use the follow place holders which will automatically be populated with the relevant data when the alarm is raised. The place holders are as follows:
{CARRIAGEWAY} : Will be replaced with the carriageway name where the incident has occurred.
{CARRIAGEWAYID} : Will be replaced with the carriageway user Id where the incident has occurred.
{SECTION} : Will be replaced with the section name where the incident has occurred.
{SECTIONID} : Will be replaced with the section user Id where the incident has occurred.
{LANE} : Will be replaced with the lane name where the incident has occurred.
{LANEID} : Will be replaced with the lane user Id where the incident has occurred.
{RULEID} : Will be replaced with the user Id of the rule which has generated the alarm.
{CLASSIFICATION} : Will be replaced with the classification description of the track causing the alarm.
...