Wrong UK address resolution

[codekrolik2]

Describe the bug
Wrong UK address resolution

To Reproduce
Run
./address_parser /Users/john/projects/libpostal/senzing/libpostal

> 3 Juvina Cl, Witham CM8 1QL, UK, Braintree, CM81QL

Result:

{
  "house_number": "3",
  "road": "juvina cl",
  "city": "witham",
  "postcode": "cm8 1ql",
  "house": "uk braintree cm81ql"
}

Expected behavior

{
  "house_number": "3",
  "road": "juvina cl",
  "city": "witham",
  "postcode": "cm8 1ql",
  "country": "uk",
  "state": "braintree"
}

Screenshots

Desktop (please complete the following information):

• OS: MacOs 13 Ventura
• Browser N/A
• Version N/A

Smartphone (please complete the following information):

• Device: N/A
• OS: N/A
• Browser N/A
• Version N/A

Additional context
The rumor has it that this model was created by Senzing Inc. for improved parsing on US, UK and Singapore addresses.
Well, this address is from UK, and leaves the model without a clue, let's fix it!

[oskar700]

@codekrolik2 Thanks for the information. We will work on this. There will be one change for the expected results: "braintree" will be classified as "state_district".

[oskar700]

We posted a new model last week, version 1.2.0. I tested the address with the new version:

> 3 Juvina Cl, Witham CM8 1QL, UK, Braintree, CM81QL

Result:

{
  "house_number": "3",
  "road": "juvina cl",
  "city": "witham",
  "postcode": "cm8 1ql",
  "city": "uk",
  "state_district": "braintree",
  "postcode": "cm81ql"
}

Only issue is "uk" labeled as "city".

With properly formed address the parse is perfect:

> 3 Juvina Cl, Witham  Braintree, CM81QL uk

Result:

{
  "house_number": "3",
  "road": "juvina cl",
  "city": "witham",
  "state_district": "braintree",
  "postcode": "cm81ql",
  "country": "uk"
}