On Fri, Jul 11, 2008 at 12:29:39PM +0200, Florian Lohoff wrote: > On Fri, Jul 11, 2008 at 06:53:13AM +0200, spaetz wrote: > > Lower priority items: > > - Reimplement tileset complexity measure. > > As an idea concerning the complexity measure - Could the number of > objects be simply used? E.g. the client downloads the data via the api > and simply counts points and ways e.g: > > grep "<node" | wc -l
I was thinking that the server determines the complexity of a tileset simply by the size of its tilesetfile, no need for more databases with 16 mio more entries and translates that into a complexity value between 1-10 as it is now or so. But I will discuss this with deelkar once things have settled down a bit. > Also clients could one day build some strategy on what to announce as > maximum complexity they are capable to render - starting low and > increasing until a fail - E.g. tcp slow start - increasing the window > on success and shorten it on fail.. Why not just have the user set a maxcomplexity value in the config. He knows how much RAM the machine has. spaetz _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
