Autocomplete - which whosonfirst data is taken?

openrouteservice
#1

Hi,

using the autocomplete endpoint with the parameter Luigi-Negreli-strasse from the Playground I get a response which contains whosonfirst data in german language, p.e.

“locality”: “Bozen”

If I issue the same query from a local postman running in Italy I get a response in English:

“locality”: “Botzen”

Now my question is:
According to the whosonfirst page https://github.com/whosonfirst-data/whosonfirst-data-admin-it/edit/master/data/101/751/763/101751763.geojson “Botzen” is a variant for English. Now while Botzen is an old name of the city, I would expect ORS to pick the eng_x_preferred value?

Is there a way to influence this behaviour?

Thanks!

#2

Hi @Harald_Kofler,

if i search for i don’t get any result:

curl --include \
     --header "Content-Type: application/json; charset=utf-8" \
     --header "Accept: application/json, application/geo+json, application/gpx+xml, img/png; charset=utf-8" \
  'https://api.openrouteservice.org/geocode/autocomplete?api_key=xxx&text=Luigi-Negreli-strasse'

Could you please click on the example code button in the playground and post your requests as well as the one you have done from postman without your api key?

#3

Hi @amandus,

sorry, I missspelled the address. this is the correct url:

https://api.openrouteservice.org/geocode/autocomplete?api_key=KEY&text=Luigi-Negrelli-strasse

#4

Up ;),
@amandus, may I ask you for a hint here?

Thanks

#5

Hi,
It seems the pelias API is accepting the “Accept-Language” header.
Your browser is automatically setting that (next to many others) by default making it return the german variant (Bozen):

(curl format)
--header "Accept-Language: de,en-US;q=0.7,en;q=0.3" \

If you do not send that header, it will default to engish (Botzen).

Best regards

1 Like
#6

@amandus, thanks- this fixed my issue!