summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authormvglasow <michael -at- vonglasow.com>2019-07-26 00:32:58 +0200
committermvglasow <michael -at- vonglasow.com>2019-07-26 00:32:58 +0200
commit8aa190c6dc548cc7101c1d2d7b11469a27463f76 (patch)
tree8433b683017232cd3aa09b208abb09bc54ab064a /docs
parentb6c0c8685f802091e2c37d88960266137d0fb6f2 (diff)
downloadnavit-8aa190c6dc548cc7101c1d2d7b11469a27463f76.tar.gz
update:doc:How an object is placed in a tile
Signed-off-by: mvglasow <michael -at- vonglasow.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/binfile.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/binfile.rst b/docs/binfile.rst
index 572ebbe19..e4489e381 100644
--- a/docs/binfile.rst
+++ b/docs/binfile.rst
@@ -114,7 +114,7 @@ An object 'fits' inside of a tile if the coordinates of the object (min lat, min
Any object that cross the equator or the poles is placed in the top-most tile because it can not fit inside of any sub-tile.
-Some important objects are placed into upper level tiles despite of their length to be easier reachable for routing or display purposes. This is done by specifying maximum tile name length for them in phase34_process_file() function in `navit/maptool/misc.c`__.
+Some important objects are placed into upper level tiles despite of their length to be easier reachable for routing or display purposes. This is done by specifying maximum tile name length for them in item_order_by_type() function in `navit/maptool/misc.c`__.
BTW, "order" (zoom level) values used to query map and referred in <itemgra> and route_depth are equal to (tile_name_length-4).