<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Am 01.11.2010 um 15:05 schrieb Yves Moisan:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#ffffff" text="#000000">Le 2010-11-01 05:58, Christoph Lingg a écrit :<blockquote cite="mid:6743E140-F4C3-400F-BCF1-3AEDE82A7BB9@lingg.eu" type="cite">Hi list,<div><br></div><div>I had a running tilecache map server and recently I updated tilecache to the newest version. Using the same tilecache.cfg as before, 50% of the tile requests are running as before, but the other half end up with an error like:</div><div><blockquote type="cite"><pre>An error occurred: Current y value 5009377.084000 is too far from tile corner y -0.000800</pre></blockquote><div>I am struggling around with this error for a couple of hours now, having tried out a lot of parameters. My configuration is very very basic:</div></div><div><br></div><div>OpenLayers:</div><div><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><span style="color: rgb(143, 13, 105); ">var</span> options = {</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><span class="Apple-tab-span" style="white-space: pre; "> </span>projection: <span style="color: rgb(143, 13, 105); ">new</span> OpenLayers.Projection(<span style="color: rgb(64, 0, 255); ">"EPSG:900913"</span>),</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><span class="Apple-tab-span" style="white-space: pre; "> </span>maxExtent: <span style="color: rgb(143, 13, 105); ">new</span> OpenLayers.Bounds(-20037508.34,-20037508.34,20037508.34,20037508.34),</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><span class="Apple-tab-span" style="white-space: pre; "> </span>resolutions: [19567.879237500001, 9783.9396187500006, 4891.9698093750003, 2445.9849046875001, 1222.9924523437501, 611.49622617187504, 305.74811308593752, 152.87405654296876, 76.43702827148438, 38.21851413574219, 19.109257067871095, 9.5546285339355475, 4.7773142669677737, 2.3886571334838869],</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><span class="Apple-tab-span" style="white-space: pre; "> </span>units: <span style="color: rgb(64, 0, 255); ">'m'</span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; ">};</div></blockquote><br></div><div>Tilecache:</div><div><div><blockquote type="cite"><div>[kmt]</div><div>type=Mapnik</div><div>mapfile=/home/christoph/render/style.xml</div><div>spherical_mercator=true</div><div>tms_type=google</div></blockquote></div></div><div><br></div><div>Has there been changed something since the last tilecache updates? I am not able to explain the origin of this error? Does anybody has a hint?</div></blockquote>Hi Christoph,<br><br>Not a hint but a related problem. I experienced the same issue a couple of weeks ago but in my case I got the ".. too far from corner ..." error messages after I updated to a newer version of OpenLayers from r10165 (2.9+) to r10848 (2.10+) with the same TC code. I can't say for sure that the change in OL version is the cause because there are other bits of code in my environment, but I have a feeling it has to do with a slightly different way of computing something that has to do with bbox. <br><br>I didn't investigate the issue past a quick SVN diff because I figured I will just dump the current cache and have it regenerated with whatever TC wants for resolutions when I'm ready to switch environments. But I am concerned that putting newer versions bring about issues like that.<br></div></blockquote><div><br></div><div>Salut Yves,</div><div><br></div><div>this is an interesting aspect, I also upgraded OpenLayers from 2.8 to 2.10. My problems occurred while using OL 2.10, but after some investigation I found out that same problems arise using OL 2.8. So I assume the problem is caused by the current tilecache version.</div><div><br></div><div>I could confirm this assumption as I replaced temporarily tilecache version 2.11 with 2.03.</div><div><br></div><div>In version 2.04 the changelog shows a change concerning the spherical mercator:</div><div><blockquote type="cite"><pre> * Minor fixes to layer initialization with regard to spherical mercator,
error logging, and others.<font class="Apple-style-span" color="#000000" face="Helvetica"><span class="Apple-style-span" style="white-space: normal; "></span></font></pre></blockquote><div><a href="http://svn.osgeo.org/tilecache/trunk/tilecache/docs/NEWS.txt">http://svn.osgeo.org/tilecache/trunk/tilecache/docs/NEWS.txt</a></div><div><br></div><div>I seems like a bug, doesn't it? Or is there somebody who knows more about that?</div><div><br></div><div>Christoph</div></div></body></html>