NIEM Examples - License Plate Reader (LPQ/LPR)
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 Customs 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 Customs 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
<![CDATA[]]>
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.