From 69e882096c80a1bd8dd3926fb19a3b451178edbe Mon Sep 17 00:00:00 2001 From: Sarah Hoffmann Date: Tue, 29 Jul 2025 23:04:14 +0200 Subject: [PATCH] clarify what merging means --- docs/customize/Import-Styles.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/customize/Import-Styles.md b/docs/customize/Import-Styles.md index 624f8541..954f173d 100644 --- a/docs/customize/Import-Styles.md +++ b/docs/customize/Import-Styles.md @@ -125,8 +125,10 @@ value without key, then this is used as default for values that are not listed. `set_main_tags()` will completely replace the current main tag configuration with the new configuration. `modify_main_tags()` will merge the new -configuration with the existing one. Otherwise, the two functions do exactly -the same. +configuration with the existing one. Merging is done at value level. +For example, when the current setting is `highway = {'always', primary = 'named'}`, +then `set_main_tags{highway = 'delete'}` will result in a rule +`highway = {'delete', primary = 'named'}`. !!! example ``` lua @@ -143,9 +145,9 @@ the same. when it has a value of `administrative`. Objects with `highway` tags are always included with two exceptions: the troll tag `highway=no` is deleted on the spot. And when the value is `street_lamp` then the object - must have a name, too. Finally, if a `landuse` tag is present then - it will be used independently of the concrete value when neither boundary - nor highway tags were found and the object is named. + must also have a name, to be included. Finally, if a `landuse` tag is + present then it will be used independently of the concrete value when + neither boundary nor highway tags were found and the object is named. ##### Presets -- 2.39.5