A NIST file has up to 16 Records, each of which have fields with subfields that hold data. At each
level there are different separator characters as shown below.
FILE
RECORD
Field
Subfield
US
Subfield
US
RS
Field
RS
GS
RECORD
GS
FS
Each file is separated by the FS "file separator" character, which is represented in
ANSI as 001 1100
Hexadecimal as 1c
Decimal as 28
Each record is separated by the GS "Group Separator" character, which is represented in
ANSI as 001 1101
Hexadecimal as 1d
Decimal as 29
Each Field is separated by the RS "Record Separator" character, which is represented in
ANSI as 001 1110
Hexadecimal as 1e
Decimal as 30
Each subfield is separated by the US "Unit Separator" character, which is represented in
ANSI as 001 1111
Hexadecimal as 1f
Decimal as 31
Each Record holds a different type of data.
1 - Transaction Information
This record contains the number of fingerprint, palmprint,
facial/mugshot, or SMT images available for processing; lists all other records included in the file,
and indicates the source of the physical record.
The Type-1 logical record is mandatory, must be first and alone, and is encoded in ASCII. There are
eight mandatory fields and two optional fields.
This mandatory ASCII field contains the total number of bytes in the record.
Field 1.001 begins with "1.001:", followed
by the length of the record, which includes every character of every field as well as the information separators.
Field 1.002: Version number (VER)
This mandatory four-byte ASCII field specifies the current version of ANSI
standard used by the software that created the file. The first two
characters specify the major version number and the last two characters specify the minor revision number.
The initial revision number for a version is "00". The 2000 approved standard carries the value "0300",
which signifies the inclusion of the Type-10 through Type-16 image records.
Usually defaulted by the sending device/system.
Field 1.003: File content (CNT)
This mandatory field identifies each of the logical records in the file by record type. It
also specifies the order in which the remaining logical records appears in the file.
The CNT field contains two or more subfields, each of which describe a single logical record in the
same order in which the logical records appear.
The first subfield contains: 1 (indicating this is a Type-1 record), followed by
the sum of all the other records contained in this file.
The remaining subfields - which each relate to a single logical record
contained in the file - contain: a number from 2 to 16 that identifies the record type, followed by the IDC
which identifies the subfield within that record.
Field 1.004: Type of transaction (TOT)
This mandatory field designates the type of transaction and subsequent processing that this file
should be given.
Field 1.005: Date (DAT)
This mandatory field contains the start date of the transaction, in the format YYYYMMDD.
For example, "20000103" represents January 3, 2000.
Field 1.006: Priority (PRY)
This optional field designates the urgency with which a response is desired. The values
range from 1 (highest priority) to 9.
Field 1.007: Destination agency identifier (DAI)
This mandatory field contains which administration or organization should
receive the transmission.
Field 1.008: Originating agency identifier (ORI)
This mandatory field contains which administration or organization sent the transmission.
Field 1.009: Transaction control number (TCN)
This mandatory field contains the unique alphanumeric Transaction Control Number as assigned by the originating
agency. The TCN will be referred to when sending a response.
“Process Control Number (PCN)” is SAGEM MORPHO’s term for the transaction tracking number.
The PCN used for the New Jersey State Police Department Fully Integrated Fingerprint Identification System
is derived by combining the booking site municipal code (MUN), scanning device identification number (LSID)
and a unique number (UNI) together as one element.
Field 1.010: Transaction control reference (TCR)
This optional field is used for responses
that refer to the TCN of a previous transaction
involving an inquiry or other action that required a
response.
Field 1.011: Native scanning resolution
(NSR)
This mandatory field specifies the native scanning resolution of the AFIS or other fingerprint
or palmprint image capture device supported
by the originator of the transmission. This field
permits the recipient of this transaction to send
response data at a transmitting resolution tailored
to the NSR (if it is able to do so) or to the minimum
scanning resolution. This field contains
five bytes specifying the native scanning resolution
in pixels per millimeter. The resolution shall
be expressed as two numeric characters followed
by a decimal point and two more numeric characters
(e.g., 19.69). This field is needed because
the interchange of fingerprint information between
systems of the same manufacturer may, in some
instances, be more efficiently done at a transmitting
resolution equal to the native scanning resolution
of the system rather than at the minimum
scanning resolution specified in this standard.
For applications other than fingerprint where
resolution is not a factor or not applicable (such a
facial or SMT image) this field shall be set to
"00.00".
Note: each of the following logical records include an Image Designation Character (IDC),
which relates items in the file contents field of the Type-1 record to each record.
The IDC identifies and links logical records on the same subject matter. The IDC's value starts
from zero and increments by one. Different records that deal with the same subject matter will have
the same IDC - for example, a high-resolution image record of a specific fingerprint and the
corresponding minutiae record for the same finger would carry the same IDC number.
2 - Descriptive Text (User-defined)
The Type-2 record is composed of user-defined textual fields providing identification and descriptive
information about the subject of the fingerprint information.
The first two fields are mandatory,
after which there can be up to 997 user-defined optional fields.
This mandatory ASCII field contains the
length of the logical record specifying the total
number of bytes, including every character of
every field contained in the record.
Field 2.002: Image designation character (IDC)
This mandatory field identifies the
user-defined text information contained in this
record. The IDC contained in this field shall be
the IDC of the Type-2 logical record as found in
the file content (CNT) field of the Type-1 record.
2.003 - 2.999: User-defined fields
Different organizations can chose to add fields that give additional information about
the person. Possible values include the person's sex, age, race, date of birth, and
other demographic information.
The following are the FBI specifications for Type-2 records:
2.005: Retention Code
2.006: Attention Indicator
the person to whom a response should be directed.
2.007: Send Copy To
where to send responses.
2.009: ORI Case Number
2.014: FBI Number
2.015: SID Number
State ID.
2.016: Social Security Number
2.017: Misc. ID Number
2.018: Name
2.019: Alias
2.020: Place of Birth
2.021: Citizenship
2.022: Date of Birth
2.023: Gender
2.024: Race
2.039: Employer and address
2.040: Occupation
2.041: Residence
the current address of the subject.
2.059: Search Results Finding
I for identified, N for not identified.
2.060: Error message
returned if the IAFIS failed to process the record.
2.071: Action to be Taken
2.073: Controlling/Booking Agency Identifier
2.075: Electronic Rap Sheet
2.085: Civil Record Number
only returned when an identification is made against
a civil file.
3 - Fingerprint Image Data (Low-resolution grayscale)
Type-3 logical records contain low-resolution grayscale fingerprints
that were subsampled, scaled down, or interpolated from higher-quality scans.
Typically, there are ten rolled impressions of the individual fingers, two plain impressions
of the thumbs, and two "slaps". There can be up to 13 images in a file,
each of which uses a separate Type-3 logical record.
The Type-3 record has 9 ordered, unnumbered fields, the first 8 of which contain information
about the image data stored in the 9th field. All the values are stored in binary.
This mandatory four-byte binary field, which occupies bytes one through four, contains the
total length of this record in bytes.
Image designation character (IDC)
This mandatory one-byte binary field, which occupies the fifth byte of a Type-3 record, identifies
the image data contained in this record. This IDC must match the IDC in the file content
(CNT) field of the Type-1 record.
Impression type (IMP)
This mandatory one-byte binary field, which occupies the sixth byte of a Type-3 record, contains
a code that describes how the fingerprint image information was obtained.
0 - Live-scan plain
1 - Live-scan rolled
2 - Nonlive-scan plain
3 - Nonlive-scan rolled
4 - Latent impression
5 - Latent tracing
6 - Latent photo
7 - Latent lift
Finger position (FGP)
This mandatory six-byte field occupies the seventh through twelfth byte positions of a Type-3 record.
It contains a code that corresponds to possible finger positions.
0 - Unknown
1 - Right thumb
2 - Right index finger
3 - Right middle finger
4 - Right ring finger
5 - Right little finger
6 - Left thumb
7 - Left index finger
8 - Left middle finger
9 - Left ring finger
10 - Left little finger
11 - Plain right thumb
12 - Plain left thumb
13 - Plain right four fingers
14 - Plain left four fingers
Up to five additional finger positions may be added in the remaining five bytes; any unused bytes are
filled with the binary equivalent of "255".
Image scanning resolution (ISR)
This mandatory one-byte binary field occupies the thirteenth byte of a Type-3 record. It
contains a binary value of "0" if half the minimum scanning resolution is used, and a "1" if half the
native scanning resolution is used.
Horizontal line length (HLL)
This mandatory two-byte binary field, which occupies the fourteenth and fifteenth bytes of the Type-3
record, specifies the number of pixels contained on a single horizontal line of the transmitted image.
Vertical line length (VLL)
This mandatory two-byte binary field, which occupies the sixteenth and seventeenth bytes of the Type-3
record, specifies the number of horizontal lines contained in the transmitted image.
Grayscale compression algorithm (GCA)
This mandatory one-byte binary field, which occupies the eighteenth byte of a Type-3 record, specifies
the type of grayscale compression algorithm used (if any). Zero denotes no
compression. Otherwise, this field holds a binary number
corresponding to the particular compression technique.
Image data
This binary field contains all of the low-resolution grayscale image data. Each pixel of
the uncompressed image shall be quantized to eight bits (256 gray levels) contained in a single
byte. The compression used must match the value in the GCA field of this record.
4 - Fingerprint Image Data (High-resolution grayscale)
Type-4 logical records contain high-resolution grayscale fingerprints.
Typically, there are ten rolled impressions of the individual fingers, two plain impressions
of the thumbs, and two "slaps".
The files, which can be compressed, are stored in binary.
The Type-4 record has 9 ordered, unnumbered fields, the first 8 of which contain information
about the image data stored in the 9th field. All the values are stored in binary.
This mandatory four-byte binary field, which occupies bytes one through four, contains the
total length of this record in bytes.
Image designation character (IDC)
This mandatory one-byte binary field, which occupies the fifth byte of a Type-4 record, identifies
the image data contained in this record. This IDC must match the IDC in the file content
(CNT) field of the Type-1 record.
Impression type (IMP)
This mandatory one-byte binary field, which occupies the sixth byte of a Type-4 record, contains
a code that describes how the fingerprint image information was obtained.
0 - Live-scan plain
1 - Live-scan rolled
2 - Nonlive-scan plain
3 - Nonlive-scan rolled
4 - Latent impression
5 - Latent tracing
6 - Latent photo
7 - Latent lift
Finger position (FGP)
This mandatory six-byte field occupies the seventh through twelfth byte positions of a Type-4 record.
It contains a code that corresponds to possible finger positions.
0 - Unknown
1 - Right thumb
2 - Right index finger
3 - Right middle finger
4 - Right ring finger
5 - Right little finger
6 - Left thumb
7 - Left index finger
8 - Left middle finger
9 - Left ring finger
10 - Left little finger
11 - Plain right thumb
12 - Plain left thumb
13 - Plain right four fingers
14 - Plain left four fingers
Up to five additional finger positions may be added in the remaining five bytes; any unused bytes are
filled with the binary equivalent of "255".
Image scanning resolution (ISR)
This mandatory one-byte binary field occupies the thirteenth byte of a Type-4 record. It
contains a binary value of "0" if half the minimum scanning resolution is used, and a "1" if half the
native scanning resolution is used.
Horizontal line length (HLL)
This mandatory two-byte binary field, which occupies the fourteenth and fifteenth bytes of the Type-4
record, specifies the number of pixels contained on a single horizontal line of the transmitted image.
Vertical line length (VLL)
This mandatory two-byte binary field, which occupies the sixteenth and seventeenth bytes of the Type-4
record, specifies the number of horizontal lines contained in the transmitted image.
Grayscale compression algorithm (GCA)
This mandatory one-byte binary field, which occupies the eighteenth byte of a Type-4 record, specifies
the type of grayscale compression algorithm used (if any). Zero denotes no
compression. Otherwise, this field holds a binary number
corresponding to the particular compression technique.
Image data
This binary field contains all of the high-resolution grayscale image data. Each pixel of
the uncompressed image shall be quantized to eight bits (256 gray levels) contained in a single
byte. The compression used must match the value in the GCA field of this record.
5 - Fingerprint Image Data (Low-resolution binary)
Type-5 logical records contain low-resolution binary fingerprint image
data, scanned at least at the minimum scanning resolution and then subsampled,
scaled down, or interpolated.
Typically, there are ten rolled impressions of the individual fingers, two plain impressions
of the thumbs, and two "slaps".
The Type-5 record has 9 ordered, unnumbered fields, the first 8 of which contain information about the image data stored in the 9th field. The values, which can be compressed, are stored in binary.
This mandatory four-byte binary field, which occupies bytes one through four, contains the
total length of this record in bytes.
Image designation character (IDC)
This mandatory one-byte binary field, which occupies the fifth byte of a Type-5 record, identifies
the image data contained in this record. This IDC must match the IDC in the file content
(CNT) field of the Type-1 record.
Impression type (IMP)
This mandatory one-byte binary field, which occupies the sixth byte of a Type-5 record, contains
a code that describes how the fingerprint image information was obtained.
0 - Live-scan plain
1 - Live-scan rolled
2 - Nonlive-scan plain
3 - Nonlive-scan rolled
4 - Latent impression
5 - Latent tracing
6 - Latent photo
7 - Latent lift
Finger position (FGP)
This mandatory six-byte field occupies the seventh through twelfth byte positions of a Type-5 record.
It contains a code that corresponds to possible finger positions.
0 - Unknown
1 - Right thumb
2 - Right index finger
3 - Right middle finger
4 - Right ring finger
5 - Right little finger
6 - Left thumb
7 - Left index finger
8 - Left middle finger
9 - Left ring finger
10 - Left little finger
11 - Plain right thumb
12 - Plain left thumb
13 - Plain right four fingers
14 - Plain left four fingers
Up to five additional finger positions may be added in the remaining five bytes; any unused bytes are
filled with the binary equivalent of "255".
Image scanning resolution (ISR)
This mandatory one-byte binary field occupies the thirteenth byte of a Type-5 record. It
contains a binary value of "0" if half the minimum scanning resolution is used, and a "1" if half the
native scanning resolution is used.
Horizontal line length (HLL)
This mandatory two-byte binary field, which occupies the fourteenth and fifteenth bytes of the Type-5
record, specifies the number of pixels contained on a single horizontal line of the transmitted image.
Vertical line length (VLL)
This mandatory two-byte binary field, which occupies the sixteenth and seventeenth bytes of the Type-5
record, specifies the number of horizontal lines contained in the transmitted image.
Binary compression algorithm (BCA)
This mandatory one-byte binary field, which occupies the eighteenth byte of a Type-5 record, specifies
whether or not data compression is used. A binary zero denotes no compression.
A binary one denotes the use of the ANSI/EIA-538-1988 facsimile compression standard
for the lossless compression and decompression of the image.
Image data
This field contains all of the low-resolution binary image data. Each binary pixel has
either a value of "0" (a white pixel) or a value of "1" (a black pixel). Uncompressed data is packed at eight pixels per byte. If compression is used, the pixel data is compressed with the algorithm specified in the BCA field.
6 - Fingerprint Image Data (High-resolution binary)
Type-6 logical records contain high-resolution binary fingerprints.
Typically, there are ten rolled impressions of the individual fingers, two plain impressions of the thumbs, and two "slaps".
The Type-6 record has 9 ordered, unnumbered fields, the first 8 of which contain information about the image data stored in the 9th field. The values, which can be compressed, are stored in binary.
This mandatory four-byte binary field, which occupies bytes one through four, contains the
total length of this record in bytes.
Image designation character (IDC)
This mandatory one-byte binary field, which occupies the fifth byte of a Type-6 record, identifies
the image data contained in this record. This IDC must match the IDC in the file content
(CNT) field of the Type-1 record.
Impression type (IMP)
This mandatory one-byte binary field, which occupies the sixth byte of a Type-6 record, contains
a code that describes how the fingerprint image information was obtained.
0 - Live-scan plain
1 - Live-scan rolled
2 - Nonlive-scan plain
3 - Nonlive-scan rolled
4 - Latent impression
5 - Latent tracing
6 - Latent photo
7 - Latent lift
Finger position (FGP)
This mandatory six-byte field occupies the seventh through twelfth byte positions of a Type-6 record.
It contains a code that corresponds to possible finger positions.
0 - Unknown
1 - Right thumb
2 - Right index finger
3 - Right middle finger
4 - Right ring finger
5 - Right little finger
6 - Left thumb
7 - Left index finger
8 - Left middle finger
9 - Left ring finger
10 - Left little finger
11 - Plain right thumb
12 - Plain left thumb
13 - Plain right four fingers
14 - Plain left four fingers
Up to five additional finger positions may be added in the remaining five bytes; any unused bytes are
filled with the binary equivalent of "255".
Image scanning resolution (ISR)
This mandatory one-byte binary field occupies the thirteenth byte of a Type-6 record. It
contains a binary value of "0" if half the minimum scanning resolution is used, and a "1" if half the
native scanning resolution is used.
Horizontal line length (HLL)
This mandatory two-byte binary field, which occupies the fourteenth and fifteenth bytes of the Type-6
record, specifies the number of pixels contained on a single horizontal line of the transmitted image.
Vertical line length (VLL)
This mandatory two-byte binary field, which occupies the sixteenth and seventeenth bytes of the Type-6
record, specifies the number of horizontal lines contained in the transmitted image.
Binary compression algorithm (BCA)
This mandatory one-byte binary field, which occupies the eighteenth byte of a Type-6 record, specifies
whether or not data compression is used. A binary zero denotes no compression.
A binary one denotes the use of the ANSI/EIA-538-1988 facsimile compression standard
for the lossless compression and decompression of the image.
Image data
This field contains all of the high-resolution binary image data. Each binary pixel has
either a value of "0" (a white pixel) or a value of "1" (a black pixel). Uncompressed data is packed at eight pixels per byte. If compression is used, the pixel data is compressed with the algorithm specified in the BCA field.
Type-7 logical records contain user-defined image data that is not elsewhere specified or described.
This record type handles miscellaneous images such as wrists, toes, soles, etc. It
does not store any ASCII data - use a type-16 record for data that needs to be tagged with text.
With the exception of the length and IDC fields, the format, parameters, and
types of images to be exchanged are undefined and will be agreed upon between
the sender and recipient.
This mandatory four-byte binary field, which occupies bytes one through four, contains the
total length of this record in bytes.
Image designation character (IDC)
This mandatory one-byte binary field, which occupies the fifth byte of a Type-7 record, identifies
the image data contained in this record. This IDC must match the IDC in the file content
(CNT) field of the Type-1 record.
User-defined fields
The remaining fields of the Type-7 logical record are be user-defined. Individual fields required
for a given transaction, such as field description,
size, and content must conform to the specifications
set forth by the agency to whom the transmission is being sent.
Type-8 logical records contain scanned high-resolution binary or
vectored images representing the signature
of the person being fingerprinted or of the official taking the fingerprint.
If scanned, the resolution of the image data must be at least
the minimum scanning resolution. If the resolution exceeds the bounds of the transmitting resolutions,
then the scanned image will need to be subsampled, scaled down, or interpolated. If vectored, the signature data is expressed as a series of binary numbers.
Typically, there may be up to two of these Type-8
signature records in a file - the subject, the official processing the subject, or both.
When there are one or two Type-8 logical records,
each record has 8 unnumbered, ordered fields. The first 7 fields total twelve bytes and provide information
about the image stored in the 8th field. The size of field eight is determined
from the LEN field of the record itself.
This mandatory four-byte binary field, which occupies bytes one through four, contains the
total length of this record in bytes - in this case, 12 + the size of the image data.
Image designation character (IDC)
This mandatory one-byte binary field, which occupies the fifth byte of a Type-8 record, identifies
the image data contained in this record. This IDC must match the IDC in the file content
(CNT) field of the Type-1 record.
Signature type (SIG)
This mandatory one-byte binary field occupies the sixth byte of the Type-8 record. It contains
a binary "0" if the signature belongs to the subject, or a binary "1" if that signature is that of
the official processing the transaction.
Signature representation type (SRT)
This mandatory one-byte binary field occupies the seventh byte of the Type-8 record. Its value
is a binary "0" if the image is scanned and not compressed, a binary "1" if the image is
scanned and then compressed, and the binary equivalent of "2" if the image is vector data.
Image scanning resolution (ISR)
This mandatory one-byte binary field occupies the eighth byte of a Type-8 record. It contains a binary value of "0" if half the minimum scanning resolution is used, and a "1" if half the native scanning resolution is used. A binary value of "0" is also used if the image is vector data.
Horizontal line length (HLL)
This mandatory two-byte binary field, which occupies the ninth and tenth bytes of the Type-8 record, specifies the number of pixels contained on a single horizontal line of the image if the signature data was scanned. For vectored signature data, both bytes contain the binary value of "0".
Vertical line length (VLL)
This mandatory two-byte binary field, which occupies the eleventh and twelfth bytes of the Type-8 record, specifies the number of horizontal lines contained in the transmitted image. if the signature data was scanned. For vectored signature data, both bytes contain the binary value of "0".
Signature image data
This field contains uncompressed scanned image signature data, compressed scanned image
signature data, or vectored image signature data. The entry contained in the SRT field
indicates which form of the signature data is present.
Uncompressed scanned image data - SRT field is binary "0". The data is packed at
eight pixels per byte.
Compressed scanned image data - SRT field is binary "1".
The scanned binary image data for the signature is compressed using the ANSI/EIA-538-1988 facsimile compression algorithm.
Vectored image data - SRT field is binary "2".
This field contains a list of vectors describing the pen position and pen pressure of
line segments within the signature. Each vector is five bytes.
First two bytes of each vector: the unsigned binary X-coordinate of
the pen position with the high order byte containing the most significant bits.
Positive values of X increase from left-to-right.
Next two bytes: the unsigned Y-coordinate with the high order byte
containing the most significant bits. Positive values of Y increase from bottom-to-top.
Fifth byte: an unsigned binary number between "0" and "255" representing
the pen pressure, which is constant until the next vector becomes active. A
pressure of "0" represents a "pen-up" (or no pressure) condition. "1" represents
the least recordable pressure for a particular device, while "254" represents the
maximum recordable pressure for that device. The end of the vector list is
denoted by "255".
Type-9 logical records contain geometric and topological minutiae
information encoded from a fingerprint, palm, or latent image.
Each record represents the processed
image data from which the location and orientation
descriptors of extracted minutiae characteristics
are listed. The primary use of this record type
shall be for remote searching of latent prints.
For a tenprint search transaction, there may be up to ten Type-9 records in
a file, each for a different finger. There may be up to six of these records for
palmprint searches.
The first twelve ASCII fields of the Type-9 logical record encode minutiae using a generic encoding
method detailed in the Minutia Type Information specification.
using a variety of methods, so that AFIS vendors can customize the encoding of minutiae
by reserving a block of uniquely numbered fields. All implementations must contain the first
four fields described below, but Field-5 through Field-12 are vendor-dependent and not required.
10 Facial & SMT Image Data
Type-10 records contain mugshots, photographs, and textual information about the subject.
The source of the image data can be from scanning a
photograph, an image captured with a digital camera, or a digitized "freeze-frame" from a video
camera.
A Type-10 logical record has numbered fields, the first two of which are ordered and mandatory.
The last field in the record should contain the image.
This mandatory four-byte ASCII field contains the total number of bytes in this record.
Field 10.002: Image designation character (IDC)
This mandatory one-byte ASCII field identifies the facial or SMT image data contained
in the record. This IDC must match the IDC in the file content (CNT) field of the Type-1 record.
Field 10.003: Image type (IMT)
This mandatory ASCII field indicates the type of image contained in this record.
Values are either "FACE", "SCAR", "MARK", or "TATTOO".
Field 10.004: Source agency / ORI (SRC)
This mandatory ASCII field identifies the organization that originally captured the facial
image, usually with its Originating Agency Identifier (ORI). The size of this field is
defined by the sender.
Field 10.005: Photo date (PHD)
This mandatory ASCII field holds the date when the facial or SMT image
was captured, in the format CCYYMMDD.
Field 10.006: Horizontal line length (HLL)
This mandatory ASCII field contains the number of pixels contained on a single horizontal line
of the transmitted image.
Field 10.007: Vertical line length (VLL)
This mandatory ASCII field contains the number of horizontal lines
contained in the transmitted image.
Field 10.008: Scale units (SLC)
This mandatory ASCII field specifies the units used to describe the image sampling frequency
(pixel density).
1 - pixels per inch
2 - pixels per centimeter.
0 - no scale is given, so use HPS/VPS
Field 10.009: Horizontal pixel scale (HPS)
This mandatory ASCII field specifies the integer pixel density used in the horizontal direction,
if the SLC contains a "1" or a "2". Otherwise, it indicates the horizontal component of the
pixel aspect ratio.
Field 10.010: Vertical pixel scale (VPS)
This mandatory ASCII field specifies the integer pixel density used in the vertical direction, if the
SLC contains a "1" or a "2". Otherwise, it indicates the vertical component of the pixel
aspect ratio.
Field 10.011: Compression algorithm (CGA)
This mandatory ASCII field specifies the compression algorithm
used on the mugshot. An entry of "NONE" means the image is uncompressed. The
preferred compression algorithm, baseline-JPEG, is indicated with "JPEGB".
An entry of "JPEGL" indicates the mugshot was compressed with lossless-JPEG.
If the image is captured in grayscale, then only the luminescence component will be compressed
and transmitted.
Field 10.012: Colorspace (CSP)
This mandatory ASCII field contains the color space used to exchange the image. For images compressed
using using baseline-JPEG and JFIF, the preferred color space is YCbCr8, indicated with "YCC".
All grayscale images will have a CSP of "GRAY". An entry of "RGB" means the image is an uncompressed color
image, containing non-interleaved red, green, and blue pixels (in that order). All other colorspaces are undefined.
Fields 10.013 - 10.019: Reserved for future definition (RSV)
These fields are reserved for inclusion in future
revisions of this standard. None of these fields
are to be used at this revision level. If any of
these fields are present, they are to be ignored.
Field 10.020: Subject pose (POS)
This optional field contains one ASCII character code describing the pose of the subject.
F - Full Face Frontal
R - Right Profile (90 degree)
L - Left Profile (90 degree)
A - Angled Pose. The offset angle from full frontal will be contained in field 10.021.
Field 10.021: Pose offset angle (POA)
This ASCII field - ignored unless Field 10.020 (POS) contains an "A" for "angled pose" -
specifies the pose position of the subject at any possible orientation
within a circle, to the nearest degree. The offset angle is measured from the fullface
pose position with a range of values from -180 degrees to +180 degrees. A positive
angle expresses the angular offset as the subject rotates from a full-face pose to their right
(approaching a left profile). A negative angle expresses the angular offset as the subject
rotates from a full-face pose to their left (approaching a right profile).
Field 10.022: Photo description (PXS)
This optional ASCII field describes special attributes of the captured facial image.
"GLASSES" - Subject Wearing Glasses
"HAT" - Subject Wearing Hat
"SCARF" - Subject Wearing Scarf
"PHYSICAL" - Physical Characteristics. This field has one or more subfields, such as "FRECKLES".
Reference the NCIC Code Manual, Part 4 Section 13 for more physical characteristic subfields.
"OTHER" - Other Characteristics of the facial image not specified by the NCIC are entered
in subfields within "OTHER".
Fields 10.023 - 10.039: Reserved for future definition (RSV)
These fields are reserved for inclusion in future
revisions of this standard. None of these fields
are to be used at this revision level. If any of
these fields are present, they are to be ignored.
Field 10.040: NCIC designation code (SMT)
This field, which is mandatory if the record contains a SMT image, identifies the
general location of the captured scar, mark, or tattoo image. The location code is found in
Part 4 Section 13 of the NCIC Code Manual.
If the scar, mark, or tattoo is larger than a single NCIC body part code, than the primary
location code is listed first, followed by the other location codes. Each location code is
separated by the “RS” separator character. For "marks", the most common locations for needle track marks
are listed in the NCIC manual; if the location isn't common then use the body location codes
listed for scars.
SMT size (SMS)
This optional field contains the dimensions of the scar, mark or tattoo (to the nearest centimeter)
in the order: height, “US” separator character, width.
SMT descriptors (SMD)
This optional field contains one or more subfields which provide progressively detailed information
describing the total image or a portion of the image.
First, the image is identified as being a scar, a mark, or a tattoo.
“SCAR” - healed scar tissue from an accident or medical procedure.
Subfield 2 - "OTHER"
Subfield 3 - "MISC"
Subfield 4 - a textual description or other information concerning the scar.
“MARK” - the pattern resulting from needle or "track" marks.
Subfield 2 - "OTHER"
Subfield 3 - "MISC"
Subfield 4 - a textual description or other information concerning the marks.
"TATTOO" (for common tattoos resulting from the pricking of the skin with a coloring matter),
"CHEMICAL" (if the image was burned in with chemicals),
"BRANDED" (if the image was burned into the skin with a branding iron or other form of heat), or
“CUT” (if the image was caused by incision of the skin).
Subfield 2 - the general class code of tattoo
Human Forms and Features
HUMAN
Animals and Animal Features
ANIMAL
Plants
PLANT
Flags
FLAG
Objects
OBJECT
Abstractions
ABSTRACT
Insignias & Symbols
SYMBOL
Other Images
OTHER
Subfield 3 - the subclass code within the general class. As an example, the plant subclasses are listed below.
Narcotics
NARCOTICS
Red Flowers
REDFL
Blue Flowers
BLUEFL
Yellow Flowers
YELFL
Drawings of Flowers
DRAW
Rose
ROSE
Tulip
TULIP
Lily
LILY
Miscellaneous Plants,Flowers, Vegetables
MPLANT
Subfield 4 - a textual description or other information concerning the tattoo.
A tattoo with multiple features can be described in multiple subfields, separated by the “RS” separator.
The first subfield describes the most predominant feature of the tattoo, followed by subfields describing
other features of the tattoo. For example, a tattoo consisting of a
man with a snake on the arm being followed by a dog may contain three subfields - one describing the man, a
second describing the snake, and a third describing the dog.
Field 10.043: Color (COL)
For each subfield in Field 10.042, this optional field has a subfield that lists the color(s) of the tattoo.
The first item in the subfield is the predominant color of the tattoo, followed by any additional colors.
Items in the subfield are separated by the "US" separator character.
Fields 10.044 - 10.199: Reserved for future definition (RSV)
These fields are reserved for inclusion in future
revisions of this standard. None of these fields
are to be used at this revision level. If any of
these fields are present, they are to be ignored.
Fields 10.200 - 10.998: User-defined fields (UDF)
These fields are user-definable fields. Their size
and content are defined by the user and be in
accordance with the receiving agency. If present
they contain ASCII textual information.
Field 10.999: Image data (DAT)
This field contains all of the grayscale or color data from a face, scar, mark, tattoo, or other image.
It is always in field number 999, since it must be the last physical field in the record.
Each pixel of uncompressed grayscale data is quantized to eight bits (256 gray levels) and
occupies a single byte. The uncompressed color image is expressed as 24 bit RGB pixels. Three
bytes each hold one color component of the pixel in the order: Red, Green, Blue. If compression is used,
the pixel data is compressed with the algorithm specified in the GCA field.
Type-13 tagged-field image records contain variable-resolution latent
fingerprint and palmprint image data together
with fixed and user-defined textual
information.
It is strongly recommended that the
minimum scanning resolution (or effective scanning
resolution) and transmission rate for latent
images be 39.38 ppmm plus or minus 0.40 ppmm
(1000 ppi plus or minus 10 ppi). However, in all
cases the scanning resolution used to capture a
latent image shall be at least as great as the
minimum scanning resolution of 19.69 ppmm (500
ppi).
The variable-resolution latent image data contained
in the Type-13 logical record must be uncompressed
or may be the output from a lossless
compression algorithm. There is no limit on the
number of these latent records that may be present
in a transaction.
Type-14 tagged-field image records contain variable-resolution tenprint
fingerprint image data together with fixed and user-defined textual information fields.
Fingerprint
images can be either rolled or plain impressions.
The scanning resolution is not specified for this
record type. While the Type-14 record may be
used for the exchange of 19.69 ppmm (500 ppi)
images, it is strongly recommended that the
minimum scanning resolution (or effective scanning
resolution) for tenprint images be 39.38
ppmm plus or minus 0.40 ppmm (1000 ppi plus or
minus 10 ppi). It should be noted that as the
resolution is increased, more detailed ridge and
structure information becomes available in the
image. However, in all cases the scanning resolution
used to capture a tenprint image shall be at
least as great as the minimum scanning resolution
of 19.69 ppmm (500ppi).
The variable-resolution tenprint image data contained
in the Type-14 logical record may be in a
compressed form. Typically, there may be up to
14 of these Type-14 records in a file; ten rolled
impressions of the individual fingers, two plain
impressions of the thumbs and two plain impressions
of the four simultaneously obtained remaining
fingers of each hand.
15 - Palmprint Image Data (Variable-resolution)
Type-15 tagged-field image records contain variable-resolution
palmprint image data together with fixed and
user-defined textual information fields.
Image data contained
in this record may be the full palm impression,
the upper half of the palm, the lower half of
the palm, or the writer's palmprint impression.
The scanning resolution is not specified for this
record type. While the Type-15 record may be
used for the exchange of 19.69 ppmm (500 ppi)
images, it is strongly recommended that the
minimum scanning resolution (or effective scanning
resolution) for palmprint images be 39.38
ppmm plus or minus 0.40 ppmm (1000 ppi plus or
minus 10 ppi). It should be noted that as the
resolution is increased, more detailed ridge and
structure information becomes available in the
image. However, in all cases the scanning resolution
used to capture a tenprint image shall be at
least as great as the minimum scanning resolution
of 19.69 ppmm (500ppi).
The variable-resolution palmprint image data
contained in the Type-15 logical record may be in
a compressed form. Typically, there may be up to
6 of these Type-15 records in a file; two full
palmprints or four partial palms, and two writer?s
palms.
16 - User-defined Testing Image Data (Variable-resolution)
The Type-16 record, a tagged-field version of the Type-7 record,
contains miscellaneous images not elsewhere specified or described, together with textual information fields. It is designed for development and testing.
The scanning resolution is not specified for this
record type but must be at least as great as the
minimum scanning resolution (19.69 ppmm, or 500ppi). Increases in the resolution used
for capturing images should follow the recommended
migration path to 39.38 ppmm (1000
ppi), 78.76 ppmm (2000 ppi), etc. It should be
noted that as the resolution is increased, more
detailed ridge and structure information becomes
available in the image.
The variable-resolution image data contained in
the Type-16 logical record may be in a compressed
form.
With the exception of the first two tagged fields and the descriptors for the image
data, the remaining details of the Type-16 record are undefined by this standard and will be
agreed upon between the sender and recipient.