Greetings.
Geoserver's graphic generation is working perfectly, but I can't get
GetFeatureInfo to work correctly on my data because of a difference in SRS.
My client makes a WMS request like this:
http://laputa:8080/geoserver/wms?
&VERSION=1.1.1
&REQUEST=GetFeatureInfo
&SERVICE=WMS
&SRS=EPSG:4326
&BBOX=-72.66666666666667,41,-69.33333333333333,44
&WIDTH=500
&HEIGHT=450
&LAYERS=ctps:tip_ims0603
&STYLES=&FORMAT=image/png
&INFO_FORMAT=text/html
&EXCEPTIONS=application/vnd.ogc.se_xml
&FEATURE_COUNT=100
&QUERY_LAYERS=ctps:tip_ims0603
&X=260
&Y=272
Which produces an empty set of results. In text/plain mode, the message "no
features were found."
This happens for both PostGIS and shapefile layers.
My data uses SRS EPSG:26986 (Massachusetts Mainland Meters), but the WMS
request uses EPSG:4326.
When I do a similar request in EPSG:26986:
http://laputa:8080/geoserver/wms?
&VERSION=1.1.1
&REQUEST=GetFeatureInfo
&SERVICE=WMS
&SRS=EPSG:26986
&BBOX=200000,800000,300000,900000
&WIDTH=500
&HEIGHT=285
&LAYERS=ctps:tip_ims0603
&STYLES=
&FORMAT=image/png
&INFO_FORMAT=text/html
&EXCEPTIONS=application/vnd.ogc.se_xml
&FEATURE_COUNT=100
&QUERY_LAYERS=ctps:tip_ims0603
&X=167
&Y=1
I get a successful result.
So it seems that GeoServer doesn't do the transformation correctly. Any
ideas why this is happening?
I don't think I can get my client (MapBender) to make the request with
EPSG:26986. It seems to only use EPSG:4326.
MapBender - GeoServer 1.3.0 - Tomcat - Solaris
Thank you.
-Ellery
--
View this message in context: http://www.nabble.com/WMS-GetFeatureInfo-%3A-no-features-were-found-tf1956217.html#a5365514
Sent from the GeoServer - User forum at Nabble.com.
It sounds like GetFeatureInfo may not support reprojection. Could you report this as a bug to our JIRA task tracker: http://jira.codehaus.org/browse/GEOS We can try to confirm it there and get around to fixing it.
best regards,
Chris
elleryjh wrote:
Greetings.
Geoserver's graphic generation is working perfectly, but I can't get
GetFeatureInfo to work correctly on my data because of a difference in SRS.
My client makes a WMS request like this:
http://laputa:8080/geoserver/wms?
&VERSION=1.1.1
&REQUEST=GetFeatureInfo
&SERVICE=WMS
&SRS=EPSG:4326
&BBOX=-72.66666666666667,41,-69.33333333333333,44
&WIDTH=500
&HEIGHT=450
&LAYERS=ctps:tip_ims0603
&STYLES=&FORMAT=image/png
&INFO_FORMAT=text/html
&EXCEPTIONS=application/vnd.ogc.se_xml
&FEATURE_COUNT=100
&QUERY_LAYERS=ctps:tip_ims0603
&X=260
&Y=272
Which produces an empty set of results. In text/plain mode, the message "no
features were found."
This happens for both PostGIS and shapefile layers.
My data uses SRS EPSG:26986 (Massachusetts Mainland Meters), but the WMS
request uses EPSG:4326.
When I do a similar request in EPSG:26986:
http://laputa:8080/geoserver/wms?
&VERSION=1.1.1
&REQUEST=GetFeatureInfo
&SERVICE=WMS
&SRS=EPSG:26986
&BBOX=200000,800000,300000,900000
&WIDTH=500
&HEIGHT=285
&LAYERS=ctps:tip_ims0603
&STYLES=
&FORMAT=image/png
&INFO_FORMAT=text/html
&EXCEPTIONS=application/vnd.ogc.se_xml
&FEATURE_COUNT=100
&QUERY_LAYERS=ctps:tip_ims0603
&X=167
&Y=1
I get a successful result.
So it seems that GeoServer doesn't do the transformation correctly. Any
ideas why this is happening?
I don't think I can get my client (MapBender) to make the request with
EPSG:26986. It seems to only use EPSG:4326.
MapBender - GeoServer 1.3.0 - Tomcat - Solaris
Thank you.
-Ellery
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org