The FAQ states "As such all addr:* tags (except addr:street) are ignored" which appears not to be true, addr:housenumber is searchable so it must be indexed. If both addr:street and addr:housenumber are parsed and indexed then why not addr:postcode? The performance impact of reading on more attribute when you're already inspecting the building objects should be negligible. Postcodes in the UK aren't given at a street level, two different sides of the same section of street can have different codes --GBee 20:42, 29 April 2011 (BST)
- It's also implied that postal_code will be inherited from the street but this doesn't appear to be true either, if I search by postcode only FreeThePostcode results are returned.--GBee 10:25, 30 April 2011 (BST)
How to output place_id with GEOJSON?
This link is not working as expected http://nominatim.openstreetmap.org/details.php?place_id=173891161&polygon_geojson=1
- Why do you think this should work? According to the documentation, only http://nominatim.openstreetmap.org/search and http://nominatim.openstreetmap.org/reverse support
polygon_geojson=1as a parameter. You've added that parameter to the details.php url. Mmd (talk) 11:16, 17 June 2017 (UTC)
- Let's take a step back first. Are you aware that the place_id has absolutely no relevance for OSM? It is just an internal Nominatim identifier, and it changes across Nominatim instances. So don't rely on that number. Please also take a look at the documentation . Are you doing reverse geocoding, or maybe something else? Mmd (talk) 18:01, 17 June 2017 (UTC)
Having a list on this page with all the different tags that Nomination actually uses in it's index (like Name=*) seems useful. For example, turns out that alt_name is indexed. But there doesn't seem to be an easy way to know that without finding an alt_name already in use and seeing if nomination can find it