I also ended up using server-side rendering in an application for displaying crime incident points. Doing the map rendering server-side also allowed nice features such as enforcing access security and rich symbology.
We wrote our own very simple map service, rendering points from a database query onto an image. We didn't even use a spatial database - for X,Y data simply using standard B-tree indices was plenty fast enough. On Mon, Jan 26, 2015 at 2:57 PM, Harris Hudson <[email protected]> wrote: > Due to network download speeds/data volume and browser vector > rendering limitations, I resorted to a compromise by using > BBOX strategy and server side clustering/filtering in an OL2 > application I did a while ago to handle a layer of more than > 70,000 points (but with still some limitations for older browsers). > > The current application response time is a little poor but that > is due simply to old server hardware it is currently running > on (once the backend is upgraded in a few months time, most map > requests will be sub-second) - from the front end, using a > compromise of server side clustering/filtering, the OL2 side > of things can give the illusion of handling a huge number of > points. > > http://web.acma.gov.au/pls/radcom/site_proximity.main_page > > _______________________________________________ > 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
