I'm trying to make WMS GetFeatureInfo requests, but the response is always
that no features were found, even though I'm fairly positive that my BBOX,
X, Y, WIDTH, and HEIGHT values should yield plenty of results. Any ideas of
what might be going wrong, or is there anything I could do to find the
issue? I don't have access to GeoServer at all, so I can't check the logs
to see what PostGIS requests are being made. Here's an example of what I'm
sending:
LAYERS=thdl%3Atest2&TRANSPARENT=true&PROJECTION=EPSG%3A4326&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&STYLES=&EXCEPTIONS=application%2Fvnd.ogc.se_xml&FORMAT=image%2Fpng&SRS=EPSG%3A4326&BBOX=39.246446%2C2.598982%2C127.840196%2C45.310796&X=637&Y=197&INFO_FORMAT=text%2Fplain&QUERY_LAYERS=thdl%3Atest2&WIDTH=1008&HEIGHT=550
Thanks,
Tom
--
View this message in context: http://www.nabble.com/WMS-GetFeatureInfo-always-returns-no-results-tp23375992p23375992.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Without the logs that is a bit tough to diagnose. I guess I would confirm that the WMS returns features, and you are not getting a blank image or anything.
Another thing to do would be to convert the request to an equivalent WFS request and see if it returns any features.
-Justin
Tom B wrote:
Hi,
I'm trying to make WMS GetFeatureInfo requests, but the response is always
that no features were found, even though I'm fairly positive that my BBOX,
X, Y, WIDTH, and HEIGHT values should yield plenty of results. Any ideas of
what might be going wrong, or is there anything I could do to find the
issue? I don't have access to GeoServer at all, so I can't check the logs
to see what PostGIS requests are being made. Here's an example of what I'm
sending:
LAYERS=thdl%3Atest2&TRANSPARENT=true&PROJECTION=EPSG%3A4326&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&STYLES=&EXCEPTIONS=application%2Fvnd.ogc.se_xml&FORMAT=image%2Fpng&SRS=EPSG%3A4326&BBOX=39.246446%2C2.598982%2C127.840196%2C45.310796&X=637&Y=197&INFO_FORMAT=text%2Fplain&QUERY_LAYERS=thdl%3Atest2&WIDTH=1008&HEIGHT=550
Thanks,
Tom
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Thanks for the tips--Unfortunately, WFS doesn't return any results either,
and WMS does return GetMap requests just fine. I didn't see one, but is
there a way to use specific lat/lon values instead of the BBOX method, to
possibly see if the issue is related to the SRS?
Thanks,
Tom
Justin Deoliveira-6 wrote:
Hi Tom,
Without the logs that is a bit tough to diagnose. I guess I would
confirm that the WMS returns features, and you are not getting a blank
image or anything.
Another thing to do would be to convert the request to an equivalent WFS
request and see if it returns any features.
-Justin
Tom B wrote:
Hi,
I'm trying to make WMS GetFeatureInfo requests, but the response is
always
that no features were found, even though I'm fairly positive that my
BBOX,
X, Y, WIDTH, and HEIGHT values should yield plenty of results. Any ideas
of
what might be going wrong, or is there anything I could do to find the
issue? I don't have access to GeoServer at all, so I can't check the
logs
to see what PostGIS requests are being made. Here's an example of what
I'm
sending:
LAYERS=thdl%3Atest2&TRANSPARENT=true&PROJECTION=EPSG%3A4326&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&STYLES=&EXCEPTIONS=application%2Fvnd.ogc.se_xml&FORMAT=image%2Fpng&SRS=EPSG%3A4326&BBOX=39.246446%2C2.598982%2C127.840196%2C45.310796&X=637&Y=197&INFO_FORMAT=text%2Fplain&QUERY_LAYERS=thdl%3Atest2&WIDTH=1008&HEIGHT=550
Thanks,
Tom
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hmmm... can you include the WFS request you are using? You might be running into problems with wfs 1.1 axis order issues. I would make sure the request is a WFS 1.0 request.
As for specifying specific lat lon values, do you mean in the GetFeatureInfo request? I do not believe so, the values have to be in pixels.
Knowing a bit about the data might help. On the feature type editor screen what does it report as the native srs of your data. And what method of SRS handling are you using.
Also feel free to make a subset of your data available that you are experiencing the issue with (via private mail if you like) and I would be happy to try it out over here.
-Justin
Tom B wrote:
Hi Justin,
Thanks for the tips--Unfortunately, WFS doesn't return any results either,
and WMS does return GetMap requests just fine. I didn't see one, but is
there a way to use specific lat/lon values instead of the BBOX method, to
possibly see if the issue is related to the SRS?
Thanks,
Tom
Justin Deoliveira-6 wrote:
Hi Tom,
Without the logs that is a bit tough to diagnose. I guess I would confirm that the WMS returns features, and you are not getting a blank image or anything.
Another thing to do would be to convert the request to an equivalent WFS request and see if it returns any features.
-Justin
Tom B wrote:
Hi,
I'm trying to make WMS GetFeatureInfo requests, but the response is
always
that no features were found, even though I'm fairly positive that my
BBOX,
X, Y, WIDTH, and HEIGHT values should yield plenty of results. Any ideas
of
what might be going wrong, or is there anything I could do to find the
issue? I don't have access to GeoServer at all, so I can't check the
logs
to see what PostGIS requests are being made. Here's an example of what
I'm
sending:
LAYERS=thdl%3Atest2&TRANSPARENT=true&PROJECTION=EPSG%3A4326&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&STYLES=&EXCEPTIONS=application%2Fvnd.ogc.se_xml&FORMAT=image%2Fpng&SRS=EPSG%3A4326&BBOX=39.246446%2C2.598982%2C127.840196%2C45.310796&X=637&Y=197&INFO_FORMAT=text%2Fplain&QUERY_LAYERS=thdl%3Atest2&WIDTH=1008&HEIGHT=550
Thanks,
Tom
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Thanks for the help with this, Justin. After looking into it in more detail,
the WFS request I had been using didn't make sense, but something like this
does work:
wfs?typename=thdl%3Atest2&layers=thdl%3Atest2&projection=EPSG%3A4326&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&SRS=EPSG%3A4326&BBOX=39.246446%2C2.598982%2C127.840196%2C45.310796&MAXFEATURES=20&propertyName=fid,name
This should work fine for my situation. I'm just going to use JavaScript to
calculate the BBOX of the pixel being clicked (this on an OpenLayers map),
and that'll also let me add some customizable pixel tolerance, which is
something I needed to do anyway. I think that should work alright, but let
me know if there are any arguments against such a method.
Thanks again,
Tom
Justin Deoliveira-6 wrote:
Hmmm... can you include the WFS request you are using? You might be
running into problems with wfs 1.1 axis order issues. I would make sure
the request is a WFS 1.0 request.
As for specifying specific lat lon values, do you mean in the
GetFeatureInfo request? I do not believe so, the values have to be in
pixels.
Knowing a bit about the data might help. On the feature type editor
screen what does it report as the native srs of your data. And what
method of SRS handling are you using.
Also feel free to make a subset of your data available that you are
experiencing the issue with (via private mail if you like) and I would
be happy to try it out over here.
-Justin
Tom B wrote:
Hi Justin,
Thanks for the tips--Unfortunately, WFS doesn't return any results
either,
and WMS does return GetMap requests just fine. I didn't see one, but is
there a way to use specific lat/lon values instead of the BBOX method, to
possibly see if the issue is related to the SRS?
Thanks,
Tom
Justin Deoliveira-6 wrote:
Hi Tom,
Without the logs that is a bit tough to diagnose. I guess I would
confirm that the WMS returns features, and you are not getting a blank
image or anything.
Another thing to do would be to convert the request to an equivalent WFS
request and see if it returns any features.
-Justin
Tom B wrote:
Hi,
I'm trying to make WMS GetFeatureInfo requests, but the response is
always
that no features were found, even though I'm fairly positive that my
BBOX,
X, Y, WIDTH, and HEIGHT values should yield plenty of results. Any
ideas
of
what might be going wrong, or is there anything I could do to find the
issue? I don't have access to GeoServer at all, so I can't check the
logs
to see what PostGIS requests are being made. Here's an example of what
I'm
sending:
LAYERS=thdl%3Atest2&TRANSPARENT=true&PROJECTION=EPSG%3A4326&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&STYLES=&EXCEPTIONS=application%2Fvnd.ogc.se_xml&FORMAT=image%2Fpng&SRS=EPSG%3A4326&BBOX=39.246446%2C2.598982%2C127.840196%2C45.310796&X=637&Y=197&INFO_FORMAT=text%2Fplain&QUERY_LAYERS=thdl%3Atest2&WIDTH=1008&HEIGHT=550
Thanks,
Tom
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Glad you found a solution, the approach is legit as far as i am concerned, if it works it works. The WMS GetFeatureInfo might be a bit cleaner, so pity we could not figure out the issue.
-Justin
Tom B wrote:
Thanks for the help with this, Justin. After looking into it in more detail,
the WFS request I had been using didn't make sense, but something like this
does work:
wfs?typename=thdl%3Atest2&layers=thdl%3Atest2&projection=EPSG%3A4326&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&SRS=EPSG%3A4326&BBOX=39.246446%2C2.598982%2C127.840196%2C45.310796&MAXFEATURES=20&propertyName=fid,name
This should work fine for my situation. I'm just going to use JavaScript to
calculate the BBOX of the pixel being clicked (this on an OpenLayers map),
and that'll also let me add some customizable pixel tolerance, which is
something I needed to do anyway. I think that should work alright, but let
me know if there are any arguments against such a method.
Thanks again,
Tom
Justin Deoliveira-6 wrote:
Hmmm... can you include the WFS request you are using? You might be running into problems with wfs 1.1 axis order issues. I would make sure the request is a WFS 1.0 request.
As for specifying specific lat lon values, do you mean in the GetFeatureInfo request? I do not believe so, the values have to be in pixels.
Knowing a bit about the data might help. On the feature type editor screen what does it report as the native srs of your data. And what method of SRS handling are you using.
Also feel free to make a subset of your data available that you are experiencing the issue with (via private mail if you like) and I would be happy to try it out over here.
-Justin
Tom B wrote:
Hi Justin,
Thanks for the tips--Unfortunately, WFS doesn't return any results
either,
and WMS does return GetMap requests just fine. I didn't see one, but is
there a way to use specific lat/lon values instead of the BBOX method, to
possibly see if the issue is related to the SRS?
Thanks,
Tom
Justin Deoliveira-6 wrote:
Hi Tom,
Without the logs that is a bit tough to diagnose. I guess I would confirm that the WMS returns features, and you are not getting a blank image or anything.
Another thing to do would be to convert the request to an equivalent WFS request and see if it returns any features.
-Justin
Tom B wrote:
Hi,
I'm trying to make WMS GetFeatureInfo requests, but the response is
always
that no features were found, even though I'm fairly positive that my
BBOX,
X, Y, WIDTH, and HEIGHT values should yield plenty of results. Any
ideas
of
what might be going wrong, or is there anything I could do to find the
issue? I don't have access to GeoServer at all, so I can't check the
logs
to see what PostGIS requests are being made. Here's an example of what
I'm
sending:
LAYERS=thdl%3Atest2&TRANSPARENT=true&PROJECTION=EPSG%3A4326&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&STYLES=&EXCEPTIONS=application%2Fvnd.ogc.se_xml&FORMAT=image%2Fpng&SRS=EPSG%3A4326&BBOX=39.246446%2C2.598982%2C127.840196%2C45.310796&X=637&Y=197&INFO_FORMAT=text%2Fplain&QUERY_LAYERS=thdl%3Atest2&WIDTH=1008&HEIGHT=550
Thanks,
Tom
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks
to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.