Publication: Magyar Közlöny
Issue: MK-2007-147 (Year: 2007, Number: 147)
Era: 2004-2010
Section: 
Paragraph Index: 25

2. If a minutia cannot be clearly categorized as one of the above two types, it shall be designated as “other”, Type 0. Table 5: Minutia types Type Description Other Ridge ending Bifurcation 2007/147/II. szám 6.1.2 Minutia placement and type For templates to be compliant with Section 5 of the ANSI INCITS 378-2004 standard, the following method, which enhances the current INCITS 378-2004 standard, shall be used for determining placement (location and angular direction) of individual minutiae. The position or location of a minutia representing a ridge ending shall be the point of forking of the medial skeleton of the valley area immediately in front of the ridge ending. If the three legs of the valley area were thinned down to a single-pixel-wide skeleton, the point of the intersection is the location of the minutia. Similarly, the location of the minutia for a bifurcation shall be the point of forking of the medial skeleton of the ridge. If the three legs of the ridge were each thinned down to a single-pixel-wide skeleton, the point where the three legs intersect is the location of the minutia. After all ridge endings have been converted to bifurcations, all of the minutiae of the dactyloscopic image are represented as bifurcations. The X and Y pixel coordinates of the intersection of the three legs of each minutia can be directly formatted. Determination of the minutia direction can be extracted from each skeleton bifurcation. The three legs of every skeleton bifurcation must be examined and the endpoint of each leg determined. Figure 6.1.2 illustrates the three methods used for determining the end of a leg that is based on a scanning resolution of 500 ppi. The ending is established according to the event that occurs first. The pixel count is based on a scan resolution of 500 ppi. Different scan resolutions would imply different pixel counts. • A distance of .064" (the 32nd pixel) • The end of skeleton leg that occurs between a distance of .02" and .064" (the 10th through the 32nd pixels); shorter legs are not used • A second bifurcation is encountered within a distance of .064" (before the 32nd pixel) Figure 6.1.2 The angle of the minutiae is determined by constructing three virtual rays originating at the bifurcation point and extending to the end of each leg. The smallest of the three angles formed by the rays is bisected to indicate the minutiae direction. 2007/147/II. szám 6.1.3 Coordinate system The coordinate system used to express the minutiae of a fingerprint shall be a Cartesian coordinate system. Minutiae locations shall be represented by their x and y coordinates. The origin of the coordinate system shall be the upper left corner of the original image with x increasing to the right and y increasing downward. Both x and y coordinates of a minutiae shall be represented in pixel units from the origin. It should be noted that the location of the origin and units of measure is not in agreement with the convention used in the definitions of the Type 9 in the ANSI/NIST-ITL 1-2000. 6.1.4 Minutiæ direction Angles are expressed in standard mathematical format, with zero degrees to the right and angles increasing in the counter clockwise direction. Recorded angles are in the direction pointing back along the ridge for a ridge ending and toward the centre of the valley for a bifurcation. This convention is 180 degrees opposite of the angle convention described in the definitions of the Type 9 in the ANSI/NIST- ITL 1-2000. 6.2 Fields for Type-9 Logical record INCITS-378 Format All fields of the Type-9 records shall be recorded as ASCII text. No binary fields are permissible in this tagged-field record. 6.2.1 Field 9.001: Logical record length (LEN) This mandatory ASCII field shall contain the length of the logical record specifying the total number of bytes, including every character of every field contained in the record. 6.2.2 Field 9.002: Image designation character (IDC) This mandatory two-byte field shall be used for the identification and location of the minutiæ data. The IDC contained in this field shall match the IDC found in the file content field of the Type-1 record. 6.2.3 Field 9.003: Impression type (IMP) This mandatory one-byte field shall describe the manner by which the dactyloscopic image information was obtained. The ASCII value of the proper code as selected from Table 3.1 shall be entered in this field to signify the impression type. 6.2.4 Field 9.004: Minutiæ format (FMT) This field shall contain a "U" to indicate that the minutiae are formatted in M1-378 terms. Even though information may be encoded in accordance with the M1-378 standard, all data fields of the Type-9 record must remain as ASCII text fields. 2007/147/II. szám 6.2.5 Field 9.126: CBEFF information This field shall contain three information items. The first information item shall contain the value "27" (0x1B). This is the identification of the CBEFF Format Owner assigned by the International Biometric Industry Association (IBIA) to INCITS Technical Committee M1. The <US> character shall delimit this item from the CBEFF Format Type that is assigned a value of "513" (0x0201) to indicate that this record contains only location and angular direction data without any Extended Data Block information. The <US> character shall delimit this item from the CBEFF Product Identifier (PID) that identifies the "owner" of the encoding equipment. The vendor establishes this value. It can be obtained from the IBIA website (www.ibia.org) if it is posted. 6.2.6 Field 9.127: Capture equipment identification This field shall contain two information items separated by the <US> character. The first shall contain "APPF" if the equipment used originally to acquire the image was certified to comply with Appendix F (IAFIS Image Quality Specification, January 29, 1999) of CJIS-RS-0010, the Federal Bureau of Investigation's Electronic Fingerprint Transmission Specification. If the equipment did not comply it will contain the value of "NONE". The second information item shall contain the Capture Equipment ID which is a vendor-assigned product number of the capture equipment. A value of "0" indicates that the capture equipment ID is unreported. 6.2.7 Field 9.128: Horizontal line length (HLL) This mandatory ASCII field shall contain the number of pixels contained on a single horizontal line of the transmitted image. The maximum horizontal size is limited to 65,534 pixels. 6.2.8 Field 9.129: Vertical line length (VLL) This mandatory ASCII field shall contain the number of horizontal lines contained in the transmitted image. The maximum vertical size is limited to 65,534 pixels. 6.2.9 Field 9.130: Scale units (SLC) This mandatory ASCII field shall specify the units used to describe the image sampling frequency (pixel density). A "1" in this field indicates pixels per inch, or a "2" indicates pixels per centimetre. A "0" in this field indicates no scale is given. For this case, the quotient of HPS/VPS gives the pixel aspect ratio. 6.2.10 Field 9.131: Horizontal pixel scale (HPS) This mandatory ASCII field shall specify the integer pixel density used in the horizontal direction providing the SLC contains a "1" or a "2". Otherwise, it indicates the horizontal component of the pixel aspect ratio. 2007/147/II. szám 6.2.11 Field 9.132: Vertical pixel scale (VPS) This mandatory ASCII field shall specify the integer pixel density used in the vertical direction providing the SLC contains a "1" or a "2". Otherwise, it indicates the vertical component of the pixel aspect ratio. 6.2.12 Field 9.133: Finger view This mandatory field contains the view number of the finger associated with this record's data. The view number begins with "0" and increments by one to "15". 6.2.13 Field 9.134: Finger position (FGP) This field shall contain the code designating the finger position that produced the information in this Type-9 record. A code between 1 and 10 taken from table 3.2 or the appropriate palm code from table 6.3 shall be used to indicate the finger or palm position. 6.2.14 Field 9.135: Finger quality The field shall contain the quality of the overall finger minutiæ data and shall be between 0 and 100. This number is an overall expression of the quality of the finger record, and represents quality of the original image, of the minutia extraction and any additional operations that may affect the minutiæ record. 6.2.15 Field 9.136: number of minutiæ The mandatory field shall contain a count of the number of minutiæ recorded in this logical record. 6.2.16 Field 9.137: Finger minutiæ data This mandatory field has six information items separated by the <US> character. It consists of several subfields, each containing the details of single minutiae. The total number of minutiae subfields must agree with the count found in field 136. The first information item is the minutiae index number, which shall be initialized to "1" and incremented by "1" for each additional minutia in the fingerprint. The second and third information items are the 'x' coordinate and 'y' coordinates of the minutiae in pixel units. The fourth information item is the minutiae angle recorded in units of two degrees. This value shall be nonnegative between 0 and 179. The fifth information item is the minutiae type. A value of "0" is used to represent minutiae of type "OTHER", a value of "1" for a ridge ending and a value of "2" for a ridge bifurcation. The sixth information item represents the quality of each minutiae. This value shall range from 1 as a minimum to 100 as a maximum. A value of "0" indicates that no quality value is available. Each subfield shall be separated from the next with the use of the <RS> separator character. 6.2.17 Field 9.138: Ridge count information This field consists of a series of subfields each containing three information items. The first information item of the first subfield shall indicate the ridge count extraction method. A "0" indicates that no assumption shall be made about the method used to extract ridge counts, nor their order in the 2007/147/II. szám record. A "1" indicates that for each centre minutiae, ridge count data was extracted to the nearest neighbouring minutiae in four quadrants, and ridge counts for each centre minutia are listed together. A "2" indicates that for each centre minutiae, ridge count data was extracted to the nearest neighbouring minutiae in eight octants, and ridge counts for each centre minutia are listed together. The remaining two information items of the first subfield shall both contain "0". Information items shall be separated by the <US> separator character. Subsequent subfields will contain the centre minutiae index number as the first information item, the neighbouring minutiae index number as the second information item, and the number of ridges crossed as the third information item. Subfields shall be separated by the <RS> separator character. 6.2.18 Field 9.139: Core information This field will consist of one subfield for each core present in the original image. Each subfield consists of three information items. The first two items contain the 'x' and 'y' coordinate positions in pixel units. The third information item contains the angle of the core recorded in units of 2 degrees. The value shall be a nonnegative value between 0 and 179. Multiple cores will be separated by the <RS> separator character. 6.2.19 Field 9.140: Delta information This field will consist of one subfield for each delta present in the original image. Each subfield consists of three information items. The first two items contain the 'x' and 'y' coordinate positions in pixel units. The third information item contains the angle of the delta recorded in units of 2 degrees. The value shall be a nonnegative value between 0 and 179. Multiple cores will be separated by the <RS> separator character. 7. Type-13 variable-resolution latent image record The Type-13 tagged-field logical record shall contain image data acquired from latent images. These images are intended to be transmitted to agencies that will automatically extract or provide human intervention and processing to extract the desired feature information from the images. Information regarding the scanning resolution used, the image size, and other parameters required to process the image, are recorded as tagged-fields within the record. Table 7: Type-13 variable-resolution latent record layout Field size per occurrence Occur count Ident Cond. code Field Number Field Name Char type min. max. min. max. Max byte count LEN M 13.001 LOGICAL RECORD LENGTH N IDC M 13.002 IMAGE DESIGNATION CHARACTER N IMP M 13.003 IMPRESSION TYPE A SRC M 13.004 SOURCE AGENCY / ORI AN LCD M 13.005 LATENT CAPTURE DATE N 2007/147/II. szám Field size per occurrence Occur count Ident Cond. code Field Number Field Name Char type min. max. min. max. Max byte count HLL M 13.006 HORIZONTAL LINE LENGTH N VLL M 13.007 VERTICAL LINE LENGTH N SLC M 13.008 SCALE UNITS N HPS M 13.009 HORIZONTAL PIXEL SCALE N VPS M 13.010 VERTICAL PIXEL SCALE N CGA M 13.011 COMPRESSION ALGORITHM A BPX M 13.012 BITS PER PIXEL N FGP M 13.013 FINGER POSITION N RSV 13.014 13.019 RESERVED FOR FUTURE DEFINITION -- -- -- -- -- -- COM O 13.020 COMMENT A RSV 13.021 13.199 RESERVED FOR FUTURE DEFINITION -- -- -- -- -- -- UDF O 13.200 13.998 USER-DEFINED FIELDS -- -- -- -- -- -- DAT M 13.999 IMAGE DATA B -- -- Key for character type: N = Numeric; A = Alphabetic; AN = Alphanumeric; B = Binary 7.1 Fields for the Type-13 logical record The following paragraphs describe the data contained in each of the fields for the Type-13 logical record. Within a Type-13 logical record, entries shall be provided in numbered fields. It is required that the first two fields of the record are ordered, and the field containing the image data shall be the last physical field in the record. For each field of the Type-13 record, table 5.1 lists the “condition code” as being mandatory “M” or optional “O”, the field number, the field name, character type, field size, and occurrence limits. Based on a three digit field number, the maximum byte count size for the field is given in the last column. As more digits are used for the field number, the maximum byte count will also increase. The two entries in the “field size per occurrence” include all character separators used in the field. The “maximum byte count” includes the field number, the information, and all the character separators including the “GS” character. 2007/147/II. szám 7.1.1 Field 13.001: Logical record length (LEN) This mandatory ASCII field shall contain the total count of the number of bytes in the Type-13 logical record. Field 13.001 shall specify the length of the record including every character of every field contained in the record and the information separators. 7.1.2 Field 13.002: Image designation character (IDC) This mandatory ASCII field shall be used to identify the latent image data contained in the record. This IDC shall match the IDC found in the file content (CNT) field of the Type-1 record. 7.1.3 Field 13.003: Impression type (IMP) This mandatory one- or two-byte ASCII field shall indicate the manner by which the latent image information was obtained. The appropriate latent code choice selected from table 3.1 (finger) or table 5.3 (palm) shall be entered in this field. 7.1.4 Field 13.004: Source agency / ORI (SRC) This mandatory ASCII field shall contain the identification of the administration or organization that originally captured the facial image contained in the record. Normally, the Originating Agency Identifier (ORI) of the agency that captured the image will be contained in this field. It consists of two information items in the following format: CC/agency. The first information item contains the Interpol Country Code, two alpha-numeric characters long. The second item, agency, is a free text identification of the agency, up to a maximum of 32 alpha-numeric characters. 7.1.5 Field 13.005: Latent capture date (LCD) This mandatory ASCII field shall contain the date that the latent image contained in the record was captured. The date shall appear as eight digits in the format CCYYMMDD. The CCYY characters shall represent the year the image was captured; the MM characters shall be the tens and unit values of the month; and the DD characters shall be the tens and unit values of the day in the month. For example, 20000229 represents February 29, 2000. The complete date must be a legitimate date. 7.1.6 Field 13.006: Horizontal line length (HLL) This mandatory ASCII field shall contain the number of pixels contained on a single horizontal line of the transmitted image. 7.1.7 Field 13.007: Vertical line length (VLL) 2007/147/II. szám This mandatory ASCII field shall contain the number of horizontal lines contained in the transmitted image. 7.1.8 Field 13.008: Scale units (SLC) This mandatory ASCII field shall specify the units used to describe the image sampling frequency (pixel density). A "1" in this field indicates pixels per inch, or a "2" indicates pixels per centimetre. A "0" in this field indicates no scale is given. For this case, the quotient of HPS/VPS gives the pixel aspect ratio. 7.1.9 Field 13.009: Horizontal pixel scale (HPS) This mandatory ASCII field shall specify the integer pixel density used in the horizontal direction providing the SLC contains a "1" or a "2". Other-wise, it indicates the horizontal component of the pixel aspect ratio. 7.1.10 Field 13.010: Vertical pixel scale (VPS) This mandatory ASCII field shall specify the integer pixel density used in the vertical direction providing the SLC contains a "1" or a "2". Otherwise, it indicates the vertical component of the pixel aspect ratio. 7.1.11 Field 13.011: Compression algorithm (CGA) This mandatory ASCII field shall specify the algorithm used to compress grayscale images. Table 8 : Compression Codes Compression Type Code No Compression NONE Wavelet/Scalar Quantization (IAFIS-IC-0110) WSQ JPEG 2000 J2K 7.1.12 Field 13.012: Bits per pixel (BPX) This mandatory ASCII field shall contain the number of bits used to represent a pixel. This field shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this field greater than “8” shall represent a grayscale pixel with increased precision. 2007/147/II. szám 7.1.13 Field 13.013: Finger / palm position (FGP) This mandatory tagged-field shall contain one or more the possible finger or palm positions that may match the latent image. The decimal code number corresponding to the known or most probable finger position shall be taken from table 3.2 or the most probable palm position from table 5.3 and entered as a one- or two-character ASCII subfield. Additional finger and/or palm positions may be referenced by entering the alternate position codes as subfields separated by the “RS” separator character. The code "0", for "Unknown Finger", shall be used to reference every finger position from one through ten. The code “20”, for “Unknown Palm”, shall be used to reference every listed palmprint position. 7.1.14 Field 13.014-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. 7.1.15 Field 13.020: Comment (COM) This optional field may be used to insert comments or other ASCII text information with the latent image data. 7.1.16 Field 13.021-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. 7.1.17 Fields 13.200-998: User-defined fields (UDF) These fields are user-definable fields. Their size and content shall be defined by the user and be in accordance with the receiving agency. If present they shall contain ASCII textual information. 7.1.18 Field 13.999: Image data (DAT) This field shall contain all of data from a captured latent image. It shall always be assigned field number 999 and must be the last physical field in the record. For example, “13.999:” is followed by image data in a binary representation. Each pixel of uncompressed grayscale data shall normally be quantized to eight bits (256 gray levels) contained in a single byte. If the entry in BPX Field 13.012 is greater or less than “8”, the number of bytes required to contain a pixel will be different. If compression is used, the pixel data shall be compressed in accordance with the compression technique specified in the GCA field. 2007/147/II. szám 7.2 End of Type-13 variable-resolution latent image record For the sake of consistency, immediately following the last byte of data from field 13.999 an “FS” separator shall be used to separate it from the next logical record. This separator must be included in the length field of the Type-13 record. 8. Type-15 variable-resolution palmprint image record The Type-15 tagged-field logical record shall contain and be used to exchange palmprint image data together with fixed and user-defined textual information fields pertinent to the digitized image. Information regarding the scanning resolution used, the image size and other parameters or comments required to process the image are recorded as tagged-fields within the record. Palmprint images transmitted to other agencies will be processed by the recipient agencies to extract the desired feature information required for matching purposes. The image data shall be acquired directly from a subject using a live-scan device, or from a palmprint card or other media that contains the subject’s palmprints. Any method used to acquire the palmprint images shall be capable of capturing a set of images for each hand. This set shall include the writer’s palm as a single scanned image, and the entire area of the full palm extending from the wrist bracelet to the tips of the fingers as one or two scanned images. If two images are used to represent the full palm, the lower image shall extend from the wrist bracelet to the top of the interdigital area (third finger joint) and shall include the thenar, and hypothenar areas of the palm. The upper image shall extend from the bottom of the interdigital area to the upper tips of the fingers. This provides an adequate amount of overlap between the two images that are both located over the interdigital area of the palm. By matching the ridge structure and details contained in this common area, an examiner can confidently state that both images came from the same palm. As a palmprint transaction may be used for different purposes, it may contain one or more unique image areas recorded from the palm or hand. A complete palmprint record set for one individual will normally include the writer’s palm and the full palm image(s) from each hand. Since a tagged-field logical image record may contain only one binary field, a single Type-15 record will be required for each writer’s palm and one or two Type-15 records for each full palm. Therefore, four to six Type-15 records will be required to represent the subject’s palmprints in a normal palmprint transaction. 8.1 Fields for the Type-15 logical record The following paragraphs describe the data contained in each of the fields for the Type-15 logical record. Within a Type-15 logical record, entries shall be provided in numbered fields. It is required that the first two fields of the record are ordered, and the field containing the image data shall be the last 2007/147/II. szám physical field in the record. For each field of the Type-15 record, table 6.1 lists the “condition code” as being mandatory “M” or optional “O”, the field number, the field name, character type, field size, and occurrence limits. Based on a three digit field number, the maximum byte count size for the field is given in the last column. As more digits are used for the field number, the maximum byte count will also increase. The two entries in the “field size per occurrence” include all character separators used in the field. The “maximum byte count” includes the field number, the information, and all the character separators including the “GS” character. 8.1.1 Field 15.001: Logical record length (LEN) This mandatory ASCII field shall contain the total count of the number of bytes in the Type-15 logical record. Field 15.001 shall specify the length of the record including every character of every field contained in the record and the information separators. 8.1.2 Field 15.002: Image designation character (IDC) This mandatory ASCII field shall be used to identify the palmprint image contained in the record. This IDC shall match the IDC found in the file content (CNT) field of the Type-1 record. 8.1.3 Field 15.003: Impression type (IMP) This mandatory one-byte ASCII field shall indicate the manner by which the palmprint image information was obtained. The appropriate code selected from table 6.2 shall be entered in this field. 8.1.4 Field 15.004: Source agency/ORI (SRC) This mandatory ASCII field shall contain the identification of the administration or organization that originally captured the facial image contained in the record. Normally, the Originating Agency Identifier (ORI) of the agency that captured the image will be contained in this field. It consists of two information items in the following format: CC/agency. The first information item contains the Interpol Country Code, two alpha-numeric characters long. The second item, agency, is a free text identification of the agency, up to a maximum of 32 alpha-numeric characters. 8.1.5 Field 15.005: Palmprint capture date (PCD) This mandatory ASCII field shall contain the date that the palmprint image was captured. The date shall appear as eight digits in the format CCYYMMDD. The CCYY characters shall represent the year the image was captured; the MM characters shall be the tens and unit values of the month; and the DD characters shall be the tens and units values of the day in the month. For example, the entry 20000229 represents February 29, 2000. The complete date must be a legitimate date. 2007/147/II. szám 8.1.6 Field 15.006: Horizontal line length (HLL) This mandatory ASCII field shall contain the number of pixels contained on a single horizontal line of the transmitted image. 8.1.7 Field 15.007: Vertical line length (VLL) This mandatory ASCII field shall contain the number of horizontal lines contained in the transmitted image. 8.1.8 Field 15.008: Scale units (SLC) This mandatory ASCII field shall specify the units used to describe the image sampling frequency (pixel density). A "1" in this field indicates pixels per inch, or a "2" indicates pixels per centimeter. A "0" in this field indicates no scale is given. For this case, the quotient of HPS/VPS gives the pixel aspect ratio. 8.1.9 Field 15.009: Horizontal pixel scale (HPS) This mandatory ASCII field shall specify the integer pixel density used in the horizontal direction providing the SLC contains a "1" or a "2". Other-wise, it indicates the horizontal component of the pixel aspect ratio. 8.1.10 Field 15.010: Vertical pixel scale (VPS) This mandatory ASCII field shall specify the integer pixel density used in the vertical direction providing the SLC contains a "1" or a "2". Otherwise, it indicates the vertical component of the pixel aspect ratio. Table 9: Type-15 variable-resolution palmprint record layout Field size per occurrence Occur count Ident Cond. code Field Number Field Name Char type min. max. min. max. Max byte count LEN M 15.001 LOGICAL RECORD LENGTH N IDC M 15.002 IMAGE DESIGNATION CHARACTER N IMP M 15.003 IMPRESSION TYPE N SRC M 15.004 SOURCE AGENCY / ORI AN PCD M 15.005 PALMPRINT CAPTURE DATE N HLL M 15.006 HORIZONTAL LINE LENGTH N VLL M 15.007 VERTICAL LINE LENGTH N SLC M 15.008 SCALE UNITS N HPS M 15.009 HORIZONTAL PIXEL SCALE N VPS M 15.010 VERTICAL PIXEL SCALE N 2007/147/II. szám Field size per occurrence Occur count Ident Cond. code Field Number Field Name Char type min. max. min. max. Max byte count CGA M 15.011 COMPRESSION ALGORITHM AN BPX M 15.012 BITS PER PIXEL N PLP M 15.013 PALMPRINT POSITION N RSV 15.014 15.019 RESERVED FOR FUTURE INCLUSION -- -- -- -- -- -- CO M O 15.020 COMMENT AN RSV 15.021 15.199 RESERVED FOR FUTURE INCLUSION -- -- -- -- -- -- UDF O 15.200 15.998 USER-DEFINED FIELDS -- -- -- -- -- -- DAT M 15.999 IMAGE DATA B -- -- Table 10 : Palm Impression Type Description Code Live-scan palm Nonlive-scan palm Latent palm impression Latent palm tracing Latent palm photo Latent palm lift 8.1.11 Field 15.011: Compression algorithm (CGA) This mandatory ASCII field shall specify the algorithm used to compress grayscale images. An entry of "NONE" in this field indicates that the data contained in this record is uncompressed. For those images that are to be compressed, this field shall contain the preferred method for the compression of tenprint fingerprint images. Valid compression codes are defined in table A7.1. 2007/147/II. szám 8.1.12 Field 15.012: Bits per pixel (BPX) This mandatory ASCII field shall contain the number of bits used to represent a pixel. This field shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this field greater than or less than “8” shall represent a grayscale pixel with increased or decreased precision respectively. Table 11: Palm Codes, Areas & Sizes Palm Position Palm code Image area (mm2) Width (mm) Height (mm) Unknown Palm 139.7 203.2 Right Full Palm 139.7 203.2 Right Writer s Palm 44.5 127.0 Left Full Palm 139.7 203.2 Left Writer s Palm 44.5 127.0 Right Lower Palm 139.7 139.7 Right Upper Palm 139.7 139.7 Left Lower Palm 139.7 139.7 Left Upper Palm 139.7 139.7 Right Other 139.7 203.2 Left Other 139.7 203.2 8.1.13 Field 15.013: Palmprint position (PLP) This mandatory tagged-field shall contain the palmprint position that matches the palmprint image. The decimal code number corresponding to the known or most probable palmprint position shall be taken from table 6.3 and entered as a two-character ASCII subfield. Table 6.3 also lists the maximum image areas and dimensions for each of the possible palmprint positions. 8.1.14 Field 15.014-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. 8.1.15 Field 15.020: Comment (COM) This optional field may be used to insert comments or other ASCII text information with the palmprint image data. 8.1.16 Field 15.021-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. 2007/147/II. szám 8.1.17 Fields 15.200-998: User-defined fields (UDF) These fields are user-definable fields. Their size and content shall be defined by the user and be in accordance with the receiving agency. If present they shall contain ASCII textual information. 8.1.18 Field 15.999: Image data (DAT) This field shall contain all of the data from a captured palmprint image. It shall always be assigned field number 999 and must be the last physical field in the record. For example, “15.999:” is followed by image data in a binary representation. Each pixel of uncompressed grayscale data shall normally be quantized to eight bits (256 gray levels) contained in a single byte. If the entry in BPX Field 15.012 is greater or less than 8, the number of bytes required to contain a pixel will be different. If compression is used, the pixel data shall be compressed in accordance with the compression technique specified in the CGA field. 8.2 End of Type-15 variable-resolution palmprint image record For the sake of consistency, immediately following the last byte of data from field 15.999 an “FS” separator shall be used to separate it from the next logical record. This separator must be included in the length field of the Type-15 record. 8.3 Additional Type-15 variable-resolution palmprint image records Additional Type-15 records may be included in the file. For each additional palmprint image, a complete Type-15 logical record together with the “FS” separator is required. 2007/147/II. szám APPENDIX 1 ASCII Separator Codes ASCII Position1 Description LF 1/10 Separates error codes in field 2.074 FS 1/12 Separates logical records of a file. GS 1/13 Separates fields of a logical record. RS 1/14 Separates the subfields of a record field. US 1/15 Separates individual information items of the field or subfield. APPENDIX 2 Calculation of Alpha-Numeric Check Character For TCN and TCR (Fields 1.09 and 1.10): The number corresponding to the check character is generated using the following formula: (YY * 108 + SSSSSSSS) Modulo 23 Where YY and SSSSSSSS are the numerical values of the last two digits of the year and the serial number respectively. The check character is then generated from the look-up table given below. For CRO (Field 2.010) The number corresponding to the check character is generated using the following formula: (YY * 106 + NNNNNN) Modulo 23 Where YY and NNNNNN are the numerical values of the last two digits of the year and the serial number respectively. The check character is then generated from the look-up table given below. This is the position as defined in the ASCII standard. 2007/147/II. szám Check Character Look-up Table 1-A 9-J 17-T 2-B 10-K 18-U 3-C 11-L 19-V 4-D 12-M 20-W 5-E 13-N 21-X 6-F 14-P 22-Y 7-G 15-Q 0-Z 8-H 16-R APPENDIX 3 Character Codes 7-bit ANSI code for information interchange ASCII Character Set + ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~ 2007/147/II. szám APPENDIX 4 Transaction Summary Type 1 Record (mandatory) Identifier Field Number Field Name CPS/ PMS SRE ERR LEN 1.001 Logical Record Length M M M VER 1.002 Version Number M M M CNT 1.003 File Content M M M TOT 1.004 Type of Transaction M M M DAT 1.005 Date M M M PRY 1.006 Priority M M M DAI 1.007 Destination Agency M M M ORI 1.008 Originating Agency M M M TCN 1.009 Transaction Control Number M M M TCR 1.010 Transaction Control Reference C M M NSR 1.011 Native Scanning Resolution M M M NTR 1.012 Nominal Transmitting Resolution M M M DOM 1.013 Domain name M M M GMT 1.014 Greenwich mean time M M M Under the Condition Column: O = Optional; M = Mandatory; C = Conditional if transaction is a response to the origin agency Type 2 Record (mandatory) Identifier Field Number Field Name CPS/ PMS MPS/ MMS SRE ERR LEN 2.001 Logical Record Length M M M M IDC 2.002 Image Designation Character M M M M SYS 2.003 System Information M M M M CNO 2.007 Case Number - M C - SQN 2.008 Sequence Number - C C - MID 2.009 Latent Identifier - C C - CRN 2.010 Criminal Reference Number M - C - MN1 2.012 Miscellaneous Identification Number - - C C MN2 2.013 Miscellaneous Identification Number - - C C MN3 2.014 Miscellaneous Identification Number - - C C MN4 2.015 Miscellaneous Identification Number - - C C 2007/147/II. szám Identifier Field Number Field Name CPS/ PMS MPS/ MMS SRE ERR INF 2.063 Additional Information O O O O RLS 2.064 Respondents List - - M - ERM 2.074 Status/Error Message Field - - - M ENC 2.320 Expected Number of Candidates M M - - Under the Condition Column: O = Optional; M = Mandatory; C = Conditional if data is available *) = if the transmission of the data is in accordance with national law (not covered by the Treaty) APPENDIX 5 Type-1 Record Definitions Table A.5: Type-1 Record Definitions Identifier Condition Field Number Field Name Character Type Example Data LEN M 1.001 Logical Record Length N 1.001:230{GS} VER M 1.002 Version Number N 1.002:0300{GS} CNT M 1.003 File Content N 1.003:1{US}15{RS}2{US}00{RS} 4{US}01{RS}4{US}02{RS}4{US }03{RS}4{US}04{RS}4{US}05{ RS}4{US}06{RS}4{US}07{RS}4 {US}08{RS}4{US}09{RS}4{US} 10{RS}4{US}11{RS}4{US}12{R S}4{US}13{RS}4{US}14{GS} TOT M 1.004 Type of Transaction A 1.004:CPS{GS} DAT M 1.005 Date N 1.005:20050101{GS} PRY M 1.006 Priority N 1.006:4{GS} DAI M 1.007 Destination Agency 1* 1.007:DE/BKA{GS} ORI M 1.008 Originating Agency 1* 1.008:NL/NAFIS{GS} TCN M 1.009 Transaction Control Number AN 1.009:0200000004F{GS} TCR C 1.010 Transaction Control Reference AN 1.010:0200000004F{GS} NSR M 1.011 Native Scanning Resolution AN 1.011:19.68{GS} NTR M 1.012 Nominal Transmitting Resolution AN 1.012:19.68{GS} DOM M 1.013 Domain Name AN 1.013: INT-I{US}4.22{GS} GMT M 1.014 Greenwich Mean Time AN 1.014:20050101125959Z Under the Condition Column: O= Optional, M= Mandatory, C= Conditional Under the Character Type Column: A= Alpha, N= Numeric, B= Binary 1* allowed characters for agency name are ["0..9", "A..Z", "a..z", "_", ".", " ", "-"] 2007/147/II. szám APPENDIX 6 Type-2 Record Definitions Table A.6.1: CPS- and PMS-Transaction Identifier Condition Field Number Field Name Character Type Example Data LEN M 2.001 Logical Record Length N 2.001:909{GS} IDC M 2.002 Image Designation Character N 2.002:00{GS} SYS M 2.003 System Information N 2.003:0422{GS} CRN M 2.010 Criminal Reference Number AN 2.010:DE/E999999999{GS} INF O 2.063 Additional Information 1* 2.063:Additional Information 123{GS} ENC M 2.320 Expected Number of Candidates N 2.320:1{GS} Table A.6.2: SRE-Transaction Identifier Condition Field Number Field Name Character Type Example Data LEN M 2.001 Logical Record Length N 2.001:909{GS} IDC M 2.002 Image Designation Character N 2.002:00{GS} SYS M 2.003 System Information N 2.003:0422{GS} CRN M 2.010 Criminal Reference Number AN 2.010:NL/2222222222{GS} MN1 C 2.012 Miscellaneous Identification Number AN 2.012:E999999999{GS} MN2 C 2.013 Miscellaneous Identification Number AN 2.013:E999999999{GS} MN3 C 2.014 Miscellaneous Identification Number N 2.014:0001{GS} MN4 C 2.015 Miscellaneous Identification Number A 2.015:A{GS} INF O 2.063 Additional Information 1* 2.063:Additional Information 123{GS} RLS M 2.064 Respondents List AN 2.064:CPS{RS}I{RS}001/001 {RS}999999{GS} 2007/147/II. szám Table A.6.3: ERR-Transaction Identifier Condition Field Number Field Name Character Type Example Data LEN M 2.001 Logical Record Length N 2.001:909{GS} IDC M 2.002 Image Designation Character N 2.002:00{GS} SYS M 2.003 System Information N 2.003:0422{GS} MN1 M 2.012 Miscellaneous Identification Number AN 2.012:E999999999{GS} MN2 C 2.013 Miscellaneous Identification Number AN 2.013:E999999999{GS} MN3 C 2.014 Miscellaneous Identification Number N 2.014:0001{GS} MN4 C 2.015 Miscellaneous Identification Number A 2.015:A{GS} INF O 2.063 Additional Information 1* 2.063:Additional Information 123{GS} ERM M 2.074 Status/Error Message Field AN 2.074: 201: IDC -1 FIELD 1.009 WRONG CONTROL CHARACTER {LF} 115: IDC 0 FIELD 2.003 INVALID SYSTEM INFORMATION {GS} Table A.6.4: MPS- and MMS-Transaction Identifier Condition Field Number Field Name Character Type Example Data LEN M 2.001 Logical Record Length N 2.001:909{GS} IDC M 2.002 Image Designation Character N 2.002:00{GS} SYS M 2.003 System Information N 2.003:0422{GS} CNO M 2.007 Case Number AN 2.007:E999999999{GS} SQN C 2.008 Sequence Number N 2.008:0001{GS} MID C 2.009 Latent Identifier A 2.009:A{GS} INF O 2.063 Additional Information 1* 2.063:Additional Information 123{GS} ENC M 2.320 Expected Number of Candidates N 2.320:1{GS} Under the Condition Column: O= Optional, M= Mandatory, C= Conditional Under the Character Type Column: A= Alpha, N= Numeric, B= Binary 1* allowed characters are ["0..9", "A..Z", "a..z", "_", ".", " ", "-", ","] 2007/147/II. szám APPENDIX 7 Grayscale Compression Codes A.7.1 Compression Codes Compression Value Remarks Wavelet Scalar Quantization Grayscale Fingerprint Image Compression Specification IAFIS-IC-0010(V3), dated December 19, 1997 WSQ Algorithm to be used for the compression of grayscale images in Type-4, Type-7 and Type-13 to Type-15 records. Shall not be used for resolutions >500dpi. JPEG 2000 [ISO 15444 / ITU T.800] J2K To be used for lossy and losslessly compression of grayscale images in Type-13 to Type-15 records. Strongly recommended for resolutions >500 dpi APPENDIX 8 Mailspecification To improve the internal workflow the mailsubject of a PRUEM transaction has to be filled with the country code (CC) of the Party that send the message and the Type of Transaction (TOT Field 1.004). Format: CC/type of transaction Example: "DE/CPS" The mailbody can be empty. The specification of the encryption/signing and the used S/MIME Version will follow as soon as possible in this Appendix, after clarify this points with the DNA Technical Work Group. 2007/147/II. szám Annex B.2 Maximum Number of candidates accepted for verification Type of AFIS Search TP/TP LT/TP LP/PP TP/UL LT/UL PP/ULP LP/ULP Maximum Number of Candidates Search types: TP/TP: ten-print against ten-print LT/TP: fingerprint latent against ten-print LP/PP: palmprint latent against palmprint TP/UL: ten-print against unsolved fingerprint latent LT/UL: fingerprint latent against unsolved fingerprint latent PP/ULP: palmprint against unsolved palmprint latent LP/ULP: palmprint latent against unsolved palmprint latent 2007/147/II. szám Annex B.3 Maximum research capacities per day for dactyloscopic data of identified persons BE NL LU AT FR ES DE BE - NL - LU - AT - FR - ES - DE 1201) 1201) 1201) 1201) 1201) - 1) estimated throughput for 2007: 60 TP/TP per day 2007/147/II. szám Annex B.4 Maximum research capacities per day for dactyloscopic traces BE NL LU AT FR ES DE BE - NL - LU - AT - FR - ES - DE 40 1) 40 1) 40 1) 40 1) 40 1) - 1) estimated throughput for 2007: 20 LP/TP per day Annexes C Automated searching for vehicle registration data Annex C.1 Common data-set for automated search of vehicle registration data 1. Definitions For each element in the data set as described in the next chapter, an indication is given whether the element is especially allocated by the Parties and whether the element is mandatory or optional when the exchange is used for the purposes of Article 12 of the Treaty. The definitions of mandatory data elements and optional data elements are as follows: 2007/147/II. szám Mandatory (M): The data element has to be communicated when the information is available in one’s national register. Therefore there is an obligation to exchange the information when available. Optional (O): The data element may be communicated when the information is available in one’s national register. Therefore there is no obligation to exchange the information even when the information is available. An indication (Y) is given for each element in the data set whether the element is specifically indicated by the Parties in relation with the Treaty. 2. Vehicle/Owner/Holder Inquiry 2.1 Triggers for the Inquiry There are two different ways to search for the information as defined in the next paragraph:

Source: https://magyarkozlony.hu/hivatalos-lapok/88f4b71203e560b8dbaa15136351c7dfe188776c/dokumentumok/48b7c45847440d497b8eccef756edae7b80ff74c/letoltes