Merge remote-tracking branch 'upstream/master'

[nominatim.git] / docs / develop / Ranking.md

diff --git a/docs/develop/Ranking.md b/docs/develop/Ranking.md
index 06f255004dcbc3b8cf272303da96880e3abc3c2a..5b1ca1915ca653624261278c04adffa65cbc9882 100644 (file)
--- a/docs/develop/Ranking.md
+++ b/docs/develop/Ranking.md
@@ -7,7 +7,7 @@ different purposes, which are explained in this chapter.
 ## Search rank
 
 The search rank describes the extent and importance of a place. It is used
 ## Search rank
 
 The search rank describes the extent and importance of a place. It is used

-when ranking search result. Simply put, if there are two results for a
+when ranking search results. Simply put, if there are two results for a

 search query which are otherwise equal, then the result with the _lower_
 search rank will be appear higher in the result list.
 
 search query which are otherwise equal, then the result with the _lower_
 search rank will be appear higher in the result list.
 


@@ -87,9 +87,9 @@ into the database. There are a few hard-coded rules for the assignment:
     * highway nodes
     * landuse that is not an area
 
     * highway nodes
     * landuse that is not an area
 

-Other than that, the ranks can be freely assigned via the JSON file
-defined with `CONST_Address_Level_Config` according to their type and
-the country they are in.
+Other than that, the ranks can be freely assigned via the JSON file according
+to their type and the country they are in. The name of the config file to be
+used can be changed with the setting `NOMINATIM_ADDRESS_LEVEL_CONFIG`.

 
 The address level configuration must consist of an array of configuration
 entries, each containing a tag definition and an optional country array:
 
 The address level configuration must consist of an array of configuration
 entries, each containing a tag definition and an optional country array: