On Monday 26 January 2009 14:19:50 Andreas Hocevar wrote:
Hi Gabriel,
On Sun, Jan 25, 2009 at 7:36 PM, Gabriel Roldan groldan@anonymised.com wrote:
I loved the hover functionality in the WFSGetFeature control. I realize
the overhead it may impose and hence it came to my mind whether it could
be benefited from an extra GetFeature optional parameter to decimate the
geometries based on the map’s dimensions, the same way the WMS does…
You mean by resolution? That would be awsome! This is one of the
frequently requested features on the openlayers-users list: to have a
server that returns geometries with just that much detail as required
for the current resolution.
Yeah, it seems there’s concensus on its usefulness and that we can do that. Next to see whether to do that on spare time or not
[14:02] hey guys, it seems the OL guys would love us if we add decimation/generalization support to WFS
[14:02] (and its not the first time someone asks)
[14:03] so it seems pretty easy to me, a custom parameter to getfeature and some JTS generalization
[14:03] am I being too naive?
[14:04] → SEWilco2 has joined this channel (n=sewilco@anonymised.com).
[14:04] → iwillig has joined this channel (n=ivan@anonymised.com).
[14:04] ( and yeah I know that sort of fall into the wcs scope)
[14:05] but how many times wfs is used for rendering? lots
[14:05] aaime, jdeolive?
[14:05] sorry?
[14:05] hi, should of pinged before my speech
[14:05] ah, I see
[14:06] yeah, i can def see the use case… i guess its just a custom parameter along with a query hint?
[14:06] groldan, that seems to fall squaredly in the wps use case
[14:06] do we have a query hint for generalization? used for rendering?
[14:06] thought I agree it would be useful in wfs too
[14:06] aaime: I know
[14:06] yet…
[14:06] jdeolive, the generalization is part of the renderer code
[14:06] it’s not an hint
[14:07] gotcha
[14:07] we should wrap teh returned feature collection with a decimating wrapper
[14:07] right
[14:07] so it woudl be a matter of setting a decimation vendor option
[14:07] using it in GetFeature to decide wheter the returned feature collections should be decimated or not
[14:08] I would not be against it, thought it seems to add complexity in the wrong place
[14:08] yet, wps is another protocol and I understand that it would require a different client
[14:09] soo… I guess open a jira issue about that?
[14:09] and eventually decide wheter you want to sponsor it for a certain release
[14:09] yeah, I share your concern
[14:09] or let’s decide if OpenGeo wants to sponsor that
[14:09] but I guess the use case is wide spread enough as to deserve it
[14:09] (cholmes, where are you when we need you most? ;.) )
[14:10] http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html
[14:10] Title: WFS: GetFeature Example (GeoServer) (at dev.openlayers.org)
[14:10] groldan, I know about the use case all too well 
[14:10] that’s my primary goal, helping out Andreas with the hover functionality
[14:11] aaime: sure you do, it’s related to performance 
That is, we could add this extra parameter to GeoServer’s GetFeature
operation and get smaller geometries as good for the map as the rendered
ones are.
What do you think?
If possible, this would be a killer feature (at least in my opinion).
Andreas.
On Friday 09 January 2009 13:32:05 Andreas Hocevar wrote:
Hi,
On Fri, Jan 9, 2009 at 12:43 AM, vjalfxweb juddy.g@anonymised.com wrote:
Using OpenLayers and GeoServer. Essentially we have lots (>10,000)
points (lat, lon with other string data) that we would like to overlay
on some WMS layer (google maps, virtual earth, etc.). User must be
able to click points to display pop ups. The data is currently stored
in mysql db(essentially lat, lon, and some other data) and we’re
using JSON to retrieve it from a java servlet, but that can be
modified.
Looking for the most efficient way to render the data in terms of
responsiveness.
I would suggest a combined WMS/WFS solution: render your map using
WMS, and use WFS GetFeature with a click handler to retreive the
features for the region the user clicked.
For this, you could use the WFSGetFeature control that OpenGeo is
about to contribute to OpenLayers. You can see it in action at
http://dev.openlayers.org/sandbox/topp/wfs/examples/wfs-getfeature.html
Comments on the usefulness and test reports for this control are
appreciated.
Regards,
Andreas.
–
Gabriel Roldan
OpenGeo - http://www.opengeo.org
----- This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
Gabriel Roldan
OpenGeo - http://www.opengeo.org