Sarah Hoffmann

The database version refers to the Nominatim version the current database was imported with or migrated to. It is saved in the `nominatim_properties` table. See [the migration code](https://github.com/osm-search/Nominatim/blob/2723553593f2c52ebf981d958942cc473f3db7e3/nominatim/tools/migration.py#L29) for an...

@anubhav06 Have you actually tried an implementation? Then the question will answer itself.

Thinking some more about it, the database version is better implemented in some separate command probably under the admin subcommand. Closing here for now as completed.

I've played with hourly planet diffs. The resulting files are about half the size of the original diff, which is good. Looking at the format, we need to get rid...

If you want to use libpostal with Nominatim in this way, you should replace the entire mechanism that creates interpretations of the search query. That means creating one or more...

> This test case, as it currently stands, fails. But, it does not fail for the reason I want. I am trying to get it to fail by misplacing the...

Closing this here as the whole approach from #2649 turned out to be infeasible.

Paranthesis have nothing to do with it. The first issue is easily fixed by placing strategic commas, e.g.: https://nominatim.openstreetmap.org/ui/search.html?q=21423%2C+Winsen+%28Luhe%29+Bahnhofstra%C3%9Fe+2 (For reference, the reason Nominatim is thrown off is the odd...

> Could you elaborate on the ref problem? If you don't put commas into your query, Nominatim needs to determine the word boundaries by itself. It does so by looking...

Nominatim doesn't take any entrance information into account at the moment. Tagging-wise entrance=main could probably work as long as the feature has a main entrance. There are buildings with multiple...