it looks like, the wiki page explaining the idea of the map format has
been deleted. So you have to live with the short explanation:
Zoomlevel 0 covers the whole world within one single tile. If you zoom
in one step you get four tiles covering the whole world. If you zoom
in to zoom level n you get 4^n tiles. (This behaviour should be well
known from slippy maps.)
As it would be too expensive to store data for each zoom level, data
is only stored in tiles of specific zoom levels, called "base zoom
levels" (bzl). By default, data is stored in tiles of bzl 8 and bzl
14.
Example: If you want to render an image tile on zoom level 16, there
is no zoom level 16 data tile to get data from. Instead you have to
load the bzl 14 data tile, that contains the level 16 tile's data. One
bzl 14 tile contains data for 4^2 level 16 tiles (see formula above).
On the other hand you have to read several bzl tiles if you intend to
render a tile with a lower zoom level.
This becomes problematic if you zoom out very far because you have to
read O(4^n) tiles. That's why zoom intervals have been introduced. All
data within one base zoom interval is read from its base zoom level.
By having different intervals you can divide data in major and minor
road for example.
Zoom interval configurations should not impact visual results. (Thats
what the render themes and tag config files are for.) They do only
affect file sizes and loading times. Adding intervals increases the
file size but reduces loading times for zoom levels that are not base
zoom levels. The selection of base zoom level leads to bigger tile
sizes and longer loading times, but does also lead to smaller files
(the tiles are bigger, but there are lesser tiles).
I hope this helps. If something is still unclear, feel free asking.
Regards,
Karsten
2012/3/21 Sebastian Fischer <federigo....@gmail.com>:
Zoom interval configurations should not impact visual results. (Thats
what the render themes and tag config files are for.) They do only
affect file sizes and loading times.