On Sun, Oct 19, 2008 at 04:44:29PM +0200, Dirk St?cker wrote: > On Sun, 19 Oct 2008, spaetz wrote: > > > Ahh, not that easy, unfortunately. Adding in the mixed one would be > > possible without problems, but showing different images based on layers > > would really require modifications to mod_tah.c (more hardcoding and > > specialcasing there that I would really like to avoid). It should be > > Well, but's the right way to do. The oceantiles overlay has nothing to do > with the missing layer handling (it only represents the data of that), so > why should it use the same images?
Missing layers have nothing at all to do with this. The oceantiles.dat layer shows exactly what it is supposed to do: land/sea tiles based on oceantiles.dat (server version). I want the tile serving code to be as fast as possible. Hardcoding ever more special cases like: "if layer is called 'oceantiles' then serve these images x,y,z based on ...." will result in a complex beast that nobody will want to touch. This was the development philosophy on the old PHP based server and I want to avoid a repetition of that. I set the opacity of the oceantiles layer to 0.5 now, see .e.g. http://server.tah.openstreetmap.org/Browse/slippy/?zoom=12&lat=51.53447&lon=3.66425&layers=BT mixed tiles are still shown as water tiles, though. No idea what would be best in that case. spaetz _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
