You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: spaetz [Added to the original trac issue at 12.28pm, Tuesday, 29th June 2010]
Mmmh, this is a difficult one. The tile serving is done by an apache extension written in C that has no access to the data base in which the available layers and zoom levels are stored.
In case there is no tile file we deliver whatever blank tile we need to deliver (all empty sea and empty land tiles are just "missing files" on the server. I don't really want to hardcode layers in that C app, nor do I want to add too many performance critical sanity checks.
It would be nice, of course. What we could do is to disable the zoom buttons from the browse GUI or deliver an error message if a wrong layer has been selected in the browse UI. Thinking of it, it should be possible and I'll add it on my TODOlist. Thanks for the sensible suggestions.
Reporter: stoecker
[Submitted to the original trac issue database at 6.48am, Thursday, 24th April 2008]
In http://tah.openstreetmap.org/Browse/?x=35240&y=21543&z=16&layer=cycle the cycle layer does not work for zoom levels > 16. Instead of silently failing, an error message tile should be delivered for each field.
The same is true, when wrong layer names are given. Here also an error tile should be delivered instead of empty tiles.
The text was updated successfully, but these errors were encountered: