Andy, The limitation is really about how browsers handle data as DOM elements.
The reality is that in most cases, people don't need to display hundreds or thousands of features as vectors. If you don't need to interact with the features directly (editing them), it may be acceptable/preferable to have your server send the data to the OpenLayers client as a Web Map Service (WMS), which is an image of the styled data. You can even support querying the data by using a WMS service that supports GetFeatureInfo. When people need to interact with the features, they may use a WMS until the user zooms in far enough, and the switch over to a vector layer. David. On Sat, Jun 25, 2011 at 12:07 AM, sulu <[email protected]> wrote: > Hi Davit. > > Ok. The OL-WIKI confirms it ;-). > This seems to be quite a bit of a constraint for the use of vector data. > Is is therefore unreasonable to think about an OL-Client which uses an areal > photo as background to display the cadastre on top? > Cadastre-features are mostly simple but there can be many of them. > > Andy > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/Can-t-get-WFS-to-work-tp6504309p6514095.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
