RangerSST Support Center

User Tools

Site Tools

You are here: start » support » 08_private_property_tows » 21_lpr_hit_list
support:08_private_property_tows:21_lpr_hit_list

This is an old revision of the document!

Table of Contents

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:

lpr_hit_list_1.jpg

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

lpr_hit_list_2.jpg

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
    • This is the LPR system ID that links hits with corrections (e.g., initial read by mobile LPR system and follow-up correction, such as 00000)
  • 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
      • LPR images saved
      • System continuing to look for an LPR supplemental data match, in progress
    •  V+I+NM :
      • violation created and linked
      • LPR images saved
      • no LPR supplemental data from Patrol Works app matched after 30 minutes
    •  V+I+M :
      • violation created and linked
      • LPR images saved
      • LPR supplemental data from Patrol Works app matched and saved
    •  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 :
      • Error, 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
      • Likely causes:
        • A brand new permit was recently purchased, but has not yet been communicated from Ranger to Vigilant
    •  LPLMFUZZY :
      • Error, 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
      • Likely causes:
        • A brand new permit was recently purchased, but has not yet been communicated from Ranger to Vigilant
    •  ERRML :
      • Error, multiple lots match LPR hit location
      • Processing of the hit is ended and no violation is created
      • Fixes:
        • Navigate to Lot spreadsheet screen and remove or edit the Vigilant location name in the Vig loc name column for at least one lot
    •  ERRNOLOT :
      • Error, no lot match
      • An error that indicates that no lot in Ranger matches the LPR hit location/lot name
      • Processing of the hit is ended and no violation is created
      • Fixes:
        • Navigate to Lot spreadsheet screen and enter a Vigilant location name in the Vig loc name column, or
        • In Vigilant client portal, remove the location from Vigilant
    •  ERRNOHLPM :
      • Error, no hotlist match for the plate
      • An error that indicates that plate in the LPR hit does not match a Ranger hotlist plate
      • Processing of the hit is ended and no violation is created
    •  ERRCNLNM :
      • Error, cancellation hit has no plate match
      • An error that indicates that an LPR hit which represents a cancellation never matches another LPR hit
      • Processing of the hit is ended and no violation is created
    •  DUPE :
      • Error, duplicate hit
      • An error that indicates that an LPR hit appears to duplicate another recently received hit
      • 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: the last time the LPR hit was touched during processing in Ranger, in Ranger timezone
  • Company: the company name of the LPR company
  • LotP: if the LPR hit results in a violation, this is the Ranger lot name
  • Property: if the LPR hit results in a violation, this is the Ranger property name

Basic hit processing

New hit

  • 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

lpr_hit_list_3.jpg

support/08_private_property_tows/21_lpr_hit_list.1654859792.txt.gz · Last modified: 2022/06/10 07:16 by edmondsj

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki