Sarah Hoffmann

Sorry to say but that is such a special-interest application that it is unlikely that it will ever make it into the generic search index. The only exception might be...

I had looked at the examples that have been provided in this ticket and the situation with name and ref tag is about as bad as for railways and hiking...

I would guess that the majority of users downloads the precomputed database provided by Graphhopper and rather repeat the download than reindexing the database. So I'd consider size a much...

I still doubt that the average user will do that. If you want to provide a development mode with a reindexable database, now that would be a different story. Please...

The table you refer to describes the importance ranking of places (aka rank_search). For computing the address a slightly different schema is used and there city, town, village and hamlet...

Downgrading hamlet/village would break it in lots of places because it means that now the nearest city/town _and_ village/hamlet appear in the address. Also it wouldn't fix your examples. The...

The postcode alone is not sufficient to solve the issue. The name that goes with the postcode is needed as well and should be recorded in OSM. How to do...

Postcodes are complicated. Usually there is no single object in OSM which describes a single postcode, so when Nominatim returns a postcode result, it is from the `location_postcode` tables of...

As usually with these things: the main blocker is a lack of people willing to make PRs.

This concerns the implementation of the `nominatim add-data --tiger-data`. The basic implementation can be found in[nominatim/tools/tiger_data.py](https://github.com/osm-search/Nominatim/blob/a7e048484b0f9066d1c6ba422087c2fd2c635b16/nominatim/tools/tiger_data.py#L78). However, to solve this issue, you have to dive a bit into the SQL...