better support for WMS getFeatureInfo on point & line datasets
--------------------------------------------------------------
Key: GEOS-880
URL: http://jira.codehaus.org/browse/GEOS-880
Project: GeoServer
Issue Type: Improvement
Components: WMS
Reporter: ross elliott
Assigned To: Gabriel Roldán
Priority: Trivial
As a reminder for the dev team.
Ross Elliott ha scritto:
That's exactly how UMN Mapserver works, you change the size of the
buffered pixel for each query layer, not ideal but it does work
providing the buffer size takes account of the biggest symbol size in
the layer and the placement of it. Ideally (for me at least) the WMS
spec would allow a BBOX for a query area rather than a single point
(like UMN Mapserver's cgi-mode query) this wouldn't solve the problem
where a symbol is placed far away from the actual point but I suspect
that's a rare occurance anyway.
This reminds me a lot about the meta-buffer issue with tiled rendering.
If the SLD is relatively static, we can spot the right buffer size by inspecting it. If not, we could have a new parameter in the request that allows the user to force a specific search area.
Ross, can you open a jira issue about this? Maybe we won't fix this overnight, at least a jira issue will make us avoid forgetting about it.
Cheers
Andrea
For me, a good solution would be to include a getFeatureInfoBufferSize and getFeatureInfoBufferUnits in the featureType so that a simple buffer could be created based on either geographic units or pixels. I'm sure this would work for most cases and is an improvement over what is currently done. Also faster than parsing an sld every time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira