About matcher settings files - SharpV | SharpOS 13.6

AutoVu™ SharpV Deployment Guide 13.6

Product
SharpOS
SharpV
Content type
Guides > User guides
Version
13.6
Language
English
Last updated
2022-07-19

When dirty or damaged license plates are misread by a Sharp camera, different methods are available for matching the plate read to a permit. Which matcher settings file you need to configure depends on the AutoVu™ installation type.

The following ALPR matcher files and settings are available on the ALPR server:

ALPR matcher File or setting Location
General matcher MatcherSettings.xml C:\Program Files\Genetec Security Center X.X.
Pay-by-Plate Sync matcher Genetec.Plugins.MobilePBP.dll.config C:\Program Files (x86)\Security Center Plugins\MobilePBP
AutoVu™ Free-Flow setting Match tolerance threshold AutoVu™ Free-Flow section of the ALPR Manager Properties page

Fixed SharpV cameras using AutoVu™ Free-Flow and the Pay-by-Plate Sync plugin

In this case, the Pay-by-Plate Sync matcher settings are used to validate license plate reads at the parking lot entrance against the Security Center permit file that has been updated with third party permits by Pay-by-Plate Sync.

The Match tolerance threshold setting is used to close parking sessions if the plate is misread at the parking lot exit.

NOTE: In the following example, the matcher settings allow one OCR equivalent character.

Fixed SharpV cameras using AutoVu™ Free-Flow without the Pay-by-Plate Sync plugin

In this case, the general matcher file is used to validate license plate reads at the parking lot entrance against the Security Center permit list. No third-party lists are involved in this scenario.

The Match tolerance threshold setting is used to close parking sessions if the plate is misread at the parking lot exit.

NOTE: In the following example, the matcher settings allow one OCR equivalent character.

Mobile cameras using the Pay-by-Plate Sync plugin

In this case, the general matcher file is used to validate license plate reads against the Genetec Patroller™ permit file that has been updated with third party permits by Pay-by-Plate Sync.

When the system performs a last chance lookup to verify that the permit has not recently been added to the list, no matcher settings are applied. Only an exact match triggers a violation.

NOTE: In the following example, the matcher settings allow one OCR equivalent character.

Mobile SharpX cameras without the Pay-by-Plate Sync plugin

In this case, the general matcher file is used to validate license plate reads against the Genetec Patroller™ permit file that has been updated with the current Security Center permit list.

When the system performs a last chance lookup to verify that the permit has not recently been added to the list, no matcher settings are applied. Only an exact match triggers a violation.

NOTE: In the following example, the matcher settings allow one OCR equivalent character.