[Tilesathome] lowzoom rendering takes forever?
spaetz
osm at sspaeth.de
Sun Nov 25 19:04:28 GMT 2007
On Sun, Nov 25, 2007 at 02:04:37PM +0100, Hakan Tandogan wrote:
> > 1) Implement a simplification preprocessor that cuts down the OSM files to a manageable complexity (no need for a 1m resolution when you squeeze half of the UK on a tile).
>
> A preprocessor that determines how many meters a pixel on a given tile
> would be and selectively removes nodes from ways? Seems like an
> interesting experiment.
something along this line, but even simpler, just run a simplifier with a granularity of 500meters or whatever on the data. i wouldn't want to repeat that process for each zoom level.
> > 2) Render a z12 which is geared for lowzoom generation, ie without text and just with the major roads etc. Then stitch them together for lowzoom tiles and overlay them with a transparent text layer. To make IE happy, we would probably merge down both layers in one PNG file.
>
> I think the first solution would be the better one.
i'd actually prefer the second one. this would enable us to turn on multiple language layers for instance. prefer turkish or greek names for cyprus? just switch to the language of your choice. although it would prevent us from running into scaling issues, which we would eventually do. visually the result should be the same.
More information about the Tilesathome
mailing list