Peter Johnson

see: https://geocode.earth/docs/reference/data_layers/#dependency

@orangejulius this API extension proposal has an attached PR which I will be reviewing shortly, let me know if you see any issues with it.

Hi @NickStallman, as you mentioned the support for things more granular than a house number are not super well supported and tested in Pelias, although [there has been progress](https://github.com/pelias/schema/pull/258) made...

This might be the problem https://github.com/pelias/api/blob/master/helper/diffPlaces.js#L135

> So the unit field would have to be added to the API output, the deduplication function fixed and then all the test cases updated accordingly? Yeah I think you're...

To move this forward I'd suggest we try to merge https://github.com/pelias/openaddresses/pull/402 and make sure the unit numbers are being properly displayed in the returned `geojson`, and that there were no...

We should move forward with https://github.com/pelias/openaddresses/pull/402

Hmmm yeah that's a tricky one, I really don't like how `name.default` ends up being a catch-all for all other fields. The 'bucket-o-words' itself isn't really a problem, but ES...

Thanks @slvlirnoff, I think we can fix this fairly easily by weighting the City higher than the Canton. I believe the assumption was that if a record was associated to...

In particular I would expect this result to rank highly for that query: ```javascript "properties": { "id": "polyline:6996267", "gid": "openstreetmap:street:polyline:6996267", "layer": "street", "source": "openstreetmap", "source_id": "polyline:6996267", "name": "Huttenstrasse", "street": "Huttenstrasse",...