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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: dan[at]karran.net [Submitted to the original trac issue database at 10.06pm, Thursday, 30th April 2009]
It would be great if the names of nearby places (e.g. nearest village(s), town(s), city(ies)) could be added to history browser pages, giving both users and search engines a better idea of where objects are located.
nodes: should be a relatively simple call to the namefinder service, but could overload it due to the volume of requests
ways, relations: could search for places within the bbox and display the biggest places, or the places near the way/relation
changesets: find the places that fall within the bbox
These suggestions perhaps only really work for objects that fit within a small BBOX, as listing places that fall within a big BBOX (or along a long way/relation) may not be as useful in most situations.
The text was updated successfully, but these errors were encountered:
Reporter: dan[at]karran.net
[Submitted to the original trac issue database at 10.06pm, Thursday, 30th April 2009]
It would be great if the names of nearby places (e.g. nearest village(s), town(s), city(ies)) could be added to history browser pages, giving both users and search engines a better idea of where objects are located.
These suggestions perhaps only really work for objects that fit within a small BBOX, as listing places that fall within a big BBOX (or along a long way/relation) may not be as useful in most situations.
The text was updated successfully, but these errors were encountered: