On Wed, Sep 1, 2010 at 12:16 PM, Eric Wolf <span dir="ltr"><<a href="mailto:ebwolf@gmail.com">ebwolf@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Yep. It's GoogleDisk, so the directory structure follows /layer/z/x/y.png.<br><br></blockquote><div>I took a look at GoogleDisk.py and it looks like it is indeed "unflipping" for tms_type=google, so that theory is thrown out.</div>
<div><br></div><div>However, I think the logging still uses "real" TMS values when writing out, so take a look at what images are actually being requested from the server (in the browser).</div><div><br></div><div>
I'm envisioning something like this:</div><div><br></div><div><font class="Apple-style-span" face="'courier new', monospace">Browser > TileCache Request Log > GoogleDisk</font></div><div><font class="Apple-style-span" face="'courier new', monospace">y=25347 y=40188 y=25347</font></div>
<div><br></div><div>I'm running dry on ideas :)</div><div><br></div><div>... Hmm, this might make sense because at zoom z there are 2^z tiles in each column or row. 2^16=65536 and 25347+40188=65536. My bet is that if you expose these images directly to a Google Maps API or similarly-set-up OpenLayers system you would end up with a valid map.</div>
</div>