Hi René, About a year ago, I tackled a similar problem [1] by putting FeatureServer [2] in front of my WFS server, acting as a WPS (sort of). Nowadays there are a few applications that can do real WPS (OGC standard), like PyWPS, Zoo, deegree (IIRC). The nice thing with FS was that I only needed to proved the resolution as an extra WFS parameter to get it to work in OL.
The idea is simple: - convert your GPX data into something that GeoServer (or MapServer, etc) can consume and then output as WFS - have a WPS act as a proxy between OL and your WFS and - configure the WPS to simplify the features it returns, based on your map resolution. The more you zoom in, the less you have it simplify and vice versa. I hope that helps. Regards, Roald [1] http://openlayers.org/pipermail/users/2009-January/009924.html [2] http://featureserver.org/ On 03/05/10 19:20, [email protected] wrote: > Hello, > > I use OpenLayers to show the track of a user. The user uploads a gpx file and > OpenLayers creates a vector and than shows the track. That's all working > fine. But users can also upload track files with more than 10000 track points > and that will slow down the zooming and scrolling of the map. > > > I thought about using only every n-th track point, but if I zoom in, the > resolution of the track becomes more and more bad, so I had to recalculate > the track points for every zoom level, which also slows down the browser. > So is there a way to limit the number of shown track points of a vector? > > Or is there a better way to solve my issue? > > Thanks for your help and best regards. > René > _______________________________________________ Users mailing list [email protected] http://openlayers.org/mailman/listinfo/users
