<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2012-10-01 14:07, Oliver Tonnhofer
wrote :<br>
</div>
<blockquote
cite="mid:B48583B3-7BA5-418C-9304-F62E8A3429B2@omniscale.de"
type="cite">
<pre wrap="">On 01.10.2012, at 05:45, André Pirard wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I was using a cache that, without any res configuration created folders 16, 17, 18 and 19 which I relate to zoom levels.
To follow your method, I used
debug_source:
type: debug
This painted the following first 2 numbers, roughly at the indicated meters/JOSM scale (2.5 screen cm).
I suggest you write them to standard output (instead or in addition).
I have absolutely no idea what calculation produces those numbers.
I assumed they correspond to the former 19 and 18, I continued multiplying by 2 and I got:
19: 0.29858214: 4, 11, 22,
18: 0.59716428: 63
17: 1.19432856
16: 2.38865712
15: 4.77731424
14: 9.55462848
13: 19.10925696
12: 38.21851392
11: 76.43702784
I chose to use:
res: [76.43702784, 19.10925696, 4.77731424, 1.19432856, 0.29858214]
Now I surprised to find directories 4 and 3 instead of 19 and 17.
Why? It would have been simple.
</pre>
</blockquote>
<pre wrap="">
Because you told MapProxy to do so :)
You configured a grid with 5 levels, from level 0 at resolution 76.43702784 to level 4 at resolution 0.29858214.
</pre>
<blockquote type="cite">
<pre wrap="">Q5: is there anything to read on the Web that would help answering not only Q1-Q4 but also Q6-Q∞? :-)
</pre>
</blockquote>
<pre wrap="">
The question is: What are you trying to do and what did not work with your first configuration (without res)?
Regards,
Oliver
</pre>
</blockquote>
The practical goal is to remove some of the zoom levels directories
from the cache to minimize server requests and conserve disk space
(as the doc explains or implies, I think).<br>
In my case, the highest resolution is kept and one or two lower
levels to navigate.<br>
It's very tedious to 1) compute resolutions with debug 2) have to
rename the directories to new, unpredicted numbers and keep the
previous contents without goofing 3) experiment and loop repeating
(2) with yet different directory names each time<br>
<br>
Suggestion:<br>
<br>
Wouldn't it be possible to specify sth like res: [16:2.38865712,
19:0.29858214]<br>
to indicate to use the existing directories named 16 and 19 with
their contents and with the indicated resolution. If other names
are required, symbolic links can be automatically created. The user
shouldn't know the new numbers except for possibly erasing them.<br>
<br>
Better yet, to specify res: [16:, 19:] meaning the same except that
the original, default resolutions are kept. In other words, the
user just selects the original, default zoom levels that she/he
wants to keep and she/he can change her/his (or even his/her ;-)
mind later.<br>
<br>
In the meantime, without that comfort, it would be interesting<br>
1) to know how the default resolutions are computed: can we get them
from a server query instead of the debug method?<br>
2) said unselfishly: to learn what you said from the doc but in
terms of directory names: level 0 to 5 = what filenames if you don't
succeed creating more than 3 and 4?<br>
3) to understand how an application uses the defined levels to force
filling the right ones;<br>
in JOSM I see a) change resolution b) zoom to native resolution but
I don't relate that to file numbers.<br>
<br>
Any how it works is appreciated because it implies 20+ howtos; the
opposite is not true.<br>
<br>
Thanks,<br>
Cheers, <br>
<br>
<table>
<tbody>
<tr>
<td valign="top">André.</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>