There is a nice selection of features users can search for right now. But I think there is a lot more data in OSM that could in theory be leveraged and made accessible to users. It is difficult to foresee what some users will desperately need. Some examples:
emergency=defibrillator
amenity=fire_station
amenity=food_sharing
leisure=playground
amenity=bicycle_parking
amenity=drinking_water
amenity=post_box
The engine to use for translating user searched strings into meaningful OSM data types (tags and keys) - which among others returns zoo and veterinary clinic when queried for animal - could be the same one that is currently used for the "Edit" side of https://www.openstreetmap.org - i.e. when you are in edit mode there and add a new node, on the left sidebar you get asked what type of feature is this. That sidebar has a search that matches human words to OSM data types. This would initially suffice and any improvements to that could also be upstreamed to the aforementioned website. It would be convenient if that could fit a button and feature for any user feedback for missing or unmatched strings - something that should be found but isn't yet. That would then cover regional variations of the English vocabulary as well.
UI-wise there are many options where to put that and I am not very proficient in figuring this out. The end result of this UI interaction would be a way to get the desired type of node/feature displayed on the map in the same way as when the user currently clicks on the Restaurant button or after searching for and navigating to London types fire statio (without the last letter) into Qwant search.
It could be a search syntax - e.g. nearby: prefix. Thus typing nearby: animal to get suggestions nearby: veterinary clinic and nearby: zoo in the search drop down and then clicking on them. I think this solution has the disadvantage of terrible discoverability. The advantage is that this could take tag-and-key pairs from power users to search for anything that exists in OSM data - not only the ones that have human word matches (I think I've had a few types missing from Id editor during my OSM edit career).
A button in the See more services nearby menu for Custom or More or Other. Also quite hard to notice. But mostly you need it when you are intently browsing that menu anyway.
Similar to the above one, but instead of a button that looks like others, another search bar.
Similar to the above one, but instead of a new search bar, the existing one gets replaced with another in a way that is very clear to the user. (My mockup is ugly.)
There is a nice selection of features users can search for right now. But I think there is a lot more data in OSM that could in theory be leveraged and made accessible to users. It is difficult to foresee what some users will desperately need. Some examples:
emergency=defibrillator
amenity=fire_station
amenity=food_sharing
leisure=playground
amenity=bicycle_parking
amenity=drinking_water
amenity=post_box
The engine to use for translating user searched strings into meaningful OSM data types (tags and keys) - which among others returns
zoo
andveterinary clinic
when queried foranimal
- could be the same one that is currently used for the "Edit" side of https://www.openstreetmap.org - i.e. when you are in edit mode there and add a new node, on the left sidebar you get asked what type of feature is this. That sidebar has a search that matches human words to OSM data types. This would initially suffice and any improvements to that could also be upstreamed to the aforementioned website. It would be convenient if that could fit a button and feature for any user feedback for missing or unmatched strings - something that should be found but isn't yet. That would then cover regional variations of the English vocabulary as well.UI-wise there are many options where to put that and I am not very proficient in figuring this out. The end result of this UI interaction would be a way to get the desired type of node/feature displayed on the map in the same way as when the user currently clicks on the Restaurant button or after searching for and navigating to
London
typesfire statio
(without the last letter) into Qwant search.nearby:
prefix. Thus typingnearby: animal
to get suggestionsnearby: veterinary clinic
andnearby: zoo
in the search drop down and then clicking on them. I think this solution has the disadvantage of terrible discoverability. The advantage is that this could take tag-and-key pairs from power users to search for anything that exists in OSM data - not only the ones that have human word matches (I think I've had a few types missing from Id editor during my OSM edit career).