[Tilesathome] Tileset files

spaetz osm at sspaeth.de
Tue Sep 16 11:09:08 BST 2008


On Tue, Sep 16, 2008 at 10:33:09AM +0200, Dirk-L?der Kreie wrote:
> would it overcomplicate things to put some metadata into a tileset file, so 
> the client can record information about the rendering process (which 
> datasource, which osmarender, which rasterizer and so forth)?

Well, you have those tilesets about 16 mio time per layer. since the tileset format works with fixed offsets you'd have to reserve 100 bytes for a renderer name, 8 bytes for the x,y, a byte for the layer etc. 

Is this really worth the bloat? We know who uploaded a tileset and we know when it was rendererd.

I am not opposing it. Someone just needs to adapt all the tools that work with it (mod_tah.c, server, client) to allow for that and allow for a gradual switchover too. Can it be done? yes. Does it require effort and will destabilize things even more for a time? likely.

> And since you have to take care of endianness, what's with older macs?

Endianness is defined as described in tileset-as-one-file in the wiki.

spaetz




More information about the Tilesathome mailing list