On Thu, Dec 18, 2008 at 8:10 PM, Matthias Julius <[email protected]> wrote: > "Ævar Arnfjörð Bjarmason" <[email protected]> writes: > I guess you were looking at empty tiles (67 or 69 bytes). Empty tiles > are not optimized. In fact, they are never written to disc. When the > client finds during tile splitting that a tile is empty it throws the > tile away and copies emptyland.png or emptysea.png from the client's > root directory. Those are actually 1 pixel PNGs with 67 respective 69 > bytes size.
I should have been clear on that. No they were not empty tiles (I read the tile optimizing code and noticed the empty tile optimization you mention). What I was rendering was a glacial area which 1844,1089 is an example of. In cases of such tiles Tileset.pm will optimize each and every individual z17 tile even though the greater z12 tile consists of only two colors with a thin line running through it, if I've understood it correctly. The map contains many areas where this applies, like lakes, large areas of landuse, large buildings etc. _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
![Re: [Tilesathome] Potential t@h optimization: Re-use the optimized .png image](/search?l=tilesathome@openstreetmap.org&q=subject:%22Re%5C%3A+%5C%5BTilesathome%5C%5D+Potential+t%40h+optimization%5C%3A+Re%5C-use+the+optimized%09.png+image%22&o=newest){kind=link}
