[Geocoding] [OpenStreetMap] #5379: Reverse geocoding ignores osm_type and won't return the closest Way

[OpenStreetMap]

#5379: Reverse geocoding ignores osm_type and won't return the closest Way
------------------------+-------------------------
  Reporter:  capellsk   |      Owner:  geocoding@…
      Type:  defect     |     Status:  closed
  Priority:  minor      |  Milestone:
 Component:  nominatim  |    Version:
Resolution:  invalid    |   Keywords:
------------------------+-------------------------

Comment (by capellsk):

 Okay, as soon as wiki account creation gets fixed (it's broken) I will
 remove the line where it says you can use osm_type with reverse.

 Your comment, lonvia, about the zoom level indicates that perhaps the zoom
 levels have semantic meaning in addition to scale (ie, zoom of 18 will
 produce a "building" and 17 a "street"). The OSM wiki page mostly talks
 about scale, with a little semantics mixed in:

 http://wiki.openstreetmap.org/wiki/Zoom_levels

 Here is what I get using that same query with different zooms:
 18+ - restaurant (node)
 17 - footway (way)
 16 - same
 15 - suburb (node)
 14 - same
 13 - same
 12 - same
 11 - city (relation)
 10 - same
 9 - county (relation)
 8 - same
 7 - state_district (relation)
 6 - same
 5 - state (relation)
 4 - country (relation)
 3 - same
 2 - same
 1 - same
 0 - same

 Oddly, OSM has 0-19 and Nominatim has 0-18 (according to the wiki).

 So does Nominatim (or OSM) use the zoom levels in a semantically
 consistent way? For example, will zoom 10 or 11 always give the city, or
 could a city show up at any zoom level depending on its size?

--
Ticket URL: <https://trac.openstreetmap.org/ticket/5379#comment:2>
OpenStreetMap <http://www.openstreetmap.org/>
OpenStreetMap is a free editable map of the whole world