Linked place names need to include the default language #2714
Labels
Comments
|
See Nominatim/lib-sql/functions/placex_triggers.sql Line 1034 in 5751686 Note: if you want to pick this up as a 'good first issue', please start with creating a BDD test that reproduces the example from the issue and create a PR with the test (which should still be failing at this point). Start with the following test as a blueprint: Nominatim/test/bdd/db/import/linking.feature Line 294 in 157414a |
asharmalik19
added a commit
to asharmalik19/Nominatim
that referenced
this issue
Mar 27, 2025
Add failing test for issue osm-search#2714 to verify default language expansion
asharmalik19
added a commit
to asharmalik19/Nominatim
that referenced
this issue
Mar 28, 2025
Add failing test for issue osm-search#2714 to verify default language expansion
asharmalik19
added a commit
to asharmalik19/Nominatim
that referenced
this issue
Apr 3, 2025
Add failing test for issue osm-search#2714 to verify default language expansion
This comment has been minimized.
This comment has been minimized.
This was referenced Apr 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:enwhile for Spanish speakers thename:esis preferred. From the_place_name, the additional_place_name:es(the default language of Colombia) needs to be inferred.The text was updated successfully, but these errors were encountered: