Talk:Dstile howto

Things that need clarification Withak 16:09, 11 Aug 2006 (UTC)
 * indexed images
 * terrain formats and how to add your terrain in WW after processing
 * should the bounding box in the xml be something other that (-180,90) (180,-90)?
 * Such 'worldwide' bbox would make WW issue tons of tile-requests, most ending with nnnn_nnnn.jpg.txt-like entries in the cache. Your example layer will better fit into W=-76, E=-75, S=39, N=40 bounding box. Then WW will search for imagery only in the proper area and its closest neighborhood. Maybe, even, you should use the borders from the source image, e.g. W=-75.842 etc. Sqr 16:35, 11 Aug 2006 (UTC)
 * It isn't requesting anything though. It is just pulling tiles from a folder on disk.  If a particular tile isn't there then nothing happens.Withak 18:34, 11 Aug 2006 (UTC)
 * I was trying to keep the xml as simple as possible so was hoping you don't need to get the exact extents and put them in by hand. Withak 19:17, 11 Aug 2006 (UTC)
 * is there a way to make the outside black areas transparent while not making holes in the imagery?
 * Re the newest "LZTS must= 1/2^N" edit: How does the problem (if the mentioned rule isn't kept) manifest? I don't remember any tile mis-alignation with any of 45,36,2.25,2.00,0.80,0.05 (and whatever else 180/N) LZTS's. Isn't there a problem with decimal->binary conversion of that value (might cause rounding errors)? IMO, there should be some 'ultimate statement' from some of the 'core devs' (those who really know how the cog wheels inside WW work) about the LZTS, definitely stating the rules for it. Sqr, 15:14, 19 Sep 2006 (UTC)
 * Apparently LZTSs that aren't 1/2^n will work, but when you zoom in close enough there will be alignment problems between the tiles. I think someone said you would need a fairly high-res image layer before you could notice the problem.Withak 16:17, 19 Sep 2006 (UTC)
 * Also, good luck getting a 'core dev' to say anything definitive. :)