DS 2019 OCR

This article walks you through the building process of an OCR API that extracts data from the DS 2019 form using our deep learning engine. It will work for any airline company or boarding pass template.

Prerequisites

  1. You’ll need a free account. Sign up and confirm your email to login.
  2. You’ll need at least 20 DS 2019 form images or pdfs to train your OCR.

Define your DS 2019 use case

First, we’re going to define what fields we want to extract from your DS 2019 form.

DS 2019 key data extraction

  • First Name: The first name of the DS 2019 holder
  • Family Name: The last name of the DS 2019 holder
  • Gender: The DS 2019 holder gender
  • Visa type: The visa type linked to the DS 2019 form
  • End of cover period: The ending date of the DS 2019 cover period

That’s it for our use case. Feel free to add any other relevant data to fit your requirements.

Deploy your API

Once you have defined the list of fields you want to extract, head over to the platform and press the ‘Create a new API’ button.

You land now on the setup page. Here is the image you can use to set up the API. For instance, my setup is as follows:

Set up your API

Once you’re ready, click on the “next” button. We are going to specify the data types for each of the fields we want our API to extract.

Define your model

To move forward, you have two possibilities:

Upload a json config
Copy the following JSON into a file and upload it on the interface

{
  "problem_type": {
    "classificator": { "features": [], "features_name": [] },
    "selector": {
      "features": [
        {
          "cfg": { "filter": { "alpha": -1, "numeric": 0 } },
          "handwritten": false,
          "name": "first_name",
          "public_name": "First name",
          "semantics": "word"
        },
        {
          "cfg": { "filter": { "alpha": -1, "numeric": 0 } },
          "handwritten": false,
          "name": "family_name",
          "public_name": "Family name",
          "semantics": "word"
        },
        {
          "cfg": { "filter": { "alpha": -1, "numeric": 0 } },
          "handwritten": false,
          "name": "gender",
          "public_name": "Gender",
          "semantics": "word"
        },
        {
          "cfg": { "filter": { "alpha": -1, "numeric": -1 } },
          "handwritten": false,
          "name": "visa_type",
          "public_name": "Visa Type",
          "semantics": "word"
        },
        {
          "cfg": { "filter": { "convention": "US" } },
          "handwritten": false,
          "name": "end_of_cover_period",
          "public_name": "End of cover period",
          "semantics": "date"
        }
      ],
      "features_name": [
        "first_name",
        "family_name",
        "gender",
        "visa_type",
        "end_of_cover_period"
      ]
    }
  }
}

Or build your data model manually
Using the interface, add up to your data model each field.

In our example, here are the different field configurations we used:

  • First name: type String that never contains numeric characters.
  • Family name: type String that never contains numeric characters.
  • Gender: type String that never contains numeric characters.
  • Visa Type: type String without specifications.
  • End of cover period: type Date in US format.

Once you’re done setting up your data model, press the Start training your model button at the bottom of the screen.

Ready to train model

Train your DS 2019 form OCR

Train your model

You’re all set!

Now is the time to train your DS 2019 deep learning model in the Training section of our API.

In a few hours (minutes if you're fast), you’ll get your first model trained and will be able to use your custom OCR API for parsing DS 2019 form in your application.

To get more information about the training phase, please refer to the Getting Started tutorial. If you have any question regarding your use case, feel free to reach out on our chat!

Updated 28 days ago


DS 2019 OCR


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.