|
I built a GML Renderer as part OWS4 last year, which used the original
development of vector rendering. Since then, I've noticed a tweaks have
made it back into the codebase which should make it faster. Below is a table measuring seconds to load GML lines/polygons. Approx 85% of the time was spent parsing GML. 15% rendering.
Erik, I'll send you the presentation directly. It is too large to send to the list. Erik Uzureau wrote: Dear users, dev, Someone asked me today what the max number of coordinates could be drawn for a geometry with the OL Vector Layer and I did not know how to really answer. I asked cr5 and he gave me some off the cuff estimates, which I have added to the FAQ here:http://trac.openlayers.org/wiki/FrequentlyAskedQuestions#WhatisthemaximumnumberofCoordinatesFeaturesIcandrawwithaVectorlayer Basically, he has suggested the following as upper bounds of reasonable use: * ~2500 Coordinates * ~100-200 Features (Since each geometry is rendered as a separate DOM object, dragging and the like get seriously slowed down the more features you have on the map.) If you've been using the vector layers in different browsers or with different limits... please let us know by either replying to this email... or just going right in and directly ediitng the wiki itself. The more input we have the better we know our own limits. Thanks for anyone who can chime in --Erik _______________________________________________ Dev mailing list [email protected] http://openlayers.org/mailman/listinfo/dev -- Cameron Shorter Geospatial Systems Architect Tel: +61 (0)2 8570 5050 Mob: +61 (0)419 142 254 Think Globally, Fix Locally Commercial Support for Geospatial Open Source Software http://www.lisasoft.com/LISAsoft/SupportedProducts.html |
_______________________________________________ Dev mailing list [email protected] http://openlayers.org/mailman/listinfo/dev
