Aamva Drivers License Barcode
- The CVP provides an effective way for AAMVA members to determine if their driver's licenses and identification (DL/ID) cards and other motor vehicle administration documents using machine readable technologies conform to the applicable AAMVA standards and specifications.
- According to the Card Design Standard by AAMVA, the PDF417 two-dimensional bar code symbology is the minimum mandatory machine-readable technology that must be present on compliant driving license/identification documents.
- AAMVA 2016 Basic Driver Licenses and Identification Cards WASHINGTON NEW LOOK AND SECURITY FEATURES Barcode Reader Calibration Sheet Washington State began issuing driver licenses and identification cards with barcodes in 2001. The Department of Licensing wants to help businesses and law enforcement to recognize and accept these cards.
Key among AAMVA's goals is improving highway safety and identification security by promoting uniform standards for all areas related to driver licensing. AAMVA is committed to improving driver safety and to the 'one driver, one record' driver's license concept.
Aamva Drivers License Barcode
Driver License's Format Recommended by (AAMVA) Track1 Format: | ||
| Field Letter | Element/Definition | Size |
| A | Start Sentinel This Character must bed used at the beginning of the track. | 1 |
| B | State of Province (addressee) (Mailing or Residential code)this field will use the ANSI D-20 standard | 2 |
| C | City This field should be truncated with a field separator ^ if less than 13 characters long. If a field separator is used, the 'NAME' field follows immediately. EXAMPLE: Bear^ | 13 |
| D | Name This field should be truncated with a field separator ^ if less than 35 characters long. If a field separator is used. The 'ADDRESS' field follows immediately. The $ symbol is to be used as a delimiter between names. EXAMPLE: Roe$Chery1$A^ EXAMPLE using 'City and Name' Bear^Roe$Chery1$A^ at this point a total of 19 bytes have been used, allowing the remainder to be used for the address. | 35 |
| E | Address This field has a minimum length of 29 which can be exceeded when utilizing the space from either the city and/or name field. The $ symbol can be used a as delimiter of multiple address lines. EXAMPLE: Using the City, Address Combination: Bear^Roe$Chery1$A^123 Something St^ | 29 |
| F | End Sentinel This character must be the next to the last character of the track. | 1 |
| G | LRC This character must be used at the end of the track. | 1 |
Track2 Format: | ||
| Field Letter | Element/Definition | Size |
| A | Start Sentinel This character must be used at the beginning of the track. | 1 |
| B | ANSI User Code This field is assigned by ANSI for the utilization of Track2 | 1 |
| C | ANSI User ID This field is the assigned identification number from ISO (International Standards Organization). | 5 |
| D | Jurisdiction ID/DL Number This field is used to represent the ID/DL number assigned by each jurisdiction. If less than 13 bytes are used the field is truncated by a field separator character. If 13 bytes are used the field separator character MUST appear in the 14th position. Overflow can be accommodated in field letter g. | 14 |
| E | Expiration Date This field will be represented in the following format YYMM. | 4 |
| F | Birthdate This field will be represented in the ANSI D-20 Standard YYYYMMDD | 8 |
| G | Remainder of Jurisdictional ID/DL This field is used to handle the overflow from the jurisdiction ID/DL field. | 5 |
| H | End Sentinel This character must be the next to the last character of the track. | 1 |
| I | LRC This character must be used at the end of the track. | 1 |
Track3 Format: | ||
| Field Letter | Element/Definition | Size |
| A | Start Sentinel This character must be used at the beginning of the track. | 1 |
| B | Template Version# Nikon capture nx2 serial key. 1 byte table, value 01-63, this field will be used to store the magnetic stripe version being used. It will be necessary to register the use with AAMVA. | 1 |
| C | Security Version #. 1 byte table, value 01-63, this field will be used to store the magnetic stripe security version used. 00 represents security is not used. | 1 |
| D | Postal Code This field will be used to store an 11 position Zip Code or the Canadian postal code. 11 Alphanumeric digits will soon be required to meet postal standards. Left justified with spaces filled. Use no hyphens. | 11 |
| E | Class This field will be alphanumeric and will represent the type of license. Use ANSI D-20 codes as modified for CDLIS. | 2 |
| F | Restrictions This field will be alphanumeric and will use the ANSI D-20 standard. | 10 |
| G | Endorsements This field will be alphanumeric and will use the ANSI D-20 standard. | 4 |
| H | Sex Represent as alphanumeric | 1 |
| I | Height Represent as numeric. See ANSI D-20 | 3 |
| J | Weight Represent as numeric. See ANSI D-20 | 3 |
| K | Hair Color Represent as alphanumeric. See ANSI D-20 | 3 |
| L | Eye Color Represent as alphanumeric. See ANSI D-20 | 3 |
| M | This field can be utilized by each jurisdiction as needed, but if used it will be necessary to register the use with AAMVA | 10 |
| N | Reserved Space This field can be utilized by each jurisdiction as needed, but if used it will be necessary to register the use with AAMVA | 16 |
| O | Error Correction This field can be utilized by each jurisdiction, but is not a mandatory field. | 6 |
| P | Security This field is for the use of each jurisdiction. | 5 |
| Q | End Sentinel This character must be the next to the last character for the track. | 1 |
| R | LRC This character must be used at the end of the track. | 1 |
Aamva Driver's License Barcode
© Copyright 2000 Escan. All Rights Reserved