Peter Johnson

Jones, the spatial service currently has 3 modes of PIP, one is called 'verbose' and I added a param called `?aliaslimit=xx` which allows us to return multiple aliases. https://spatial.demo.geocode.earth/query/pip/verbose?lon=13.392334&lat=52.509535&role=boundary&wofonly=1&aliaslimit=100

Hi @enzopolo thanks for the bug report. You're correct in saying that there is currently no support for normalising apostrophes. I've opened an issue to address that in the schema...

Actually what is said is incorrect, we do currently normalize apostrophes. The term "McDonald's" is normalized to "McDonalds", and in the example above "IX's" is normalized to "IXs". So either...

That does seem redundant, I suspect what you're seeing is multiple addresses within the same building which share the same lat/long in the source CSV. It would be a nice...

I'm not sure how easy it would be to apply some sort of query caching for these queries... If there was no parallelism it would be simple, it's still totally...

If someone is interested in looking at this, I think it could be a nice addition to https://github.com/pelias/microservice-wrapper/blob/master/service.js I suspect that either there is an existing `superagent` plugin which does...

see: https://github.com/jpodwys/superagent-cache/issues/41

Hi @bartek5186, can you confirm this is the case globally or is it only better in Poland?

The WOF dataset contains a lot of those `0,0` postcodes, I believe the WOF team leave them as placeholders for when the correct coordinates become available. Pelias should not import...

I had a quick look at this today and opened up https://github.com/whosonfirst-data/whosonfirst-data-postalcode-pl/issues/1 to discuss with the WOF team. @bartek5186 I pulled down http://www.geonames.org/export/zip/PL.zip to have a look and I'm not...