hans/Nominatim
1
0
Fork 1
mirror of https://github.com/osm-search/Nominatim.git synced 2026-03-11 21:34:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3800 from lonvia/improve-style-docs

Browse Source 
Improvements to documentation for custom import styles
This commit is contained in:
Sarah Hoffmann
2025-07-30 14:50:17 +02:00
committed by GitHub
parent 194b607491 69e882096c
commit 64bb8c2a9c
1 changed files with 20 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
docs/customize/Import-Styles.md
View File

@@ -36,18 +36,27 @@ local flex = require('flex-base')
### Using preset configurations ### Using preset configurations
If you want to start with one of the existing presets, then you can import If you want to start with one of the existing presets, then you can import
its settings using the `import_topic()` function: its settings using the `load_topic()` function:
``` ``` lua
local flex = require('flex-base') local flex = require('flex-base')
flex.import_topic('streets') flex.load_topic('streets')
``` ```
The `import_topic` function takes an optional second configuration The `load_topic` function takes an optional second configuration
parameter. The available options are explained in the parameter. The available options are explained in the
[themepark section](#using-osm2pgsql-themepark). [themepark section](#using-osm2pgsql-themepark).
Available topics are: `admin`, `street`, `address`, `full`. These topic
correspond to the [import styles](../admin/Import.md#filtering-imported-data)
you can choose during import. To start with the 'extratags' style, use the
`full` topic with the appropriate config parameter:
``` lua
flex.load_topic('full', {with_extratags = true})
```
!!! note !!! note
You can also directly import the preset style files, e.g. You can also directly import the preset style files, e.g.
`local flex = require('import-street')`. It is not possible to `local flex = require('import-street')`. It is not possible to
@@ -116,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 `set_main_tags()` will completely replace the current main tag configuration
with the new configuration. `modify_main_tags()` will merge the new with the new configuration. `modify_main_tags()` will merge the new
configuration with the existing one. Otherwise, the two functions do exactly configuration with the existing one. Merging is done at value level.
the same. 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 !!! example
``` lua ``` lua
@@ -134,9 +145,9 @@ the same.
when it has a value of `administrative`. Objects with `highway` tags are when it has a value of `administrative`. Objects with `highway` tags are
always included with two exceptions: the troll tag `highway=no` is 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 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 must also have a name, to be included. Finally, if a `landuse` tag is
it will be used independently of the concrete value when neither boundary present then it will be used independently of the concrete value when
nor highway tags were found and the object is named. neither boundary nor highway tags were found and the object is named.
##### Presets ##### Presets