Open pcampospaulo opened 2 years ago
Describe the bug
I've found a strange behaviour when searching for a postal code "AB10 1ST"
Steps to Reproduce
https://pelias.github.io/compare/#/v1/autocomplete?layers=postalcode&focus.point.lat=54.753161&focus.point.lon=-2.554325&text=AB10+1ST
with the query above several results are returned but not the correct ("AB10 1ST"): AB10 1GS AB10 1WS AB10 1ZX AB10 1ZG ...
The expected result is found if a comma is added to the end "AB10 1ST,"
https://pelias.github.io/compare/#/v1/autocomplete?layers=postalcode&focus.point.lat=54.753161&focus.point.lon=-2.554325&text=AB10+1ST%2C
Additional information
parsers return the data for both inputs: "parsed_text": { "subject": "AB10 1ST" },
Thanks for the report, after some investigation we found that there is a conflict with the functionality which flattens English diacriticals such as 1st, 2nd, 3rd, 4th but we're still discussing a fix for it.
Describe the bug
I've found a strange behaviour when searching for a postal code "AB10 1ST"
Steps to Reproduce
https://pelias.github.io/compare/#/v1/autocomplete?layers=postalcode&focus.point.lat=54.753161&focus.point.lon=-2.554325&text=AB10+1ST
with the query above several results are returned but not the correct ("AB10 1ST"): AB10 1GS AB10 1WS AB10 1ZX AB10 1ZG ...
The expected result is found if a comma is added to the end "AB10 1ST,"
https://pelias.github.io/compare/#/v1/autocomplete?layers=postalcode&focus.point.lat=54.753161&focus.point.lon=-2.554325&text=AB10+1ST%2C
Additional information
parsers return the data for both inputs: "parsed_text": { "subject": "AB10 1ST" },