On Sat, Jul 12, 2008 at 12:03:25AM +0200, Henry Loenwind wrote: > I once had ma tah client patched to reject high complexity based on that > number, I removed it when I found out that it was useless. There were c8 > tiles my PC could not render, but c10 ones it could...
Complexity measures are and will always be a somewhat crude thing, so i am not surprised. The number of nodes proxies the complexity of a tile quite well, but then it will depend on what the nodes represent to estimate how difficult it will be for inkscape. If it's all "amenity=ghostbusters_were_here" nodes inkscape wouldn't care less, for example. If you have a limited machine, a scale from 1-10 would still make sense even if you miss out a few complexity=10 tiles. Better safe than sorry :-). A settings from 1-10000000 wouldn't improve this fact, it would just make the setting more complicated. But as I don't want to maintain another 16 mio entry complexity data base on the server, we'll have to find a good complexity measure anyway. I still favor tilesetfile filesize as it is very easy to gather and doesn't use up more disk space to keep track of. spaetz _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
