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

docs: fix more links

Browse Source
This commit is contained in:
Sarah Hoffmann
2021-10-18 17:26:14 +02:00
parent 632436d54d
commit 2635fe8b4c
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/admin/Import.md
View File

@@ -96,7 +96,7 @@ This data can be optionally downloaded into the project directory:
wget https://www.nominatim.org/data/us_postcodes.csv.gz wget https://www.nominatim.org/data/us_postcodes.csv.gz
You can also add your own custom postcode sources, see You can also add your own custom postcode sources, see
[Customization of postcodes](Customization.md#external-postcode-data). [Customization of postcodes](../customize/Postcodes.md).
## Choosing the data to import ## Choosing the data to import

2
docs/customize/Special-Phrases.md
View File

@@ -2,7 +2,7 @@
## Importing OSM user-maintained special phrases ## Importing OSM user-maintained special phrases
As described in the [Import section](Import.md), it is possible to As described in the [Import section](../admin/Import.md), it is possible to
import special phrases from the wiki with the following command: import special phrases from the wiki with the following command:
```sh ```sh

2
docs/customize/Tokenizers.md
View File

@@ -37,7 +37,7 @@ NOMINATIM_DATABASE_MODULE_PATH=<path to directory where nominatim.so resides>
``` ```
This is in particular useful when the database runs on a different server. This is in particular useful when the database runs on a different server.
See [Advanced installations](Advanced-Installations.md#importing-nominatim-to-an-external-postgresql-database) for details. See [Advanced installations](../admin/Advanced-Installations.md#importing-nominatim-to-an-external-postgresql-database) for details.
There are no other configuration options for the legacy tokenizer. All There are no other configuration options for the legacy tokenizer. All
normalization functions are hard-coded. normalization functions are hard-coded.

2
docs/develop/Tokenizers.md
View File

@@ -6,7 +6,7 @@ tokenizers that use different strategies for normalisation. This page describes
how tokenizers are expected to work and the public API that needs to be how tokenizers are expected to work and the public API that needs to be
implemented when creating a new tokenizer. For information on how to configure implemented when creating a new tokenizer. For information on how to configure
a specific tokenizer for a database see the a specific tokenizer for a database see the
[tokenizer chapter in the administration guide](../admin/Tokenizers.md). [tokenizer chapter in the Customization Guide](../customize/Tokenizers.md).
## Generic Architecture ## Generic Architecture