LPR POLICE 14.10
G. O. 14.10
TEQUESTA POLICE DEPARTMENT
GENERAL ORDER
TITLE: LICENSE PLATE RECOGNITION (LPR) CAMERA SYSTEM
GENERAL ORDER: 14.10
EFFECTIVE: August 15, 2010
RESCINDS: New
PAGES: 4
CONTENTS:
This order consists of the following numbered sections:
I. SYSTEM DESCRIPTION
II. TYPES OF QUERIES
III. ADDITIONAL FEARUTES OF SYSTEM
IV. COMMUNICATION RESPONSIBILITIES
V. ROAD PATROL
VI. PURSUITS
VII. GLOSSARY
PURPOSE:
To establish guidelines for the License Plate Recognition technology.
SCOPE:
This order applies to all Police Department members.
DISCUSSION:
License Plate Recognition (LPR) technology is used for identifying and reading vehicle license
plates. LPR cameras are placed on Country Club Dr. at the north gate to the Tequesta Country Club. The camera
will take a picture of the vehicle and license plate when a license plate passes the camera’s field of view. Once a
license plate is read by the system, a search is conducted of a hotlist provided by FDLE. This hotlist contains
possible stolen license plates, stolen vehicles, wanted persons and other intelligence information important to
law enforcement. If a license plate inquiry matches one on the hotlist it will active an audible and visual signal
on the computer monitoring the LPR system.
POLICY:
Any hits or intelligence gathered from the LPR technology will be handled in conformance with this
order.
PROCEDURE:
I. SYSTEM DESCRIPTION:
A.
The LPR Camera System takes a digital photograph of every vehicle and license tag that enters its field of
view. It then searches a hotlist to see if the tag is wanted for any reason.
B.
The LPR Camera System does not conduct a live check against FCIC or NCIC. But rather, the system
conducts checks against a hotlist database which is periodically downloaded throughout the day from
FDLE.
C.
The system then searches the hotlist for the license plate detected.
D.
The system downloads the FCIC hotlist every 3 hours and the NCIC hotlist once a day.
E.
The system is unable to determine the type of license plate detected. E.g. the system may detect tag
1
G. O. 14.10
ABC123, but cannot determine if the tag is Florida or an alternative state or country.
F.
As a result, every tentative hit by the LPR System must be verified via a live query transaction through
FCIC/NCIC by the Dispatcher before any contact is initiated. A “tentative hit” by the LPR System prior to
a live query transaction through FCIC/NCIC by the dispatcher is not probable cause to conduct a stop or
the vehicle.
II. TYPES OF QUERIES:
A
. The LPR System is capable of conducting various types of queries that may include:
1.
FCIC/NCIC Warrant checks
2.
Persons checks
3.
Missing persons checks
4.
Wanted persons
5.
Stolen Vehicles
6.
Stolen Tags
7.
Protection orders, Domestic violence injunctions
8.
Gang and terrorists watch lists
9.
Felons on release programs
10.
Inmate release program
III. ADDITIONAL FEATURES OF SYSTEM
A. Searches
1. The LPR System allows for searches to be run by tag, camera location and/or time frame.
2. Select personnel within the Department will be trained and authorized to conduct searches of
the LPR database.
B. Flagged vehicles
1.
With the approval of a supervisor, the dispatcher can enter a license plate of a vehicle of
interest into the LPR system to alert when the plate is detected entering the city or
designated area by one of the LPR cameras.
2.
Officers requesting a vehicle be flagged in the LPR system must complete a request form
(LPR Flagged Vehicle Entry), and have it approved by a supervisor.
3.
Each entry shall include the following information:
a
. Date of entry;
b
. License plate number and state;
c.
Vehicle description;
d.
Requesting officer’s name and ID;
e.
Approving supervisors name and ID;
f.
Case number;
g.
Reason for entry;
h.
Action to take;
1)
Stop and interview driver
2)
Notify specific officer
3)
Do not stop, monitor only
4.
The dispatcher shall enter all flagged vehicles in the LPR Flagged Vehicle Log.
A. Covert Entries
1.
With the approval of the Chief of Police a covert entry of a license plate of a vehicle of interest may
be entered into the LPR system to alert specified personnel.
2.
Covert entries will not alert the dispatcher through the monitors in dispatch, but will send an alert
directly to the specified personnel.
3.
Each covert entry shall include the following information:
a
. Date of entry;
b.
License plate number and state;
2
G. O. 14.10
c.
Vehicle description;
d.
Requesting officer’s name and ID;
e.
Approving supervisors name and ID;
f.
Case number;
g.
Reason for entry;
h.
Action to take;
1)
Stop and interview driver
2)
Notify specific officer
3)
Do not stop, monitor only
IV. Communications Responsibilities:
Upon notification of a tentative hit by the LPR system the dispatcher shall;
A.
Immediately compare the alert obtained by the LPR system against the actual tag displayed on the
LPR photo, and verify it is the same tag number and state; next verify hit through FCIC/NCIC.
B.
Confirm hit with FCIC/NCIC
1. After the hit is confirmed notify the correct zone unit of the tag details.
a.
Nature of alert (stolen vehicle, stolen tag, wanted person etc.);
b.
Vehicle description, if known;
c.
Tag number;
d.
The camera location;
e.
Direction of travel.
C
. The dispatcher will attempt to obtain any other information that may be available and notify
responding units of that information, as soon as possible.
V. Road Patrol:
A.
Upon being notified of a tentative hit a patrol unit will be dispatched to the area to intercept the
subject vehicle.
B.
Unless the officer has independent probable cause to make a stop, the office shall not make any
contact with the subject vehicle until the alert is verified as active through FCIC/NCIC.
C.
If a live query transaction is verified as active and the vehicle is located, the assigned officer will
have the dispatcher confirm the validity with the entering agency.
D.
Once the entry is confirmed with the entering agency, the officer will advise the dispatcher to
change the header accordingly (i.e., stolen vehicle, stolen tag, wanted person etc.)
E.
If the live query transaction is verified through FCIC/NCIC but the vehicle is not located, the
assigned officer shall document the incident in CAD entry titled “LPR Incident”
F.
If the tag is not a match, the assigned officer shall code the call in CAD as a “LPR Incident” and
put LPR misread in the CAD narrative.
G.
In the event an alert of an outbound vehicle exiting the City, the dispatcher shall immediately
notify MCSO of the alert information.
H.
All traffic stops initiated as a result of a confirmed hit will be made in strict accordance with
General Order 14.1, Traffic Law Enforcement, Paragraph IV, Vehicle Stops, Sub Paragraph B,
High Risks Stops.
VI. Pursuits:
Should an officer encounter a motorist who flees or refuses to stop upon verification of a hit
confirmation, General Order 12.2, Pursuits, will be strictly adhered to.
VII. Glossary:
LPR - License Plate Recognition
Alert - An alert of a tag by the PR system that has NOT BEEN VISULLAY VERIFIED by the
dispatcher against the photo in the LPR system.
3
G. O. 14.10
Tentative Hit - An alert by the LPR system that HAS BEEN VISUALLY VERIFIED by the
dispatcher against the LPR hotlist and photo but HAS NOT BEEN QUERIED in FCIC/NCIC by
dispatcher or an officer as a live query transaction OR CONFIRMED AS VALID with the
original entering agency.
Live Query Transaction - A hit by the LPR system that HAS BEEN QUERIED as active in the
FCIC/NCIC system but HAS NOT BEEN CONFIRMED as valid by the entering agency.
Confirmation (Confirmed Hit) - A hit by the LPR system that HAS BEEN CONFIRMED as
valid and active by the original entering agency through FCIC/NCIC teletype by dispatcher.
INDEXING:
LPR
LICENSE PLATE RECOGNITION CAMERA SYSTEM 14.10
DRAFTED:
JG/July 2010/filed: License Plate Recognition Camera System 14.10
APPROVED:
Pete Pitocchelli, Chief DATE: November 05, 2011
Tequesta, Florida
4