Section 28: License Plate Reader

From Nlets Wiki
Jump to: navigation, search

License Plate Reader Transactions (LPQ/LPR)

Overview

The purpose of the National License Plate Reader (LPR) Sharing Program is to create a consolidated LPR repository across the US to search and locate LPR data. This will enable the Nlets authorized user community to determine if any other contributing law enforcement agency has captured a vehicle's license plate of interest. This solution will not only enhance law enforcement investigative capabilities, but also address homeland security vulnerabilities, particularly in regards to first responders.

The initial source of LPR data for the Nlets national pointer system will be states and/or federal agencies that maintain their own LPR repositories. A subset of the base LPR data (called meta data) will be extracted from these repositories and sent to Nlets for hosting in the national database. After the initial load, meta data will continue to be sent to Nlets as new LPR read events are captured. This will keep the national pointer system up-to-date with the latest information. Law Enforcement agencies, in states that have implemented the LPQ/LPR message keys, will then be able to query and obtain information about license plate read events stored in the national pointer system. To obtain detailed information about an LPR read event, will require two sets of LPQ/LPR message queries/responses. The first query will be sent to Nlets to search the meta-data database and return a set of candidate. This candidate set will provide the information necessary to issue a second query to the state's or federal agency's repository that will retrieve detailed information about the LPR read event.

The benefits in using a national pointer system for LPR are:

  • Share LPR information across jurisdictions nationwide
  • Enable law enforcement to more effectively distribute LPR information
  • Provide a cost effective solution for managing and sharing LPR data

As stated above, the LPQ and LPR message keys will support two different data exchanges. The first LPQ will be sent to Nlets to query the National LPR Pointer system where participating states have supplied Nlets with searchable LPR meta-data. This is known as the initial LPQ. The response (LPR) generated from this query will have a list of candidates that match the search criteria including the unique data capture event number and the location where the image and additional information is held.

The second LPQ is sent directly to the State housing the detailed LPR data and uses the unique event number to access additional information associated with the specific data capture event. This is known as the LPR Detail Query. The detail response (the second LPR) will contain information about the data capture event including the LPR image if requested. Note: An LPQ will need to be generated for each candidate of interest from the candidate list. If there are five candidates of interest, then five LPQs will need to be generated.

Section28-LPQ.jpg

XML and Legacy Field Requirements

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<nlets-lpr:LicensePlateReadListQuery>
  <nc:ConveyanceRegistrationPlateIdentification>
      <nc:IdentificationID>
LIC/ 1-10 Alphanumeric License
Number
<nlets-lpr:LicensePlateQueryMetadata>
  <nlets-lpr:ReasonCode>
RSN/ 1 Single letter:


N, F, V,


T, S or H.
Identify reason code:


N - Narcotics
F - Fraud (includes
counterfeit documents)
V - Violent crimes
(incl. robbery, murder,
rape, bombing, etc.)
T - Traffic violations
S - Theft


H - Humanitarian
<nlets-lpr:LicensePlateQueryMetadata>
  <nlets-lpr:CaseIdentification>
    <nc:IdentificationID>
OCA/ 1-20 Numeric Request
number
Optional Elements:
<nc:LocationAddress>
  <nc:StructuredAddress>
    <nc:LocationStateNCICLSTACode>
LOC/ 2 Alpha
Characters
State
Code
<nc:ActivityDate>
  <nc:DateTime>
BEG/ 1-20 Numeric Beginning
Date
<nc:ActivityDate>
  <nc:DateTime>
END/ 1-20 Numeric Ending
Date
<nlets-lpr:LooseMatchIndicator>
LMI/ 5 Alpha
Characters
Loose Match
on misread characters
<nlets-lpr:MaximumRecordsNumeric>
MAX/ 5 Numeric Max Number
of Records Requested
Or
<nlets-lpr:LicensePlateReadDetailQuery>
 <nlets-lpr:LicensePlateRead>
  <nc:ActivityIdentification>
   <nc:IdentificationID>
EID/ 20 Alphanumeric Event ID
<nlets-lpr:LPRQueryDateRange>
  <nc:StartDate>
    <nc:DateTime />
  </nc:StartDate>
  <nc:EndDate>
    <nc:DateTime />
  </nc:EndDate>
DAT/ 20 Numeric Date Range
Optional Element:
<nlets-lpr:BinaryRequestIndicator>
IMQ/ 5 Alpha
Characters
Image Tag

Help File

A help file of frequently asked questions can be obtained by sending an Administrative Message to NLLPRHELP.

NVS LPR Overview

National Vehicle Service (NVS) working with Locator Technologies, has partnered with an additional LPR company (PRA) to provide Law Enforcement Agencies (LEA) access to a Central Repository of LPR data from private mobile and stationary LPR machines. The companies collecting these reads include towing and repossession companies, parking lots, garages, and toll way systems. LEAs may utilize this information at no cost to augment and/or initiate criminal investigations.

The National Vehicle Service (NVS) also supports the Nlets 'RQ' message key to query their LPR database. Nlets users, in addition to being able to query the CBP Border Crossing LPR database via destination 'NA', can now also send 'RQ's to destination 'VS' to query NVS's database containing nearly 900 million LPR reads with 30 million being added per month by two data Partners.

In addition to allowing LEAs access to the database, NVS proactively searches the database against the stolen vehicle file provided by the FBI. Knowing the location of a stolen vehicle prior to or shortly after its theft will greatly enhance LEA's capabilities.

To utilize this functionality, enter VS in the State Field of the 'RQ' function, as well as the plate number and license year (standard Nlets 'RQ' query). A positive response to your query will be similar to the following sample:

RR.VANVS005V
08:59 03/29/2010 44914
08:59 03/29/2010 00604 VANVS006V
*JSPI00MX00
TXT
Vehicle license plate number 619WCX was captured by mobile license plate recognition on March 21, 2012
at 123 W Forest Brook Dr Casselberry, FL.
 
To access the complete LPR data record including other additional historical LPR scans, vehicle images
and satellite map overlays, please proceed to the following Internet Website:
http://platenet.net/nlets register and enter the (Platenet code) to be used for your free plate search)
 
** CAVEAT **
This is lead information ONLY to assist with your investigation and should NOT be used for non-law
enforcement purposes. Should you require additional assistance with this RESPONSE, please contact
National Vehicle Service at 866-687-1102.

Help File

A help file for NVS can be obtained by sending an Administrative Message to VSADMHELP.

CBP LPR Overview

License Plate Readers (LPR's) were initially installed by the United States Custom and Border Protection (CBP) to develop and track movement of vehicles as they crossed through the ports of entry along the southwest border between the United States and Mexico and the northern border between the United States and Canada. One of the benefits of the LPR is their effectiveness relating to vehicle theft initiatives regarding stolen vehicles entering and exiting the United States. Because of their benefits of providing investigative information regarding stolen vehicles, CBP agreed to provide NICB the raw LPR data as a tool in its efforts to prevent and investigate vehicle theft and insurance fraud.

The NICB in cooperation with the United States Custom and Border Protection and the International Justice and Public Safety Information Sharing Network (NLETS), will be adding an RQ transaction which will provide the capability to initiate a LIC query to NICB against the LPR file.

An RQ transaction is sent with the license plate of interest to destination NA as the state designator for NICB.

*** IMPORTANT ****


The RQ does allow for a 10 character license plate, but the LPR records only
captures 8 characters. Therefore, if a 9 or 10 RQ is received, a search will
be conducted only on the first 8 characters.

NICB will respond with a RR message consisting of the following information:

NICB RESPONSE FOR LIC/FT20688 MSG 001 OF 001
CROSSING LOCATION: INBOUND
ADDRESS: USCS-107 INTERSTATE SOUTH
CITY: DERBY LINE:INTERSTATE STATE: VT ZIP: 05830
CROSSING DT/TIME: 09/30/2002 14.31.29
LIC PLATE: FT20688 STATE: PQ COUNTRY: C
 
** NOTICE **
THE NICB PROVIDES THE INFORMATION CONTAINED HEREIN SOLELY
AS AN INVESTIGATORY AID. SINCE THESE RECORDS ARE NOT
VALIDATED, THE NICB DOES NOT GUARANTEE OR WARRANT THEIR
LEGITIMACY. PLEASE USE SECONDARY VERIFICATION BEFORE YOU
TAKE ANY ENFORCEMENT ACTION.

The following fields are included in the LPR response:

Address of the Crossing Location:
Inbound/Outbound Indicator
Crossing Date/Time: (Military time will be displayed in hour/minute/second format)
LIC Plate #:
LIC State:
Country Code:

Not all borders crossings contain readers. The borders that do have readers are based on priorities established by CPB. Not all 50 state plates are recognized by the readers. The LPR software is programmed to read plates from the states that represent the largest percentage of crossings at a specific location. Some of the readers are programmed to read plates from Mexico and Canada. LPR data in maintained for 12 months. At the 13th month, the 1st month's data is dropped from the file.

If a query gets multiple hits. The RR message will contain 7 LPR hits. If there are more that 7 hits, you will receive multiple messages stating "message 1 of ?" There is no limit on the number of hits that may possibly be received.

LPR from NVS & CBP

If a user would like to receive information from both NVS and CBP from a single Vehicle Registration transaction (RQ) than a destination of LP should be used instead of NA or VS.

Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

License Plate Reader NIEM Specifications

This section describes message specifications and formats so that agencies may utilize the License Plate Reader resources. License Plate Readers (LPR's) were initially installed by the United States Custom and Border Protection (CBP) to develop and track movement of vehicles as they crossed through the ports of entry along the southwest border between the United States and Mexico and the northern border between the United States and Canada. One of the benefits of the LPR is their effectiveness relating to vehicle theft initiatives regarding stolen vehicles entering and exiting the United States. Because of their benefits of providing investigative information regarding stolen vehicles, CBP agreed to provide NICB the raw LPR data as a tool in its efforts to prevent and investigate vehicle theft and insurance fraud.

Effective Friday, March 25, 2005 the NICB in cooperation with the United States Custom and Border Protection and the International Justice and Public Safety Information Sharing Network (Nlets), will be adding an RQ transaction which will provide the capability to initiate a LIC query to NICB against the LPR file.

LPR Queries are generated as standard RQ messages on license plate and are sent to the destination NA. NA will return an RR response.

Element Dictionary

Transaction types detailed below include: Query by License Plate, Year, Type (RQ) and Response to License Plate Query (RR).

Query Formats

Query by License Plate, Year, Type (RQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Vehicle
  A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.

    nc:ConveyanceRegistrationPlateIdentification
    An identification on a metal plate fixed to a conveyance.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the license plate number to be queried.

      nc:IdentificationCategoryText
      A kind of identification.
      This element should contain the type of license plate being queried. Allowable values come from the NCIC LIT
      code table.

      nc:IdentificationExpirationDate
      A date after which an identification is no longer valid.

        nc:Date
        A full date.
        This element's value should be the expiration date of the license plate, also known as the plate year. The value
        should be in the format YYYY. For non-expiring plates NX or YYYY may be entered.

  n2:HistoryRequestIndicator
  This optional element can be used to indicate that a registration history is requested, if available. The element will
  only be passed onto XML states and will be stripped from queries to legacy states. Value should be boolean.

Response Formats

Response to license plate query (RR)

Response Data (n:NLETSResponseData)
This element will contain all elements specific to this transaction.

  Response Text (n:ResponseText)


  This element will contain the free text response. Nlets recommends the use of

<!&#91;CDATA&#91;&#93;&#93;>

tags to ensure that the


  response does not contain any characters illegal in XML.

License Plate Reader NIEM Examples

Example 1: A license plate reader list query.

<n2:NLETS n2:version="4.0" xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" 
xmlns:nlets-lpr="http://www.nlets.org/niem2/lpr/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>LPQ</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>NL</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>NLETSTEST1</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSInquiryData n2:key="LPQ">
		<nlets-lpr:LicensePlateReadListQuery>
			<nc:ConveyanceRegistrationPlateIdentification>
				<nc:IdentificationID>ABC123</nc:IdentificationID>
			</nc:ConveyanceRegistrationPlateIdentification>
		</nlets-lpr:LicensePlateReadListQuery>
		<nlets-lpr:LicensePlateQueryMetadata>
			<nlets-lpr:ReasonCode>N</nlets-lpr:ReasonCode>
			<nlets-lpr:CaseIdentification>
				<nc:IdentificationID>123</nc:IdentificationID>
			</nlets-lpr:CaseIdentification>
		</nlets-lpr:LicensePlateQueryMetadata>
	</n2:NLETSInquiryData>
</n2:NLETS>

Example 2: A license plate reader detailed query.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" 
xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nlets-lpr="http://www.nlets.org/niem2/lpr/1.0"> 
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>LPQ</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>NL</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText><![CDATA[NLETSTEST1]]></nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSInquiryData n2:key="LPQ">
		<nlets-lpr:LicensePlateReadDetailQuery>
			<nlets-lpr:LicensePlateRead>
				<nc:ActivityIdentification>
					<nc:IdentificationID>1234567890</nc:IdentificationID>
				</nc:ActivityIdentification>
				<nc:ActivityDate>
					<nc:DateTime>20120612</nc:DateTime>
				</nc:ActivityDate>
			</nlets-lpr:LicensePlateRead>
		</nlets-lpr:LicensePlateReadDetailQuery>
		<nlets-lpr:LicensePlateQueryMetadata>
			<nlets-lpr:ReasonCode>N</nlets-lpr:ReasonCode>
			<nlets-lpr:CaseIdentification>
				<nc:IdentificationID>123456</nc:IdentificationID>
			</nlets-lpr:CaseIdentification>
		</nlets-lpr:LicensePlateQueryMetadata>
	</n2:NLETSInquiryData>
</n2:NLETS>

Example 3: A license plate reader list response.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.0/" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" 
xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" 
xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>LPR</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>NL0000000</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
		<nh2:MessageReceiveDate>06/10/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>16:13</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>06/10/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>16:13</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>11918</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00125</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSInquiryData n2:key="LPQ">
		<nlets-lpr:LicensePlateReadListQuery xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http://www.nlets.org" xmlns:nlets-lpr="http://www.nlets.org/niem2/lpr/1.0">
			<nc:ConveyanceRegistrationPlateIdentification>
				<nc:IdentificationID>ABC123</nc:IdentificationID>
			</nc:ConveyanceRegistrationPlateIdentification>
		</nlets-lpr:LicensePlateReadListQuery>
	</n2:NLETSInquiryData>
	<n2:NLETSResponseData n2:key="LPR">
		<nlets-lpr:LicensePlateReadResponse xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http://www.nlets.org" xmlns:nlets-lpr="http://www.nlets.org/niem2/lpr/1.0">
			<nlets-lpr:LicensePlateRead s:id="ACT1">
				<nc:ActivityIdentification>
					<nc:IdentificationID>NLETSTEST1</nc:IdentificationID>
				</nc:ActivityIdentification>
				<nc:ActivityDate>
					<nc:DateTime>2000-01-01T00:00:00</nc:DateTime>
				</nc:ActivityDate>
				<nlets-lpr:LPRVehicle>
					<nc:ConveyanceRegistrationPlateIdentification>
						<nc:IdentificationID>ABC123</nc:IdentificationID>
					</nc:ConveyanceRegistrationPlateIdentification>
				</nlets-lpr:LPRVehicle>
				<nlets-lpr:ReadLocation>
					<nc:LocationAddress>
						<nc:StructuredAddress>
							<nc:LocationStreet>
								<nc:StreetFullText>NLETS</nc:StreetFullText>
							</nc:LocationStreet>
						</nc:StructuredAddress>
					</nc:LocationAddress>
					<nc:LocationTwoDimensionalGeographicCoordinate>
						<nc:GeographicCoordinateLatitude>
							<nc:LatitudeDegreeValue>0</nc:LatitudeDegreeValue>
							<nc:LatitudeMinuteValue>0</nc:LatitudeMinuteValue>
							<nc:LatitudeSecondValue>0</nc:LatitudeSecondValue>
						</nc:GeographicCoordinateLatitude>
						<nc:GeographicCoordinateLongitude>
							<nc:LongitudeDegreeValue>0</nc:LongitudeDegreeValue>
							<nc:LongitudeMinuteValue>0</nc:LongitudeMinuteValue>
							<nc:LongitudeSecondValue>0</nc:LongitudeSecondValue>
						</nc:GeographicCoordinateLongitude>
					</nc:LocationTwoDimensionalGeographicCoordinate>
				</nlets-lpr:ReadLocation>
				<nlets-lpr:LPRCameraIdentification>
					<nc:IdentificationID>0</nc:IdentificationID>
					<nc:IdentificationSourceText>NLETS</nc:IdentificationSourceText>
				</nlets-lpr:LPRCameraIdentification>
				<nlets-lpr:LPRThumbnailImage />
				<nlets-lpr:ConfidenceLevelText>0</nlets-lpr:ConfidenceLevelText>
			</nlets-lpr:LicensePlateRead>
			<nlets-lpr:LPRRecordHoldingOrganizationAssociation>
				<nc:ActivityReference s:ref="ACT1" />
				<nc:OrganizationReference s:ref="ORG1" />
			</nlets-lpr:LPRRecordHoldingOrganizationAssociation>
			<nlets-lpr:Organization s:id="ORG1">
				<j4:OrganizationAugmentation>
					<j4:OrganizationORIIdentification>
						<nc:IdentificationID>NLETS</nc:IdentificationID>
						<nc:IdentificationJurisdictionText>NLETS</nc:IdentificationJurisdictionText>
					</j4:OrganizationORIIdentification>
				</j4:OrganizationAugmentation>
			</nlets-lpr:Organization>
		</nlets-lpr:LicensePlateReadResponse>
	</n2:NLETSResponseData>
</n2:NLETS>

Example 4: A license plate reader detailed response.

Top

Legacy (DEPRECATED)

License Plate Reader Legacy Specifications

This section provides Legacy formats and examples for the License Plate Reader (LPQ/LPR) Transactions.

Query Formats

Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
LIC/ 1-10 Alphanumeric License
Number
Optional Elements:
LOC/ 2 Alpha
Characters
State
Code
BEG/ 1-20 Numeric Beginning
Date
END/ 1-20 Numeric Ending
Date
LMI/ 5 Alpha
Characters
Loose Match
on misread characters
MAX/ 5 Numeric Max Number
of Records Requested
Or
EID/ 20 Alphanumeric Event ID
DAT/ 20 Numeric Date Range
Optional Element:
IMQ/ 5 Alpha
Characters
Image Tag
License Plate Reader Legacy Examples

Example 1: A license plate reader list query.

LPQ.AZNLETS20.NL.TXT
LIC/ABC123

Example 2: A license plate reader detailed query.

LPQ.AZNLETS20.AL.TXT
EID/1234567890.DAT/20120612

Top

Downloads

Download LPQ Schema (updated 5/29/2019)

Download LPQ Stylesheet

Download LPR Schema (updated 5/29/2019)

Download LPR Stylesheet

Top