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 ...
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION8.15.11 Field 15.011: Compression algorithm / CGAThis field is mandatory if an image is present in Field 15.999. Otherwise it is absent. Itshall specify the algorithm used to compress the transmitted grayscale images. See Table15 for a list of the codes, and Section 7.7.9.1.8.15.12 Field 15.012: Bits per pixel / BPXThis field is mandatory if an image is present in Field 15.999. Otherwise it is absent.See Section 7.7.8.6 for details.8.15.13 Field 15.013: Friction ridge generalized position / FGPThis mandatory field shall contain the palm print position that matches the palmprintimage. Valid codes range from 20 to 38, or 81 to 84. See Table 8. See Section 7.7.4.2for details.8.15.14 Field 15.016: Scanned horizontal pixel scale / SHPSThis is an optional field. See Section 7.7.8.7 for details.8.15.15 Field 15.017: Scanned vertical pixel scale / SVPSThis is an optional field. See Section 7.7.8.8 for details.8.15.16 Field 15.018: Amputated or bandaged / AMPThis optional field shall specify if a hand is amputated or bandaged. Multiple subfieldsmay be entered and each shall contain two information items.• The first item is the friction ridge amputated or bandaged position / FRAPbetween 21 and 38 or 81 through 84 as chosen from Table 8. This informationitem is called the friction ridge amputated or bandaged position / FRAP todifferentiate it from FGP.• The second item is the amputated or bandaged code / ABC, also known as theAMPCD. Table 85 is a list of allowable indicators for the AMPCD.If an entire hand is missing, either 83 (right full palm, including writer's palm) or 84 (leftfull palm, including writer's palm) shall be entered for FRAP. A partially scarred palmshould be printed. XX shall be used only when a partial print exists due to amputation;therefore it contains some friction ridge detail. UP shall be used with the complete blockwhere an image was to be transmitted, but there is no image due to amputation or totallack of friction ridge detail (such as with a bandage). An image with a scar should not bemarked XX or UP.8.15.17 Field 15.020: Comment / COMThis is an optional field. See Section 7.4.4 for details.May, 2013 DRAFT VERSION UPDATE 2013 Page 333
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION8.15.18 Field 15.024: Palm quality metric / PQMThis optional field is used to specify one or more different metrics of the print imagequality score data for the image stored in this record. Each subfield is comprised of fourinformation items. The first information shall be the friction ridge metric position /FRMP for the image stored in this record. Valid codes range from 20 to 38, 81, 82, 83 or84. See Table 8. See Section 7.7.7 for a description of the remaining three informationitems.8.15.19 Field 15.030: Device monitoring mode / DMMThis is an optional field. See Section 7.7.1.3 for details.[2013n>]8.15.20 Field 15.046: Subject / SUBThis field is optional. This field is particularly useful if the image is obtained from adeceased person. However, its use is not limited to such circumstances. SUB iscomprised of the following information items:• The first information item is mandatory if this field is present. It is subjectstatus code / SSC. Possible entries are:0 = Status of individual unknown1 = Data obtained from a living person – such as a victim orpersons unable to identify themselves2 = Data obtained from a decedent – such as an unknowndeceased• The second information item shall be entered if SSC is 2. It is subject bodystatus code / SBSC. Its purpose is to indicate whether the informationrelates to an entire corpse or a separate body part. The numeric value isselected from the descriptors below:1 = Whole2 = Fragment• The third information item shall be entered if SSC is 2. It is subject bodyclass code/ SBCC. The numeric value is selected from the descriptorsbelow:1 = Natural Tissue2 = Decomposed3 = Skeletal8.15.21 Field 15.047: Capture organization name / CONThis field is optional. Note that this can be different from the agency entered in Field334
- Page 324 and 325: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 326 and 327: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 328 and 329: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 330 and 331: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 332 and 333: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 334 and 335: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 336 and 337: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 338 and 339: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 340 and 341: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 342 and 343: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 344 and 345: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 346 and 347: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 348 and 349: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 350 and 351: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 352 and 353: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 354 and 355: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 356 and 357: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 358 and 359: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 360 and 361: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 362 and 363: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 364 and 365: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 366 and 367: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 368 and 369: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 370 and 371: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 372 and 373: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 376 and 377: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 378 and 379: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 380 and 381: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 382 and 383: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 384 and 385: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 386 and 387: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 388 and 389: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 390 and 391: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 392 and 393: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 394 and 395: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 396 and 397: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 398 and 399: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 400 and 401: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 402 and 403: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 404 and 405: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 406 and 407: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 408 and 409: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 410 and 411: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 412 and 413: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 414 and 415: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 416 and 417: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 418 and 419: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 420 and 421: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 422 and 423: ANSI/NIST-ITL 1-2011 - UPDATE 2013
ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION8.15.18 Field 15.024: Palm quality metric / PQMThis optional field is used to specify one or more different metrics of the print imagequality score data <strong>for</strong> the image stored in this record. Each subfield is comprised of fourin<strong>for</strong>mation items. The first in<strong>for</strong>mation shall be the friction ridge metric position /FRMP <strong>for</strong> the image stored in this record. Valid codes range from 20 to 38, 81, 82, 83 or84. See Table 8. See Section 7.7.7 <strong>for</strong> a description of the remaining three in<strong>for</strong>mationitems.8.15.19 Field 15.030: Device monitoring mode / DMMThis is an optional field. See Section 7.7.1.3 <strong>for</strong> details.[2013n>]8.15.20 Field 15.046: Subject / SUBThis field is optional. This field is particularly useful if the image is obtained from adeceased person. However, its use is not limited to such circumstances. SUB iscomprised of the following in<strong>for</strong>mation items:• The first in<strong>for</strong>mation item is mandatory if this field is present. It is subjectstatus code / SSC. Possible entries are:0 = Status of individual unknown1 = Data obtained from a living person – such as a victim orpersons unable to identify themselves2 = Data obtained from a decedent – such as an unknowndeceased• The second in<strong>for</strong>mation item shall be entered if SSC is 2. It is subject bodystatus code / SBSC. Its purpose is to indicate whether the in<strong>for</strong>mationrelates to an entire corpse or a separate body part. The numeric value isselected from the descriptors below:1 = Whole2 = Fragment• The third in<strong>for</strong>mation item shall be entered if SSC is 2. It is subject bodyclass code/ SBCC. The numeric value is selected from the descriptorsbelow:1 = Natural Tissue2 = Decomposed3 = Skeletal8.15.21 Field 15.047: Capture organization name / CONThis field is optional. Note that this can be different from the agency entered in Field334