11.07.2015 Views

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION8.9.5.8 Field 9.133: M1 finger view / FVWThis mandatory field contains the view number of the finger associated with this record’sdata. The view number begins with “0” and increments by one to “15”. Finger viewdifferentiates multiple images of the same finger that are included in the transaction to betaken consecutively to develop an "average" template <strong>for</strong> that particular set of finger minutiae<strong>for</strong> enrollment applications.8.9.5.9 Field 9.134: M1 friction ridge generalized position / FGPThis is a mandatory field. See Section 7.7.4.2 <strong>for</strong> details . Valid codes <strong>for</strong> this field arebetween 1 and 10, taken from Table 8 to indicate the finger position. (Note that codes 16and 17 are not covered in INCITS 378). The 2007 version restricted this to fingerprint codes.The 2008 version also allowed palm codes, but this version of the ANSI/<strong>NIST</strong>-ITL standarddoes not in order to maintain consistency with INCITS 378.8.9.5.10 Field 9.135: M1 friction ridge quality data / FQDThis mandatory field shall contain the quality of the overall finger minutiae data. There maybe a subfield <strong>for</strong> each algorithm and predictive per<strong>for</strong>mance measure. Each subfield shallcontain the first in<strong>for</strong>mation item (quality value / QVU) described in Section 7.7.7. Thesecond two in<strong>for</strong>mation items are optional <strong>for</strong> this field. (algorithm vendor identification /QAV and algorithm product identification / QAP).The 2004 version of INCITS 378 had only 1 byte <strong>for</strong> quality with no second and thirdin<strong>for</strong>mation items. The 2009 version of INCITS 378 had all three in<strong>for</strong>mation items and allthree are mandatory in that standard. The 2007 and 2008 versions of ANSI/<strong>NIST</strong>-ITLmandated the presence of all three in<strong>for</strong>mation items. However, this version of ANSI/<strong>NIST</strong>-ITL allows the second and third items to be optional, in order to accommodate those usersfollowing the 2004 version of INCITS 378.8.9.5.11 Field 9.136: M1 number of minutiae / NOMThis mandatory field shall contain a count of the number of minutiae recorded in this block.8.9.5.12 Field 9.137: M1 finger minutiae data / FMDThe total number of subfields shall agree with the count found in Field 9.136: M1 numberof minutiae / NOM. Each subfield has six in<strong>for</strong>mation items.• The first in<strong>for</strong>mation item (minutia index number / MAN), shall be initialized to“1” and incremented by “1” <strong>for</strong> each additional minutia in the fingerprint.• The second in<strong>for</strong>mation item (‘x’ coordinate / MXC) is expressed in pixel units.• The third in<strong>for</strong>mation item (‘y’ coordinate / MYC) is expressed in pixel units.• The fourth in<strong>for</strong>mation item (minutia angle / MAV) is recorded in units of twodegrees. This value shall be nonnegative between 0 and 179, inclusive.• The fifth in<strong>for</strong>mation (minutia type / M1M) has a value of “0” to represent aMay, 2013 DRAFT VERSION UPDATE 2013 Page 139

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!