5 Images shall either be uncompressed or compressed using an implementation of the Wavelet Scalar Quantization
All changes in this version
Title
Images shall either be uncompressed or compressed using an implementation of the Wavelet Scalar Quantization
Control
(WSQ) algorithm that has been certified by the FBI. The FBI's current requirement for a 15:1 nominal compression ratio shall apply. 6. Compression should only be applied after the records required by sections 3.4 and 3.6 have been prepared and transformed NFIQ values have been assigned. 7. The term view refers to the number of images of that particular finger. This value would exceed one if imaging has been repeated. Inclusion of more than one image of a finger can afford some benefit in a matching process. This document recommends that any additionally available images (say, from a PIV Card re-issuance procedure) with quality value 1 to 3 should be included in the record. In all cases the images shall be stored in order of capture date, with newest first. 8. Quality values shall be present. These shall be calculated from the NIST Fingerprint Image Quality (NFIQ) method described in [NFIQ] using the formula Q = 20*(6 - NFIQ). This scale reversal ensures that high quality values connote high predicted performance and consistency with the dictionary definition. The values are intended to be predictive of the relative performance of a minutia based fingerprint matching system. It is recommended that a user should be prompted to first attempt authentication using the finger with the highest quality, regardless of whether this is the primary or secondary finger. 9. The quality value shall be set to 254 (the [FINGSTD] code for undefined) if this record is not a single finger print (i.e., it is a multi-finger image, or a palm print) or if the NFIQ implementation fails. 10. There is no restriction on the image size. However non-background pixels of the target finger shall be retained (i.e. cropping of the image data is prohibited). 11. [FINGSTD, Table 4] refers to a single-byte field labeled "reserved", but there is no corresponding clause to formally define it. The M1 committee has undertaken to resolve this by inserting a new subclause to require inclusion of the "Reserved" field. This will appear in a revision of [FINGSTD]. In any case, PIV implementations must include the single byte field, setting the value to 0.