Skip to content
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

Linked place names need to include the default language #2714

Open
lonvia opened this issue May 19, 2022 · 1 comment
Open

Linked place names need to include the default language #2714

lonvia opened this issue May 19, 2022 · 1 comment

Comments

@lonvia
Copy link
Member

lonvia commented May 19, 2022

If a place is linked to a boundary and has different names, these names are added to the boundary. However, Nominatim doesn't do the expansion to the default language of the country there.

Example: the boundary of Popayan gets linked to the town node. The boundary only has an ugly descriptive name while the node has the proper town name. English speakers get the _place_name:en while for Spanish speakers the name:es is preferred. From the _place_name, the additional _place_name:es (the default language of Colombia) needs to be inferred.

@lonvia
Copy link
Member Author

lonvia commented May 6, 2023

See

NEW.name := add_default_place_name(NEW.country_code, NEW.name);
to learn where local names are added. See
SELECT hstore(array_agg('_place_' || key), array_agg(value)) INTO extra_names
for where the place names from the linked place are linked in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant