Hi, > Looking at the code for _unstable (which is identical to stable at the > moment, IIRC,) there's a function to recalibrate maxTilesetComplexity > based on processing time. IMO, it's fixing one problem (people not > having a good idea of where there complexity should be,) but causing > others (I see a couple things I consider logic errors, and it ignores > the fact that, for some of us, the bigger problem with complexity is > available RAM and not available CPU cycles.) I'm the one who is to blame for that code. Input is welcome.
Patrick "Petschge" Kilian _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
