Closed dr0i closed 5 years ago
While a direct lookup in ES results ok , e.g. lod@gaia:pelias$ curl "172.20.0.2:9200/pelias/address/_search?q=name.default:gutenbergstraße"
, the api call to curl "http://gaia.hbz-nrw.de:4000/v1/search?layers=address&text=Gutenbergstraße"
results in:
"geocoding": { "query": { "text": "GutenbergstraÃe",
and no hits. So there may be an encoding problem with the 'geocoding'-endpoint parsing the queries.
One has to simply url-encode the search like:
$ curl -G http://gaia.hbz-nrw.de:4000/v1/search --data-urlencode "layers=address" --data-urlencode "text=Jülicher straße 6 , 50674 Köln"
As this works as expected: closing.
Querying by using Umlaute in the
text
parameter seem to not work, thus resulting in inaccurate data. See the first test "Jülicher Straße".If this is indeed not working this could explain why there are 2k inaccurate lookups in https://github.com/hbz/lobid-organisations/issues/419.