Peter Johnson

``` head PL.txt PL 00-001 Warszawa Mazowieckie Warszawa 52.25 21 4 PL 00-002 Warszawa Mazowieckie Warszawa 52.25 21 4 PL 00-003 Warszawa Mazowieckie Warszawa 52.25 21 4 PL 00-004 Warszawa...

Which is the official source that geonames uses? You might be better off just using the [csv-importer](https://github.com/pelias/csv-importer) to import those files directly. We've found the Geonames postcodes files to be...

Hi @bartek5186 I had a quick look at the issue you reported and I wasn't able to reproduce the error where the `source` you provide is not the same as...

there are some interactive examples in the CORS documentation: https://github.com/pelias/documentation/blob/master/use-cors.md the leaflet geocoder plugin will only work with a leaflet map.

The interactive demos are pointing to `search.mapzen.com` which is no longer operational, so you'll need to change that to point to your Pelias server.

List of the `4337` HSTS rows: https://gist.github.com/missinglink/5c5ad2fd5a82860c82967edd380e17f0 Of the total of `12,214,535` rows globally they represent `0.035%`

Ooh transferring issues between repos... fancy!

Oh yeah, that must be super confusing to new developers. Although i don't think these all refer to the same thing. `integration` tests call `elasticsearch` and test how the js...

FYI this is already possible using the spatial service, there is a [backwards-compatible API](https://spatial.synergy.io/query/pip/_view/pelias/13.427/52.530) as well as one which [also includes OSM boundaries](https://spatial.synergy.io/query/pip?lon=13.427&lat=52.530).

I am hoping we can support multiple querying methods for the spatial service, the main two being: - query allthethings - query for the lowest match and walk the hierarchy