-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 spaetz wrote: | On Sun, Jul 06, 2008 at 03:07:58PM +0100, Kai Krueger wrote: |>> offset is either a pointer to the file position where the png data |>> is, or it can also be a blankness value: |>> 0=unknown |>> 1=land |>> 2=sea |>> 3=transparent (not implemented yet) |> |> Hmm, I think there is a tiny bug in the serve_tiles.py, it checks for |> the offset being larger than 1 for special case tiles. Both sea and |> transparent tiles would therefore try and load a tile with an invalid |> offset. Shouldn't it be greater than 3? | | True, that is a bug and it's fixed now. Thanks for spotting :-).
Checking greater than 3 still seems a bit un-expandable. Why not allocate the first 4096 offset values to mean special tiles? Then you could put special tiles named 0.png to 4095.png somewhere and whenever those offsets are encountered, redirect to them. Robert (Jamie) Munro -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkh0jFQACgkQz+aYVHdncI2HdgCfZqoDaemzW+aswSSnSmD/OZat 1IAAoN5kr8W2R/ssgQb4pv9mX2rNDOMd =T5is -----END PGP SIGNATURE----- _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
