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 VERSIONFieldNumberMnemonicContentDescriptionCondcodeCharacterTypeMIn#Max#ValueConstraintsOccurrenceMIn#Max#12.997RESERVED FORFUTURE USE only byANSI/NIST-ITLNot to be usedGEOGEOGRAPHICSAMPLEACQUISITIONLOCATIONO 0 1UTE universal time entry O↑encoding specific: encoding specific:See Section 7.7.2.2 See Section 7.7.2.2and Annex C: and Annex C:NIEM-conformant NIEM-conformantencoding rules encoding rules0 1LTD latitude degree value D NS 1 9 -90 < LTD < 90 0 1LTM latitude minute value D NS 1 8 0 < LTM < 60 0 1LTS latitude second value D NS 1 8 0 < LTS < 60 0 1LGD longitude degree value D NS 1 10 -180 < LGD < 180 0 1LGM longitude minute value D NS 1 8 0 < LGM < 60 0 1LGS longitude second value D NS 1 8 0 < LGS < 60 0 112.998ELE elevation O NS 1 8-422.000 < ELE
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION8.12.1 Field 12.001: Record headerThe content of this mandatory field is dependent upon the encoding used. See therelevant annex of this standard for details. See Section 7.1 Record header.8.12.2 Field 12.002: Information designation character / IDCThis mandatory field shall contain the IDC assigned to this Type-12 record as listed inthe information item IDC for this record in Field 1.003 Transaction content / CNT .See Section 7.3.1 Information designation character / IDC.8.12.3 Field 12.003: Forensic dental setting / FDSThis optional field is used to describe the forensic setting that carried out theanalysis of the dental and oral data to identify or confirm the identity of thesubject. This field is not used when data is gathered and transmitted withoutforensic analysis. The field is comprised of the following information items:• The first information item is the forensic analyst category code /FACC. It is mandatory if this field is used. It contains a single letterdescribing the head of the team that processed the forensic data:MDATOMedical ExaminerDental Professional / Forensic OdontologistForensic AnthropologistTechnicianOther• The second information item is the forensic organization primarycontact information/ FOPC for the forensic analysis. This is anoptional item. It should include the name, telephone number, and e-mail address of the person responsible for the analysis.• The third information item is optional. It is the forensic sourcecountry code / FSCC. This is the code of the location where theforensic analysis was performed, not the code of the location fromwhich the forensic data or sample were sent for analysis. FSCCdefaults to ISO-3166-1 coding. If Field 1.018 Geographic name set /GNS is set to 1, then FSCC is from the GENC list.8.12.4 Field 12.004: Source agency identification ID / SRCThis is a mandatory field. See Section 7.6 for details. The SRC is a code for aparticular agency that is assigned by the implementation domain (such as276
- Page 266 and 267: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 268 and 269: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 270 and 271: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 272 and 273: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 274 and 275: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 276 and 277: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 278 and 279: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 280 and 281: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 282 and 283: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 284 and 285: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 286 and 287: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 288 and 289: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 290 and 291: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 292 and 293: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 294 and 295: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 296 and 297: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 298 and 299: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 300 and 301: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 302 and 303: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 304 and 305: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 306 and 307: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 308 and 309: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 310 and 311: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 312 and 313: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 314 and 315: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 318 and 319: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 320 and 321: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 322 and 323: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- 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
ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION8.12.1 Field 12.001: Record headerThe content of this mandatory field is dependent upon the encoding used. See therelevant annex of this standard <strong>for</strong> details. See Section 7.1 Record header.8.12.2 Field 12.002: In<strong>for</strong>mation designation character / IDCThis mandatory field shall contain the IDC assigned to this Type-12 record as listed inthe in<strong>for</strong>mation item IDC <strong>for</strong> this record in Field 1.003 Transaction content / CNT .See Section 7.3.1 In<strong>for</strong>mation designation character / IDC.8.12.3 Field 12.003: Forensic dental setting / FDSThis optional field is used to describe the <strong>for</strong>ensic setting that carried out theanalysis of the dental and oral data to identify or confirm the identity of thesubject. This field is not used when data is gathered and transmitted without<strong>for</strong>ensic analysis. The field is comprised of the following in<strong>for</strong>mation items:• The first in<strong>for</strong>mation item is the <strong>for</strong>ensic analyst category code /FACC. It is mandatory if this field is used. It contains a single letterdescribing the head of the team that processed the <strong>for</strong>ensic data:MDATOMedical ExaminerDental Professional / Forensic OdontologistForensic AnthropologistTechnicianOther• The second in<strong>for</strong>mation item is the <strong>for</strong>ensic organization primarycontact in<strong>for</strong>mation/ FOPC <strong>for</strong> the <strong>for</strong>ensic analysis. This is anoptional item. It should include the name, telephone number, and e-mail address of the person responsible <strong>for</strong> the analysis.• The third in<strong>for</strong>mation item is optional. It is the <strong>for</strong>ensic sourcecountry code / FSCC. This is the code of the location where the<strong>for</strong>ensic analysis was per<strong>for</strong>med, not the code of the location fromwhich the <strong>for</strong>ensic data or sample were sent <strong>for</strong> analysis. FSCCdefaults to ISO-3166-1 coding. If Field 1.018 Geographic name set /GNS is set to 1, then FSCC is from the GENC list.8.12.4 Field 12.004: Source agency identification ID / SRCThis is a mandatory field. See Section 7.6 <strong>for</strong> details. The SRC is a code <strong>for</strong> aparticular agency that is assigned by the implementation domain (such as276