Peter Johnson

@razafinr I've made some changes to `pbf2json` which will allow us to be more specific when targeting tags from the OSM extracts, eg. you can now say `amenity~toilets,amenity~kindergarten` or whatever...

@razafinr it's also worth noting that street addresses are currently being extracted from `addr:street` and `addr:housenumber` tags, so if the query logic is correct then we should be able to...

I've kicked off a full planet build @additional-name-fields-2022-04-01-55f13ca329927bcfa31a576504b9920801ee9046

Hi @CatInCosmicSpace, that sounds like a nice addition, the core team are currently working on other features at the moment but I'd be happy to review and merge a PR...

this looks promising, grepping the fixture file shows that *all* name fields now only contain a single entry

Another solution is to simply modify https://github.com/pelias/openstreetmap/blob/master/config/features.js to suit your needs. If you are using Docker, then you can achieve this *without* modifying the docker image using a feature called...

Here's an example of how to use bind-mounts in `docker-compose` to override the file stored inside the container with one from your local machine: https://github.com/pelias/docker/blob/master/projects/portland-metro/docker-compose.yml#L17

ref: https://mapzen.com/documentation/search/autocomplete/#user-experience-guidelines

I'm actually considering dropping `highway:bus_stop+name` too, it produces weird labels, like this one from nominatim:

removed [highway:bus_stop](https://taginfo.openstreetmap.org/tags/highway=bus_stop#overview) and [railway:tram_stop](https://taginfo.openstreetmap.org/tags/railway=tram_stop#overview), these smaller local stops generally don't have a unique name.