Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using Wikipedia article names as final backup #2969

Closed
matkoniecz opened this issue Feb 5, 2023 · 1 comment
Closed

Consider using Wikipedia article names as final backup #2969

matkoniecz opened this issue Feb 5, 2023 · 1 comment

Comments

@matkoniecz
Copy link
Contributor

What did you search for?

https://nominatim.openstreetmap.org/ui/search.html?q=Pi%C5%82sudski%27s+Mound
https://nominatim.openstreetmap.org/search.php?q=Pi%C5%82sudski%27s+Mound&format=jsonv2&debug=1

What result did you get?

No search results found

What result did you expect?

https://www.openstreetmap.org/node/274386820

Further details

https://en.wikipedia.org/wiki/Pi%C5%82sudski%27s_Mound is indirectly linked via wikipedia and wikidata tags

I searched for similar issues and have not found anything, hopefully I have not missed anything this time.

Note: I am not 100% sure is there some licensing complication, I admit that I have not researched this aspect situation strongly enough to be sure.

@lonvia
Copy link
Member

lonvia commented Feb 6, 2023

This is not going to happen at least not on the official instance. Nominatim is explicitly there for searching in OSM data. Adding Wikipedia names would just cause confusion.

We do need to do something in terms of translated category terms, see my thoughts on that in #2944. However, I don't think that any solution there will ever cover this particular case because 'mound' wouldn't really be covered by natural=peak (among other things, there is nothing natural about it). historic=monument would need a subtag that describes the 'mound type'. But this is a tagging discussion that does not belong here.

@lonvia lonvia closed this as not planned Won't fix, can't repro, duplicate, stale Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants