BlinkID / blinkid-android

Everything you need to add AI-driven ID scanning into your native Android app.
https://microblink.com/identity/identity-document-scanning/
438 stars 153 forks source link

Korean ID Card Information Extraction #259

Closed hassammughal closed 1 year ago

hassammughal commented 2 years ago

There is not enough information being extracted from Korean ID Card. The good thing was that it does hide the Registration Number, but it doesn't extract the other information such as Name, Address, Date of expiry. In addition the registration number should be shown like this: 920301-4** in the personal number field.

anjapenic commented 2 years ago

Hello @hassammughal,

You can check out here - https://github.com/BlinkID/blinkid-android/blob/master/documentation/BlinkIDRecognizerResult.md which documents are supported and which fields are extracted. In case of South Korean ID, only date of issue and document number fields can be extracted.

Best regards, Anja

hassammughal commented 2 years ago

Hello @anjapenic, Thanks for sharing. So, what is the procedure to put a request for extracting the masked personal id number along with name in Korean language? Or, is there any way that we can contribute in this project and develop this feature?

anjapenic commented 2 years ago

Hi @hassammughal,

Unfortunately, it's not possible to extract the name in Korean language. Since the document number is anonymized, in order to extract it, please try disabling the AnonymizationMode by setting it to none, for example, like this:

        recognizer = new BlinkIdRecognizer();

        recognizer.setAnonymizationMode(AnonymizationMode.None);

You can extract the document number and date of issue from the results like this:

        BlinkIdRecognizer.Result result = recognizer.getResult();

        String docNumber = result.getDocumentNumber();

        String dateOfIssue = result.getDateOfIssue().toString();

Hope this helps, let us know if you extracted the fields successfully.

Best regards, Anja

krizaa commented 1 year ago

This issue was closed because it has been inactive for such a long time. If the issue persists, please open a new one.