Hi,
is it possible to filter a WMS GetFeatureInfo request to limit the number of
parameters (database table columns) that are returned for an individual
feature?
Any help appreciated,
Dave
--
View this message in context: http://www.nabble.com/WMS-GetFeatureInfo-tp21913573p21913573.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
djud ha scritto:
Hi,
is it possible to filter a WMS GetFeatureInfo request to limit the number of
parameters (database table columns) that are returned for an individual
feature?
Nope, it's not possible. But you can make a wfs GetFeature request
instead and parse the gml/geojson on the client side and build
whatever representation you want.
Also, would you want that setting as a server side option, or as
a request parameter? Trying to understand if you are trying to
protect your data (in this case you'd need a server side param)
or just show less result on occasion (in this case a request
parameter would suit better your needs).
In any case, you can also open a request for a new feature
on jira.codehaus.org. If many people vote to have it maybe
some dev will take the time to implement it (if it's server
side config it's unlikely to happen on the 1.7.x series
thought).
And if you cannot wait or do it yourself, there is also
the commercial support option, see the associated page
at geoserver.org
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Thanks Andrea for the reply,
if I use GetFeature instead, how would I duplicate the X and Y (and
hard-coded 2 pixel halo) parameters that we have in GetFeatureInfo? Just set
a very small BBOX?
As for GetFeatureInfo, I would just want the filter option as a parameter to
limit the amount of returned data - no data protection issues, just
efficiency.
Cheers,
Dave
--
View this message in context: http://www.nabble.com/WMS-GetFeatureInfo-tp21913573p21914083.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
djud ha scritto:
Thanks Andrea for the reply,
if I use GetFeature instead, how would I duplicate the X and Y (and
hard-coded 2 pixel halo) parameters that we have in GetFeatureInfo? Just set
a very small BBOX?
I believe you'll find the answer to your request here:
http://www.mail-archive.com/users@anonymised.com/msg08199.html
As for GetFeatureInfo, I would just want the filter option as a parameter to
limit the amount of returned data - no data protection issues, just
efficiency.
Well, we could add a vendor parameter to GetFeatureInfo to limit the
columns returned, to mimick GetFeature, propertyName=p1,p2,...
If you want this open a feature request on jira.codehaus.org.
If enough people ask for it someone will eventually implement it.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
That's great Andrea, thanks for your help.
The code in the link you provided is a very good work-around to the problem
and a lot less hassle for the geoserver developers than me requesting an
additional vendor parameter, so I'll leave it a that.
Thank you.
--
View this message in context: http://www.nabble.com/WMS-GetFeatureInfo-tp21913573p21914520.html
Sent from the GeoServer - User mailing list archive at Nabble.com.