On Wed, Apr 8, 2009 at 1:15 PM, Jens Frank jens.l.frank@googlemail.com wrote:
2009/4/8 Ævar Arnfjörð Bjarmason avarab@gmail.com
And it it enough to have the alternate static map inside <noscript>? Does this work on all the odd browsers out there that we want to support? If so that'll make everything else much easier.
There are some concerns about a) printing and b) the amount of JavaScript that needs to be loaded for the slippy map, and c) possibly missing <noscript> support. Would it perhaps be better to have the static map image that's currently in <noscript> as default, add a JavaScript "onclick" handler to it, that shows some animated sandclock, loads OpenLayers and displays a map instead of the former static image?
Sounds good, even on Firefox I'd prefer to have a static image when printing as I don't need the OpenLayers UI elements on paper. But even then quicker loading time wins over the maps being dynamic in most cases, and you get other niceties like right click -> save image.
Which is the default could be made optional, either with a parameter or site-wide (depending on a config setting. Requesting someone with JavaScript-fu to implement the user visible parts :)
Except on Wednesday you'll see an empty map (only coastline) if you look at that, since the osm2pgsql import is running on the tileserver. I don't know whether that's something that's a problem we could hack around in our own setup while updating the Planet mirror, maybe by keeping two database copies.
The original plan was to permanently import the diffs, just like others are doing it already (e.g. MetaCarta for the up-to-date service).
Ah, but the problem outlined above is encountered by OSM due to the way they're swapping out the planet weekly.
But in any case it's a solvable server administration problem, so let's just worry about it when we have something installed to worry about. I shouldn't have brought it up.