osm-search/Nominatim
1
1
Fork 0
mirror of https://github.com/osm-search/Nominatim.git synced 2024-11-22 21:28:10 +03:00
Code Issues Packages Projects Releases Wiki Activity
67e1c7dc72
Nominatim/settings/address-levels.json

227 lines
5.1 KiB
JSON
Raw Normal View History

Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
[
{ "tags" : {
"place" : {
"sea" : [2, 0],
change place node expansion for large area table So far we've used a buffer around a place node to define its potential address reach. This had two problems: the buffer was so large that addresses often contain false positives and the buffer is really distorted when getting closer to the poles. Change the buffer here to draw a bounndig box at a certain distance in meter. This means that we always use the same box everywhere on the planet and can make the extent much smaller. Using a box has the advantage that it is much faster to figure out if a point is within the box.
2020-05-06 23:22:24 +03:00
"island" : [17, 0],
"islet" : [20, 0],
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
"continent" : [2, 0],
generally remove all country and state places from address Gets rid of the hard-coded expection for place nodes and sets the address rank generally via the address level config instead. That means only administrative boundaries are now used at that level in addresses.
2019-06-20 00:16:43 +03:00
"country" : [4, 0],
"state" : [8, 0],
update place address levels Adds province and allotments and downgrades hamlet.
2020-01-09 00:44:56 +03:00
"province" : [8, 0],
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
"region" : [18, 0],
"county" : 12,
reorganize ranks of high-level place types Rank 25 is now available for places that should appear in addresses but not when a street is present. Use this for som block-like place types. Also document the particularity of rank 25. subdevisions and allotments are now at the same level as landuse which they are frequently used together with.
2020-10-20 21:20:49 +03:00
"district" : 12,
adapt tests to new search ranks
2020-05-30 12:50:04 +03:00
"municipality" : 14,
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
"city" : 16,
"town" : [18, 16],
change place node expansion for large area table So far we've used a buffer around a place node to define its potential address reach. This had two problems: the buffer was so large that addresses often contain false positives and the buffer is really distorted when getting closer to the poles. Change the buffer here to draw a bounndig box at a certain distance in meter. This means that we always use the same box everywhere on the planet and can make the extent much smaller. Using a box has the advantage that it is much faster to figure out if a point is within the box.
2020-05-06 23:22:24 +03:00
"borough" : 18,
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
"village" : [19, 16],
change place node expansion for large area table So far we've used a buffer around a place node to define its potential address reach. This had two problems: the buffer was so large that addresses often contain false positives and the buffer is really distorted when getting closer to the poles. Change the buffer here to draw a bounndig box at a certain distance in meter. This means that we always use the same box everywhere on the planet and can make the extent much smaller. Using a box has the advantage that it is much faster to figure out if a point is within the box.
2020-05-06 23:22:24 +03:00
"suburb" : [19, 20],
update place address levels Adds province and allotments and downgrades hamlet.
2020-01-09 00:44:56 +03:00
"hamlet" : 20,
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
"croft" : 20,
reorganize ranks of high-level place types Rank 25 is now available for places that should appear in addresses but not when a street is present. Use this for som block-like place types. Also document the particularity of rank 25. subdevisions and allotments are now at the same level as landuse which they are frequently used together with.
2020-10-20 21:20:49 +03:00
"subdivision" : 22,
"allotments" : 22,
change place node expansion for large area table So far we've used a buffer around a place node to define its potential address reach. This had two problems: the buffer was so large that addresses often contain false positives and the buffer is really distorted when getting closer to the poles. Change the buffer here to draw a bounndig box at a certain distance in meter. This means that we always use the same box everywhere on the planet and can make the extent much smaller. Using a box has the advantage that it is much faster to figure out if a point is within the box.
2020-05-06 23:22:24 +03:00
"neighbourhood" : [20, 22],
"quarter" : [20, 22],
"isolated_dwelling" : [22, 20],
reorganize ranks of high-level place types Rank 25 is now available for places that should appear in addresses but not when a street is present. Use this for som block-like place types. Also document the particularity of rank 25. subdevisions and allotments are now at the same level as landuse which they are frequently used together with.
2020-10-20 21:20:49 +03:00
"farm" : [22, 20],
"city_block" : 25,
"mountain_pass" : 25,
add support for place=square Squares are now addressable (on address level 25) and thus can be attached to a house number via addr:place. Needed to increase the rank range for matching up addr:place to 25.
2020-08-26 13:12:52 +03:00
"square" : 25,
reorganize ranks of high-level place types Rank 25 is now available for places that should appear in addresses but not when a street is present. Use this for som block-like place types. Also document the particularity of rank 25. subdevisions and allotments are now at the same level as landuse which they are frequently used together with.
2020-10-20 21:20:49 +03:00
"locality" : 25,
change place node expansion for large area table So far we've used a buffer around a place node to define its potential address reach. This had two problems: the buffer was so large that addresses often contain false positives and the buffer is really distorted when getting closer to the poles. Change the buffer here to draw a bounndig box at a certain distance in meter. This means that we always use the same box everywhere on the planet and can make the extent much smaller. Using a box has the advantage that it is much faster to figure out if a point is within the box.
2020-05-06 23:22:24 +03:00
"houses" : [28, 0],
improve fallback ranking Boundaries and places now always get a rank < 26 to make sure that they do not parent to a street. Skip boundary=place completely because they will be covered throught the secondary place tag.
2020-09-01 18:55:40 +03:00
"house" : 30,
"" : [22, 0]
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
},
"boundary" : {
"administrative2" : 4,
"administrative3" : 6,
"administrative4" : 8,
"administrative5" : 10,
"administrative6" : 12,
"administrative7" : 14,
"administrative8" : 16,
"administrative9" : 18,
"administrative10" : 20,
"administrative11" : 22,
improve fallback ranking Boundaries and places now always get a rank < 26 to make sure that they do not parent to a street. Skip boundary=place completely because they will be covered throught the secondary place tag.
2020-09-01 18:55:40 +03:00
"administrative12" : 24,
"" : [25, 0]
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
},
"landuse" : {
"residential" : 22,
"farm" : 22,
"farmyard" : 22,
"industrial" : 22,
"commercial" : 22,
"allotments" : 22,
"retail" : 22,
"" : [22, 0]
},
"leisure" : {
"park" : [24, 0]
},
"natural" : {
"peak" : [18, 0],
"volcano" : [18, 0],
"mountain_range" : [18, 0],
elevate most natural feature to address rank 22 Makes them be in par with landuse features.
2020-10-23 13:58:13 +03:00
"sea" : [4, 0],
"tree" : 30,
"spring" : 30,
"cave_entrance" : 30,
"geyser" : 30,
"hot_spring" : 30,
"rock" : 30,
"stone" : 30,
"" : [22, 0]
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
},
"waterway" : {
downgrade waterways A lot of streams in OSM are of minor importance, they certainly should show up lower in the list of results than villages. Those rivers/streams that are well known have a wikipedia page and get a higher importance from that. The disadvantage with downgrading is that the address gets even more useless but that's something that needs to be solved outside the rank search.
2020-04-14 18:14:20 +03:00
"river" : [19, 0],
"stream" : [22, 0],
"ditch" : [22, 0],
"drain" : [22, 0],
"" : [20, 0]
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
},
"highway" : {
change default rank for highway objects to 30 The highway key is being used more and more for non-ways these days. This clashes with Nominatim's assumption that essentially everything that has a highway tag can be used as the street part of the address. Change the default rank of highway objects to 30 to avoid this. Only the known values for streets keep the rank 26 and are now listed explicitly.
2021-11-24 16:40:23 +03:00
"" : 30,
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
"service" : 27,
"cycleway" : 27,
"path" : 27,
"footway" : 27,
"steps" : 27,
"bridleway" : 27,
"motorway_link" : 27,
"primary_link" : 27,
"trunk_link" : 27,
"secondary_link" : 27,
change default rank for highway objects to 30 The highway key is being used more and more for non-ways these days. This clashes with Nominatim's assumption that essentially everything that has a highway tag can be used as the street part of the address. Change the default rank of highway objects to 30 to avoid this. Only the known values for streets keep the rank 26 and are now listed explicitly.
2021-11-24 16:40:23 +03:00
"tertiary_link" : 27,
"residential" : 26,
"track" : 26,
"unclassified" : 26,
"tertiary" : 26,
"secondary" : 26,
"primary" : 26,
"living_street" : 26,
"trunk" : 26,
"motorway" : 26,
"pedestrian" : 26,
"road" : 26,
"construction" : 26
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
},
"mountain_pass" : {
"" : [20, 0]
remove historic:neighbourhood from address ranks Should not be reverse searchable. Fixes #1379.
2019-06-10 21:12:27 +03:00
},
"historic" : {
improve fallback ranking Boundaries and places now always get a rank < 26 to make sure that they do not parent to a street. Skip boundary=place completely because they will be covered throught the secondary place tag.
2020-09-01 18:55:40 +03:00
"neighbourhood" : [22, 0]
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
}
}
Remove county places and Regierungsbezirke vom German addresses
2019-06-20 00:19:52 +03:00
},
remove county nodes in Canada from addresses Canada has complete coverage for administrative boundaries on county level. Removing the county nodes from the addresses avoids error due to a wide-spread doubling of place nodes for city counties.
2022-05-18 11:19:05 +03:00
{ "countries" : [ "ca" ],
"tags" : {
"place" : {
"county" : [12, 0]
}
}
},
Remove county places and Regierungsbezirke vom German addresses
2019-06-20 00:19:52 +03:00
{ "countries" : [ "de" ],
"tags" : {
"place" : {
adapt municipality and region for Germany
2020-04-05 17:15:55 +03:00
"region" : [10, 0],
fix admin levels for Norway and Sweden Admin levels 3 and 4 are used for region and county respectively, so downgrade the ranking.
2020-04-25 23:53:35 +03:00
"county" : [12, 0]
Remove county places and Regierungsbezirke vom German addresses
2019-06-20 00:19:52 +03:00
},
"boundary" : {
"administrative5" : [10, 0]
}
}
Remove administrative arrondissements from Belgian addresses "administrative7" -> [14, 0]
2019-08-27 15:15:18 +03:00
},
{ "countries" : [ "be" ],
"tags" : {
"boundary" : {
adapt admin_levels for Belgium Fixes #272.
2020-11-03 12:46:52 +03:00
"administrative3" : [5, 0],
"administrative4" : 6,
"administrative5" : [7, 0],
"administrative6" : 8,
"administrative7" : 12,
"administrative8" : 14,
"administrative9" : 16,
"administrative10" : 18
Remove administrative arrondissements from Belgian addresses "administrative7" -> [14, 0]
2019-08-27 15:15:18 +03:00
}
}
fix admin levels for Norway and Sweden Admin levels 3 and 4 are used for region and county respectively, so downgrade the ranking.
2020-04-25 23:53:35 +03:00
},
{ "countries" : ["se", "no"],
"tags" : {
"place" : {
},
"boundary" : {
"administrative3" : 8,
"administrative4" : 12
}
}
adapt address levels for admin boundaries in Indonesia
2020-10-09 23:28:06 +03:00
},
{ "countries" : ["id"],
"tags" : {
"place" : {
"municipality" : 18
},
"boundary" : {
"administrative5" : 12,
"administrative6" : 14,
"administrative7" : 16,
"administrative8" : 20,
"administrative9" : 22,
"administrative10" : 24
}
}
add country-specific address ranks for Russia Removes admin level 7, which should not exist and promotes admin level 8 to municipality level. place=municipality is only used for boroughs of St. Petersburg, so demote to level 18. Fixes #926.
2020-10-17 18:54:06 +03:00
},
{ "countries" : ["ru"],
"tags" : {
"place" : {
"municipality" : 18
},
"boundary" : {
disable admin level 5 in Russia They either interfere with cities or refer to historical boundaries.
2020-10-26 22:17:28 +03:00
"administrative5" : [10, 0],
add country-specific address ranks for Russia Removes admin level 7, which should not exist and promotes admin level 8 to municipality level. place=municipality is only used for boroughs of St. Petersburg, so demote to level 18. Fixes #926.
2020-10-17 18:54:06 +03:00
"administrative7" : [13, 0],
"administrative8" : 14
}
}
Admin levels 8 and 10 of the Netherlands are municipal / city
2020-11-18 13:30:24 +03:00
},
{ "countries" : [ "nl" ],
"tags" : {
"boundary" : {
make sure that admin levels in NL are kept in order
2020-11-19 11:44:02 +03:00
"administrative7" : [13, 0],
Admin levels 8 and 10 of the Netherlands are municipal / city
2020-11-18 13:30:24 +03:00
"administrative8" : 14,
make sure that admin levels in NL are kept in order
2020-11-19 11:44:02 +03:00
"administrative9" : [15, 0],
Admin levels 8 and 10 of the Netherlands are municipal / city
2020-11-18 13:30:24 +03:00
"administrative10" : 16
}
}
adjust address ranks for Spain Adjusts levels for boundaries according to the list on https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative * no admin_level 5, so drop that from addresses * admin_level 6 has the province * admin_level 7 has the county when it exists Also reranks place=province so that it matches up with admin_level 6 and introduces place=civil_parish which is used as a place node for some admin_level=9 boundaries in Galicia.
2021-09-24 18:37:31 +03:00
},
{ "countries" : ["es"],
"tags" : {
"place" : {
"province" : 10,
"civil_parish" : 18
},
"boundary" : {
"administrative5" : [10, 0],
"administrative6" : 10,
"administrative7" : 12,
"administrative10" : 22
}
}
adjust address levels for boundaries in Slovakia Levels choosen according to OSM wiki. Mainly moves admin_level 6 to county level and admin_level 8 to city/town level. Higher levels are adjusted accordingly. Fixes #2453.
2021-09-28 00:32:11 +03:00
},
{ "countries" : ["sk"],
"tags" : {
"boundary" : {
"administrative5" : [10, 0],
"administrative6" : 11,
"administrative7" : [11, 0],
"administrative8" : 12,
"administrative9" : 16,
"administrative10" : 18,
"administrative11" : 20
}
}
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
}
adjust address levels for boundaries in Slovakia Levels choosen according to OSM wiki. Mainly moves admin_level 6 to county level and admin_level 8 to city/town level. Higher levels are adjusted accordingly. Fixes #2453.
2021-09-28 00:32:11 +03:00
Make rank assignments configurable The initial search and address rank is saved in a table that is set up from a json configuration file. Ranks may be assigned on a country level according to class and type of the object. Special handling that depends on the geometry or OSM type is still hard-coded in placex insert. The new default config file mimicks the current assignment as close as possible. A couple of exceptions have been removed, most notably the exception for Irish townlands.
2018-11-24 01:02:32 +03:00
]
Reference in New Issue Copy Permalink