You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some items have a P159 (headquarters location) with a nested P625, but no P625 (coordinates location).
Example: https://www.wikidata.org/wiki/Q908077
Since such items are rather numerous, we should take them into account in Nearby.
I suggest waiting until Nearby is asynchronous (load items first, then load the properties of each item) before implementing this.
Even then, a first request using P625 and a second request using P159 would be the best to avoid adding request time.
nicolas-raoul
changed the title
[far future] Also consider headquarters location (P159) in Nearby
Also consider headquarters location (P159) in Nearby
May 8, 2024
Some items have a P159 (headquarters location) with a nested P625, but no P625 (coordinates location).
Example: https://www.wikidata.org/wiki/Q908077
Since such items are rather numerous, we should take them into account in Nearby.
I suggest waiting until Nearby is asynchronous (load items first, then load the properties of each item) before implementing this.
Even then, a first request using P625 and a second request using P159 would be the best to avoid adding request time.
There is no strict consensus on whether such nested coordinates are a good idea or a bad idea, which unfortunately means we should support both:
https://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2021/03#coordinate_location_(P625)_to_headquarters_location_(P159)_switch
https://www.wikidata.org/wiki/Topic:W5d3dstxpky3z5sl
The text was updated successfully, but these errors were encountered: