[Geoserver-users] Geoserver 1.5.3 / WMS GetFeatureInfo Problem with different SRS

GeoServer GeoServer User
1

Hello everyone,

I have some problem with the GetFeatureInfo request.
I am trying to retrieve informations on a WMS layer stored in SRS:32631
which is displayed in SRS:4326.

I am having the following error message in the logs of geoserver :
[SEVERE]
org.vfny.geoserver.wms.responses.featureInfo.AbstractFeatureInfoResponse -
Longitude 646°10.5'E is out of range (±180°).

I don't understand why as I formulate my request as following:
"http://10.37.0.1:8080/geoserver/wms?REQUEST=GetFeatureInfo&VERSION=1.3.0&EXCEPTIONS=application/vnd.ogc.se_xml&BBOX=1.048831,42.845709,2.111667,43.512296&X=418&Y=389&INFO_FORMAT=application/vnd.ogc.gml&WIDTH=861&HEIGHT=540&LAYERS=mpc:road,mpc:railroad&STYLES=&SRS=EPSG:4326&QUERY_LAYERS=mpc:road,mpc:railroad&FORMAT=image/png"

Does anybody have a clue ?
--
View this message in context: http://www.nabble.com/Geoserver-1.5.3---WMS-GetFeatureInfo-Problem-with-different-SRS-tp14696353p14696353.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

Bakoi ha scritto:

Hello everyone,

I have some problem with the GetFeatureInfo request.
I am trying to retrieve informations on a WMS layer stored in SRS:32631
which is displayed in SRS:4326.

I am having the following error message in the logs of geoserver :
[SEVERE]
org.vfny.geoserver.wms.responses.featureInfo.AbstractFeatureInfoResponse -
Longitude 646°10.5'E is out of range (±180°).

I don't understand why as I formulate my request as following:
"http://10.37.0.1:8080/geoserver/wms?REQUEST=GetFeatureInfo&VERSION=1.3.0&EXCEPTIONS=application/vnd.ogc.se_xml&BBOX=1.048831,42.845709,2.111667,43.512296&X=418&Y=389&INFO_FORMAT=application/vnd.ogc.gml&WIDTH=861&HEIGHT=540&LAYERS=mpc:road,mpc:railroad&STYLES=&SRS=EPSG:4326&QUERY_LAYERS=mpc:road,mpc:railroad&FORMAT=image/png"

I don't really know, but it's likely it has been fixed in 1.6.0 (or else, you're having an issue with that specific layer...).

For example, if we have a look at this GeoServer 1.6.0-rc2 install:
http://geo.openplans.org:8080/geoserver

and we issue the following request against the topp:states layer, which
is stored in EPSG:4326, but queried in EPSG:900913 (the "Google projection"):

http://geo.openplans.org:8080/geoserver/wms?bbox=-13885038.38296092,2870337.13079368,-7455049.48918242,6338174.05575762&styles=&Format=application/openlayers&request=GetMap&layers=topp:states&width=800&height=317&srs=epsg:900913

and then click on the map to execute a GetFeatureInfo, the result
comes back just fine. An example GetFeatureInfo request against that layer is:

http://geo.openplans.org:8080/geoserver/wms?WIDTH=800&SRS=epsg%3A900913&LAYERS=topp%3Astates&HEIGHT=317&STYLES=&FORMAT=image%2Fpng&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&EXCEPTIONS=application%2Fvnd.ogc.se_xml&BBOX=-15693472.759336%2C2613721.922057%2C-5646615.112807%2C6594789.264494&X=361&Y=213&INFO_FORMAT=text%2Fhtml&QUERY_LAYERS=topp%3Astates&FEATURE_COUNT=50&srs=epsg%3A900913&layers=topp%3Astates&styles=

and it works for me.

Cheers
Andrea

3

aaime wrote:

Bakoi ha scritto:

Hello everyone,

I have some problem with the GetFeatureInfo request.
I am trying to retrieve informations on a WMS layer stored in SRS:32631
which is displayed in SRS:4326.

I am having the following error message in the logs of geoserver :
[SEVERE]
org.vfny.geoserver.wms.responses.featureInfo.AbstractFeatureInfoResponse
-
Longitude 646°10.5'E is out of range (±180°).

I don't understand why as I formulate my request as following:
"http://10.37.0.1:8080/geoserver/wms?REQUEST=GetFeatureInfo&VERSION=1.3.0&EXCEPTIONS=application/vnd.ogc.se_xml&BBOX=1.048831,42.845709,2.111667,43.512296&X=418&Y=389&INFO_FORMAT=application/vnd.ogc.gml&WIDTH=861&HEIGHT=540&LAYERS=mpc:road,mpc:railroad&STYLES=&SRS=EPSG:4326&QUERY_LAYERS=mpc:road,mpc:railroad&FORMAT=image/png"

I don't really know, but it's likely it has been fixed in 1.6.0 (or
else, you're having an issue with that specific layer...).

...

... it works for me.

Cheers
Andrea

Thank you Andrea for you answer.

I found my problem. My layer had a big name : 00_Eng_RailRoads_UTM29_WGS84.
It seems that for xml parsing it leads to an error. Everything is working
fine except the fact that I still see the same errors on the log of
Geoserver. I don't know why. I wonder if it is not the use of a too high
level of log for just a debug information.

Bye.
--
View this message in context: http://www.nabble.com/Geoserver-1.5.3---WMS-GetFeatureInfo-Problem-with-different-SRS-tp14696353p14730190.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

4

Bakoi ha scritto:

I found my problem. My layer had a big name : 00_Eng_RailRoads_UTM29_WGS84.
It seems that for xml parsing it leads to an error. Everything is working
fine except the fact that I still see the same errors on the log of
Geoserver. I don't know why. I wonder if it is not the use of a too high
level of log for just a debug information.

I'm loosing you here :slight_smile:
The error your reported was about a coordinate being out of definition
area, not about the name being too big, in fact that GetMap
request did not have the 00_Eng_RailRoads_UTM29_WGS84 layer at all?

Here is an excerpt of your first mail:

>>> I am having the following error message in the logs of geoserver :
>>> [SEVERE]
>>> org.vfny.geoserver.wms.responses.featureInfo.AbstractFeatureInfoResponse
>>> -
>>> Longitude 646°10.5'E is out of range (±180°).
>>>
>>> I don't understand why as I formulate my request as following:
>>> "http://10.37.0.1:8080/geoserver/wms?REQUEST=GetFeatureInfo&VERSION=1.3.0&EXCEPTIONS=application/vnd.ogc.se_xml&BBOX=1.048831,42.845709,2.111667,43.512296&X=418&Y=389&INFO_FORMAT=application/vnd.ogc.gml&WIDTH=861&HEIGHT=540&LAYERS=mpc:road,mpc:railroad&STYLES=&SRS=EPSG:4326&QUERY_LAYERS=mpc:road,mpc:railroad&FORMAT=image/png"

Another thing I've noticed only now is that you're trying to use VERSION=1.3.0 for WMS. GeoServer does not support it, the maximum
version we support is 1.1.1... we should throw an exception instead
of answering the request... also consider that for wms 1.1.1 the
bbox should be expressed in lon/lat order, whilst 1.3.0 requires
the opposite order afaik.

Cheers
Andrea