Intelligent Address Parsing

Intelligent Address Parsing is an optional addon that delivers preprocessing capability for difficult, incomplete, or OCR-derived addresses. It identifies structured components in raw address input before the address is sent through the existing validation workflow.

Intelligent Address Parsing complements validation. It does not replace validation and does not, by itself, confirm that an address is deliverable. It is available through the REST interface only.

Before configuring the capability, review the Prerequisites.

Make sure that you have:

• Pro REST version 8.13 or later.
• A valid product licence and the required Pro Web REST configuration files:
  qalicn.ini, qawserve.ini, and qaworld.ini.

Installing

Intelligent Address Parsing is packaged in a separate installer. Run the installer and complete the neccessary steps. It is recommended that the installation is done within the same environment where Pro Web is installed.

During installation, the user must decide on a port number, where Intelligent Address Parsing service will run. After completing the installation, the service will run in this port.

How it works

The setup require two services:

• Intelligent Address Parsing is an ASP.NET Core service that does the address parsing.
• Pro REST is a Java REST server that exposes the parsing end-point.

Configure

Within ProWeb installation folder, you must locate “application.properties” file. The file is part of the “config” folder. Edit the “application.properties“ and reflect the Intelligent Address Parsing port number.

Example:

mlparser.grpc.host=myserver
mlparser.grpc.port=9090
mlparser.grpc.deadline=PT30S

Once this is done, restart the Pro Web REST service.
After the restart, both services should have an additional end-point in the swagger:

/address/parse/v1
/address/expand/v1
/address/bulk/parse/v1
/address/bulk/expand/v1

Licence requirements

The parsing and expansion endpoints are licence-guarded. All of the following conditions must be met:

1. A valid product licence is present in qalicn.ini.
2. InstalledData in qawserve.ini is configured for the country covered by the licence.

Workflow process

1. Send the raw and unstructured address to Intelligent Address Parsing end-point.
2. Use the structured components from the response to prepare the validation request.
3. Send the structured address to the existing validation endpoint.
4. Use the validation response and status information as the source of truth for the validated address.

Use parsing before validation when the input is difficult to interpret or incomplete.

Parse an address

Use POST /address/parse/v1 to identify components in an address.

Example request:

{
  "input": {
    "reference_id": "gbr-001",
    "input": "10 Downing Street, Westminster, London, SW1A 2AA, United Kingdom"
  }
}

Example response:

{
  "result": {
    "reference_id": "gbr-001",
    "original_search": "10 Downing Street, Westminster, London, SW1A 2AA, United Kingdom",
    "parsed_components": [
      {
        "value": "10",
        "name": "building_number"
      },
      {
        "value": "downing street",
        "name": "street"
      },
      {
        "value": "westminster",
        "name": "district"
      },
      {
        "value": "london",
        "name": "town"
      },
      {
        "value": "sw1a 2aa",
        "name": "postal_code"
      },
      {
        "value": "united kingdom",
        "name": "country_name"
      }
    ]
  }
}

Expand an address

Use POST /address/expand/v1 to return possible expansions for abbreviated or ambiguous address text.

Example request:

{
  "input": 
    {
      "reference_id": "e1",
      "input": "One-hundred twenty E 96th St"
    }
}

Example response:

{
  "result": 
    {
      "reference_id": "e1",
      "original_search": "One-hundred twenty E 96th St",
      "expansions": [
        "120 e 96th street",
        "120 east 96th street"
      ]
    }

}