Performs a one-to-many comparison of the given samples with the stored biometric templates in order to identify the individuals that are most likely represented by the given samples.
bool Identify(BiometricClassID partition, Sample samples, ClassificationFlags flags, int maxResults, out ScoredClass matches, out string messages)
true when the given classId could have been verified successfully with the given samples;
false otherwise, or when errors occurred (see messages for details).
A biometric identification tests the given samples against all samples (biometric templates) stored in the the specified partition of the cloud storage. A list of identified BCIDs (Biometric Class IDs) is generated and sorted according to the score (a kind of probability of similarity) that has been calculated for each BCID. Note that only those BCIDs are considered that have a biometric template available for each trait specified by the delivered samples.
This method now supports liveness detection (currently supported traits are face and periocular). To activate liveness detection, simply use the flag ClassificationFlags.LiveFaceDetection or ClassificationFlags.LivePeriocularDetection with the flags parameter. Note that in this case the identification will only succeed, when it can undoubtedly determine that the given data is live data. In case that the live detection succeeds, the degree of the head rotation between two subsequent images is reported with the returned messages XML-string.
Internally this operation performs a QualityCheck (in BioID ExtractTokenData mode) for all submitted samples before they are forwarded to the liveness detection - in case a live-detection flag is set - and finally the identification is performed. Therefore you might get results from these operations as well together with the identification results.
This API has a fault contract of type BioIDWebServiceFault, which is used for fatal errors like invalid arguments or missing service, etc. Messages, even error messages, generated by the identification procedure are reported via the messages output value, which contains an XML string according to the BWSMessages schema namespace.
The messages output XML string might contain operation specific errors as follows:
The messages output XML string might also contain errors for the individual samples. Many of the errors can result from the initial quality-check that is performed before anything else is done. Please refer to the QualityCheck method for a list of sample errors that might have been generated by the quality-check.
Additionally the following errors can occur. With any of theses errors the sample is marked as unsuitable and is not considered in the identification process: