cozydvlpr

Hi @missinglink, is there any progress on this issue? In my use case I need to find addresses using the postal code on the openaddresses source and on custom sources....

Sure, my Pelias includes only Portugal (PT/PRT) data `curl -v -k ':4000/v1/search/structured?postalcode=1170-257&sources=oa' | jq` Result ``` { "geocoding": { "version": "0.2", "attribution": "http://xxxxxx:4000/attribution", "query": { "parsed_text": { "postalcode": "1170-257" },...

Thanks for the quick change. I pulled the new image but it did not work. You can see my case here: https://pelias.github.io/compare/#/v1/search/structured?layers=postalcode&postalcode=1170-257&country=Portugal&debug=1 ~can be the dash in the postal code...

Thanks for your explanation, I understand. Do you have any suggestions to resolve my specific use case?

actually I need only to find one address with the given postalcode. In a second call, I'll use its coordinates to restrict the search area

My current infrastructure offers OpenSearch 2.11. I'm patching here and there to check if I can make Pelias run on that. Following this issue. However, no Elasticsearch client will allow...