Codes seems okay to me. The only thing that can cause performance issue could be transforming from 4326 to map projection but after initializing geometries it shouldn't affect the performance.
In my opinion, you can: 1- Try to change renderers to get best performance. 2- Simplify geometries with respect to zoom levels. 3- Try to keep fill opacity to 0 and stroke opacity to 1 (should be tested) 4- Draw only the place inside the bounding box These are the things which I can say, but unfortunately with many vertexes openlayers (even in chrome) gives a bit bad performance. So don't expect to get results like desktop applications. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/very-slow-map-using-WKT-Multipolygon-with-a-lot-of-Points-tp5017181p5017233.html Sent from the OpenLayers Users mailing list archive at Nabble.com. _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
