support for mapping tags to name.default aliases #435
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this PR allows OSM tags to be mapped as aliases of the
name.default
field.the
schema/name_osm.js
file contains a mapping of OSM tags toname.*
fields.prior to this PR we were only able to map 1:1 from OSM to the Pelias model.
this PR now supports multiple values in that object set as
default
, in this case the additional tags will be mapped as aliases of thename.default
field.the configuration also adds an additional inenumerable property called
_primary
which defines which of those is considered the 'primary' name.an example tag mapping:
I enabled 3 tags as aliases of default:
[ short_name, alt_name, loc_name ]
, of these onlyshort_name
is supported by nominatim.https://wiki.openstreetmap.org/wiki/Names#Key_Variations
The test/fixtures/combined_vancouver_queens.json file in this PR includes a diff which shows and example of the expected changes.