This is an old revision of the document!

Overview

The LPR hit list is a report designed to communicate the status of all hits received in the system from LPR system interfaces:
- Vigilant
It lists all hits that have been received in the provided date range, and can be filtered with a variety of different parameters

Access

When accessed via the administrative menu, as shown below, it can display hits from any LPR company and be grouped by company:

When accessed via an LPR company menu, hits are limited to those related to the company:

Row ID: the internal system-assigned row ID for the LPR hit
Type: the type of hit
- UnauthVeh: an unauthorized vehicle hit, generally due to a plate not being on the allowlist
- Hotlist: a hotlist hit, generally due to a plate not being on the hotlist (e.g., guest permits in wrong space, etc.)
- ExpPark: a hit related to chalking, generally caused by a plate being parked too long in the same space
- ExcDetect:
Lic plate: the license plate read by the LPR system, or edited by the spotter
Lic st: the license plate state provided by the LPR system
Vio ID: the violation ID created by Ranger and linked to the LPR hit, if in fact the hit results in a violation
Ext sys ID: the unique system ID assigned to the hit by the LPR system
Proc stat: the status of the LPR hit assigned by Ranger, whether an interim step in processing or a final status
- Empty: new hit
- V: violation created and linked
- V+I: violation created and linked, and LPR images saved
- V+I+NM: violation created and linked, LPR images saved, but no LPR supplemental data from Patrol Works app matched after 30 minutes
- V+I+M: violation created and linked, LPR images saved, and LPR supplemental data from Patrol Works app matched and saved
Created:
Event time:
Location:
Processed:
Company:
LotP:
Property:

A new hit will look like the one on row 1, Row ID 8825, shown below:
- The Vio ID', Proc stat, Processed, LotP, and Property'' columns will be empty