support:08_private_property_tows:21_lpr_hit_list
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:
It lists all hits that have been received in the provided date range, and can be filtered with a variety of different parameters
Access
Column definitions
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 :
V+I+M :
VCAN :
An LPR hit that indicates hit cancellation (e.g., plate that contains 00000) is received, and cancels any other hits that match on Ext sys ID.
If the hit with this status has a violation ID, that means a violation was in fact created and subsequently cancelled.
If no violation ID is listed, the hit was cancelled before a violation could be created.
LPLM :
(e.g., local plate list match), the plate on the LPR hit was found on a Ranger local plate list, so processing of the hit is ended and no violation is created
LPLMFUZZY :
(e.g., local plate list fuzzy match), the plate on the LPR hit was found on a Ranger local plate list using a fuzzy search
Fuzzy search considers 0, O, and D to be the the same for matching purposes
Processing of the hit is ended and no violation is created
ERR : ????
ERRNOLOT : (e.g., error, no lot match), an error that indicates that no lot in Ranger matches the LPR hit location/lot name, so processing of the hit is ended and no violation is created
ERRNOHLPM : (e.g., error, no hotlist match for the plate), an error that indicates that plate in the LPR hit does not match a Ranger hotlist plate, so processing of the hit is ended and no violation is created
ERRCNLMN : (e.g., error, cancellation hit has no plate match), an error that indicates that an LPR hit which represents a cancellation never matches another LPR hit, so processing of the hit is ended and no violation is created
DUPE : (e.g., duplicate hit), an error that indicates that an LPR hit appears to duplicate another recently received hit, so processing of the hit is ended and no violation is created
Created: time the LPR hit was created in Ranger, in Ranger timezone
Event time: time the LPR hit was created by the mobile LPR system, in customer timezone
Location: the location provided in the LPR hit
Processed:
Company:
LotP:
Property:
Basic hit processing
New hit
support/08_private_property_tows/21_lpr_hit_list.1653329187.txt.gz · Last modified: 2022/05/23 14:06 by edmondsj