Markus Schlotbohm

Debug level 3 output: ```json { "geocoding": { "version": "0.2", "attribution": "http://127.0.0.1:8888/attribution", "query": { "enableDebug": true, "exposeInternalDebugTools": true, "enableElasticDebug": true, "enableElasticExplain": true, "text": "Saturnstraße Willich", "parser": "pelias", "parsed_text": { "subject":...

To reproduce run pelias with the configuration of the project `projects\germany` in the `pelias\docker` repo.

@orangejulius @missinglink Ok, I found the issue. By passing `layers=coarse,address,venue,neighbourhood,locality,localadmin,county,macrocounty,region,borough,country` as query parameter the results are the same between pelias.github.io/compare and a self deployed instance. So the question is, why...

Thanks @missinglink - We are using the latest builds - The results of `pelias elastic stats` seem reasonable: ```json { "took" : 3359, "timed_out" : false, "_shards" : { "total"...

Won't running `pelias prepare all` prepare also the polylines from the osm data set?

Oh ok, after checking the `docker_extract.sh` script in [pelias/polylines](https://github.com/pelias/polylines/blob/master/docker_extract.sh) I recognized that the script exits if the `pbf` file is greater than 1GB. This however is not obvious from the...

I've gone ahead and updated the warning message in the [pelias/polylines#259](https://github.com/pelias/polylines/pull/259) repo. I also figured out that in the `pelias.json` config file under `imports.polyline.files` an array of files is expected,...

That looks good. Let's add at least a warning if more than one file is specified in the `pelias.json` config file for now. Maybe this warning could be removed in...

Having the same issue: [`Am Nordkanal 8, 47877 Willich, Deutschland`](https://pelias.github.io/compare/#/v1/autocomplete?lang=de&text=Am+Nordkanal+8%2C+47877+Willich%2C+Deutschland) Looking forward for a fix 👍🏽