-
-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecating gazetteer output #1311
Comments
Having Nominatim use the flex output, would open up the possibility of generating a single database for rendering and geocoding. Something that a lot of people want. At a minimum this would need some mechanism for handling the difference in processing though: For the rendering db osm2pgsql needs to handle the forward dependencies in append mode, Nominatim doesn't need that. |
With the merge of #1847 another big step towards this has been taken. See also https://nominatim.org/2022/11/28/towards-flex.html . |
Handling of forward dependencies has been rendered moot by osm-search/Nominatim#2927. The one task that remains is to remove the gazetteer output. I don't think we need much of a deprecation period as the output was only ever meant to be used with Nominatim. |
Closing in favour of #1870. |
With the flex output, there is no need to have a separate gazetteer output, as it allows to configure most of what we need. This tickets collects the features that would still be needed on the osm2pgsql side to get the flex output on par with the current gazetteer implementation:
add_row()
twice for the same object.Disable handling of forward dependencies on a per-table base.The tasks for the Nominatim side are collected at osm-search/Nominatim#2047.
The text was updated successfully, but these errors were encountered: