spaetz <[EMAIL PROTECTED]> writes: > On Tue, Oct 14, 2008 at 01:05:05PM -0400, Matthias Julius wrote: >> > I tested the creation of tilesetfiles by the client. They look >> > good. I have implemented tileset file handling now. > > (what is still missing is marking requests as finished as user > stats. No clue yet, how a tileset should affect the "Uploaded number > of tiles".
How is that done now? I guess you leave empty tiles out? How are empty tilesets counted? I would say having a processor just to count the tiles in a tileset to update the statistics is a bit overkill. If we really want to count tiles that actually contain data the upload handler needs to read the index of the tileset file and count the non-empty tiles. > >> > 3) we save the tilesets and have a cron job that examines all >> > existing tileset files and deletes empty ones regularly. Not that >> > difficult but probably wasteful? >> 3a) only check tileset files that have been uploaded since the last >> check. > > That's feasable and might be the short term fix until we implement > something better. I would say we do it right from the beginning. There is no need to rush that through just to revisit the subject later. > >> 4) the client can upload a special "empty" file. 4a) this file only >> contains 1 byte (1=sea, 2=land, 3=transparent) 4b) this file is a >> special tileset file that instead of containing 4 bytes for each >> empty tile only contains the information that all tiles are empty >> and whether it is land, sea or transparent. > > Right, that's the alternative option I was considering. It would > actually only mark "blankness". The type of blankness is determined by > oceantiles.dat then. > >> Having a special "empty" file could eliminate the need for database >> lookups while tile serving alltogether. The drawback of this is >> that it will be a lot of inodes. Don't know if that is a problem. > > I rather have one 4MB db file (that is kept open and is mmapped into > RAM across tile servings) than 16 million 4 byte files that need > opening and closing all the time. Not that people pan across the Pacific at z12 or higher all the time. But anyway, in whatever format you want to have that info the client can (learn to) deliver it. What I wouldn't want to do is have the client upload tileset files full of empty tiles. That's just a waste of bandwidth if the server discards them anyway. The easiest for the client is probably to create a 1 byte file because then the uploader doesn't need to worry about that and uploads just whatever it finds in uploadable. Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
