Hi,
I would ask you about WMS FeatureInfo requests to Geoserver. Is it
mandatory to include the '&styles' parameter in a request? Our geoserver
1.7.5 distribution only returns information if we specify this param.
For example whit next request,
http://…/wms?bbox=-130,24,-66,50&format=jpeg&info_format=text/plain&request=GetFeatureInfo&layers=topp:states&query_layers=topp:states&width=550&height=250&x=170&y=160
we have this error:
<ServiceExceptionReport version="1.1.1" >
<ServiceException code="org.vfny.geoserver.wms.requests.GetMapKvpReader">
1 layers requested, but found 0 styles specified. Since SLD
parameter is not yet implemented, the STYLES parameter is mandatory and
MUST have exactly one value per requested layer
</ServiceException>
</ServiceExceptionReport>
What is it used for?
Thanks
Funnily enough I ran into the same thing today and I had to adapt my code.
The OGC spec does say it is required, so Geoserver is right according to
the spec.
I must admit that I do not see the use for the parameter, but that aside.
Best regards,
Bart
Hi,
I would ask you about WMS FeatureInfo requests to Geoserver. Is it
mandatory to include the '&styles' parameter in a request? Our geoserver
1.7.5 distribution only returns information if we specify this param.
For example whit next request,
http://…/wms?bbox=-130,24,-66,50&format=jpeg&info_format=text/plain&request=GetFeatureInfo&layers=topp:states&query_layers=topp:states&width=550&height=250&x=170&y=160
we have this error:
<ServiceExceptionReport version="1.1.1" >
<ServiceException code="org.vfny.geoserver.wms.requests.GetMapKvpReader">
1 layers requested, but found 0 styles specified. Since SLD
parameter is not yet implemented, the STYLES parameter is mandatory and
MUST have exactly one value per requested layer
</ServiceException>
</ServiceExceptionReport>
What is it used for?
Thanks
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
bartvde@anonymised.com ha scritto:
Funnily enough I ran into the same thing today and I had to adapt my code.
The OGC spec does say it is required, so Geoserver is right according to
the spec.
I must admit that I do not see the use for the parameter, but that aside.
Oh, but without that parameter you don't know what to catch.
The style may filter out data, without it it won't know about that.
So style is an integral part of GetFeatureInfo with good reason.
Also, GeoServer in the latest versions uses the SLD to determine how
big the search radius should be, layer by layer (if you have a point
layer with 20px wide symbols the search radius will be automatically
set to 20 for that layer).
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Umm ... I think I must review the spec again 
Thanks!
Andrea Aime escribió:
bartvde@anonymised.com ha scritto:
Funnily enough I ran into the same thing today and I had to adapt my
code.
The OGC spec does say it is required, so Geoserver is right according to
the spec.
I must admit that I do not see the use for the parameter, but that
aside.
Oh, but without that parameter you don't know what to catch.
The style may filter out data, without it it won't know about that.
So style is an integral part of GetFeatureInfo with good reason.
Also, GeoServer in the latest versions uses the SLD to determine how
big the search radius should be, layer by layer (if you have a point
layer with 20px wide symbols the search radius will be automatically
set to 20 for that layer).
Cheers
Andrea