The recommendations for the capture of mugshots and facial images have been
developed to find the best compromise between the requirements of the police
forces for person searches and identification as well as the size of the image
files.
During the tests, mugshots were taken with different resolutions and then processed
using different ratio rates. The resulting files were printed by a high resolution
printer (Fuji Pictography 3000, 320 dpi, true color) and examined by our experts.
Analyzing the different expertises we set up the following recommendations:
In addition to the full-face or frontal pose, two angled poses with 45 and
90 degrees should be aquired. For persons normally wearing glasses a frontal
mugshot of the subject without glasses should be captured too.
The facial image should be in focus from the nose to the ears. To minimize
distortions the focal length shall be between 85mm to 135mm in reference to
a 35mm camera. The camera should be positioned on the same height as the subject's
eyes.
The mid-points of the mouth and of the bridge of the nose shall be horizontally
centered.
Approximately 50% of the width of the captured image should be covered by the
subject's face. An imaginary horizontal line through the eyes should be located
at approximately 55-60% of the vertical hight.
A minimum of two photo lights shall be used to illuminate the subjects face.
It is important to adjust the lights to minimize shadows and hot spots.
To fulfill the rquirements of person identification, the minimum of pixels
in a digital image should be 600 pixels in horizontal and 800 pixels in vertical
direction. The colorspace of the image shall be 24-bit RGB. To minimze the size
of a digital image file the JPEG compression algorithm shall be used. A compression
ratio of 20 should not be exceeded.
This field contains a three letter mnemonic designating the type of the transaction.
These codes are different from those used by the FBI but similar to those in
the UK-I.
| IRQ: |
Image Request. This transaction allows
the fingerprint officer to retrieve fingerprints and scenes of crime marks
from an image database. It contains only sufficient information to enable
the system to make a unique identification of the required prints or marks.
For marks the Case Number (CNO), Sequence Number (SQN) and Mark Identifier
(MID) must be specified, while for prints one of the following must be
specified: Criminal Reference Number (CRO), Other Reference Number (ORN)
or Miscellaneous Reference Number (MN1 to MN5).
|
| IMR: |
Image Response. This transaction is for
the transmission of a print or mark image from a collection, often in
response to an IRQ transaction. The Type-2 record may contain textual
information relevant to the image.
|
| CPS: |
Criminal Print-to-Print Search. This
transaction is a request for a search of a record relating to a criminal
offence against a Prints database. If the person’s prints are not
already in the remote system they must be included as images in the file.
|
| NPS: |
Non-Criminal Print-to-Print Search. This
transaction is a request for a search against a Prints database that falls
outside the scope of a CPS transaction. If the person’s prints are
not already in the remote system they must be included as images in the
file.
|
| MPS: |
Mark-to-Print Search. This transaction
is used when a mark is to be searched against a Prints database. If the
mark is not already in the remote system, it must be included as an image
in the file.
|
| PMS: |
Print-to-Mark Search. This transaction
is used when a set of prints is to be searched against an Unidentified
Marks database. If the person’s prints are not already in the remote
system they must be included as images in the file. If they are already
present in the remote system, they may instead be specified by one of
the unique identification numbers in the Type-2 record.
|
| MMS: |
Mark-to-Mark Search. In this transaction
the file contains a mark which is to be searched against an Unidentified
Marks database in order to establish links between various scenes of crime.
If the mark is not already in the remote system, it must be included as
an image in the file.
|
| DBS: |
Database Search. This transaction is intended
primarily as a means of searching a remote image database, and only contains
a Type-1 and a Type-2 record. The Type-2 record specifies the textual
parameters for a fingerprint, mark or photo search. The result of the
search is an SRE transaction which lists those fingerprints, marks or
photos that meet the search criteria. The images can then be retrieved
using an IRQ or an PHR request.
|
| SRE: |
Search Results. This transaction contains
a Type-1 and Type-2 record which detail the results of the search. The
way fields are interpreted will depend on the original search request
and to whom the search request was sent. If the SRE transaction is coming
from an AFR system, the AFR system will specify a list of potential matches
in the Respondents List (RLS). Additional information regarding the search,
such as images and signatures can be attached to the record using Type-4,
Type-7, Type-8 or Type-10 records.
|
| USA: |
Add Mark to Unidentified Marks Collection.
Besides containing the image of the mark being added to the database,
or the image of a complete lift or photograph, the file includes a Type-2
record in which information is transmitted about the mark.
It is likely that a system would be designed
to block such a transaction initiated by a remote agency unless it had
been specifically authorised by a senior user of the receiving agency.
In some circumstances, a full lift or
photograph of a sequence of marks is to be transmitted from one system
to another, by agreement with both parties and not in response to an IRQ.
In such circumstances the following apply.
- Any block on USA transactions must
be removed.
- The image of the original must be transmitted
as a Type-7 Record, captured at high resolution.
|
| USR: |
Remove Mark from Unidentified Marks Collection.
This transaction contains, besides the Type-1 record, only a Type-2 record
in which enough information is given to uniquely specify the mark.
It is likely that a system would be designed
to block such a transaction initiated by a remote agency unless it had
been specifically authorised by a senior user of the receiving agency.
|
| ATP: |
Add To Print Collection. This transaction
is used for sending a complete set of prints or an entire fingerprint form
to a remote site, as a new record or to replace an existing record. The
FIB field (Fingerprint Identification Byte) of the Type-2 record identifies
the reason for fingerprinting. The other fields in the record can be used
to specify other details about the fingerprinted subject which may be stored
by the AFR system or the image database.
It is likely that a system would be designed
to block such a transaction initiated by a remote agency unless it had
been specifically authorised by a senior user of the receiving agency.
In certain circumstances complete ten-print
forms are to be transmitted from one system to another, by agreement with
both parties and not in response to an IRQ. In such circumstances the
following apply.
- Any block on ATP transactions must
be removed.
- A Type-7 Record must be transmitted which contains an image of the
full ten-print form. Field 7.04 (IMD) must be "47".
|
| SUP: |
Substitute Print(s) Into Existing Ten-Print.
During this transaction individual print(s) are transmitted to replace
those in an existing ten-print.
It is likely that a system would be designed
to block such a transaction initiated by a remote agency unless it had
been specifically authorised by a senior user of the receiving agency.
|
| DFP: |
Delete From Print Collection. This transaction
is used to remove a complete record from a Print collection. Like the
USR, this transaction only contains a Type-1 and a Type-2 record with
enough information to uniquely identify the relevant record.
It is likely that a system would be designed
to block such a transaction initiated by a remote agency unless it had
been specifically authorised by a senior user of the receiving agency.
|
| DIP: |
Disregard Individual Print(s) Update.
This transaction advises the receiving agency that print(s) supplied by
a previous SUP transaction should no longer be used.
|
| CPR: |
Criminal Subject Photo Request. This transaction
allows the police officer to retrieve a photo set from an image database.
Each set of photos contains one or more photos of a subject posed from
different views and other photos linked to the person (e.g. tattoos, scars).
The Type-2 Record of this transaction contains only sufficient information
to enable the system to make a unique identification of the person. One
of the following must be specified: Criminal Reference Number (CRO), Other
Reference Number (ORN) or Miscellaneous Reference Number (MN1 to MN5).
|
| PHR: |
Photo Response. This transaction is for
the transmission of a photo set from a collection, often in response to
a CPR transaction. The Type-2 record may contain textual information relevant
to the photo.
|
| APC: |
Add To Print Collection. This transaction
is used for sending a complete set of photos and a complete set of fingerprints
to a remote site, as a new record or to replace an existing record. The
FIB field (Fingerprint Identification Byte) of the Type-2 record identifies
the reason for taking fingerprints and photos. The other fields in the
record can be used to specify other details about the person which may
be stored in the database.
|
| DPC: |
Delete From Photo Collection. This transaction
is used to remove a complete set of photos from a photo collection. Like
the USR and DFP, this transaction only contains a Type-1 and a Type-2
record with enough information to uniquely identify the relevant record.
|
| CPP: |
Criminal Photo-to-Photo Search. This transaction
is a request for an automated search of a photo set relating to a criminal
offence against a Photo database.
|
| NPP: |
Non-Criminal Photo-to-Photo Search. This
transaction is a request for an automated search against a Photo database
that falls outside the scope of a CPP transaction.
|
| ERR: |
Error Message. This transaction is generated
if the remote system has difficulty performing the transaction, e.g. if
the unique reference number specified for an IRQ does not exist, or if a
particular search is not allowed on the system. The Type-2 record will contain
the error message. Which error messages are generated in what circumstances
is an issue for the system designer. |
The definition of these transactions implies that what appears to the fingerprint
officer performing a search as one transaction may, in fact, involve a number
of separate transactions between the fingerprint officer’s workstation
and the remote site.
One limitation of the standard is that it is not permissable for the file to
have more than one transaction field. Thus if, say, a mark is to be searched
against both the marks database and the prints database, two separate files
must be sent.
