the question might be simple, the answer it is not ;-)
According to my experience, I would say it depends...
... on the browser type, the complexity of the features, memory and
CPU's of the PC, what you regard as still acceptable responsiveness of
the application, etc.
If your features are quite simply structured, i.e. with few vertices
(rectangle-like polygons, straight short lines, etc), then browsers like
IE 7/8 (v9 should be faster I guess) should be able to handle a few
100's. Chrome and Firefox maybe a few 1000's. With more features the
application becomes more and more sluggish and pan actions become sticky.
If your features are complex then this will happen already with fewer
features. I have not tried, but I would guess loading as vectors e.g.
the coastline of Norway, digitized with decent details, can make an OL
application virtually unusable because a single feature could have some
100000's vertices.
armin
On 19/01/2012 00:01, Tondo wrote:
Hi lists,
I have a simple question... I've got one vector layer, that might be
sometimes loaded by huge amount of data (hundreds/thousands of features).
What is the limit of features? Thank you!
Regards,
Tom.
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/A-LOT-of-features-tp7202081p7202081.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
_______________________________________________
Users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/openlayers-users
