Re: [Geoserver-users] How do you handle large amounts of data?

[Tito, J. <Jos...@co...>]

Thanks everyone for the replies, but I had a few other questions about
integrating GeoServer:

 

-          Is there any way to make the points plotted by a WMS
clickable? In our current app our points open popups when clicked, and
we'd like to replicate that.

-          Is there a way to filter points returned from the WMS? Ex.
SELECT * FROM [table] WHERE type IN ([types]) AND time >= expiredTime

 

 

From: Phil Scadden [mailto:p.s...@gn...] 
Sent: Thursday, September 08, 2011 5:06 PM
To: geo...@li...
Subject: Re: [Geoserver-users] How do you handle large amounts of data?

 


  

The main problem I have is when a user views an area on a map that has
more than 2,000 points, performance is severely degraded. I was
wondering if GeoServer could help with this in some way. If a particular
area has 5,000 points for example, is there a way to group that
information into clusters with GeoServer. So the browser only thinks
there's 2,000 points, but those points represent the 5,000 you should be
seeing?

Well I am pumping out some pretty huge datasets via geoserver, but the
drawing is done WMS. When you talk about performance degradation with
3000 pts, it sounds like you are using WFS which is definitely too slow.
You want to draw with WMS (where you have server-level hardware doing
the drawing using fast code not javascript and where tile caching can
further improve performance), and WFS for querying. If you look at the
SLDSelect example in openlayers, you can even use WMS for drawing the
selection but geoserver doesnt honour SRS in the SLD (mapserver does) so
you have to deal with that in the client.

Notice: This email and any attachments are confidential. If received in
error please destroy and immediately notify us. Do not copy or disclose
the contents.