|
In releases prior to 2.5 if in run a WMS getFeatureInfo request using a projected coordinate system (in my case EPSG:2157), then the response geometry is also in that projected coordinate system. However, with the new getFeatureInfo engine introduced in release 2.5, the returned geometry is lat/long.
This has been discussed in this user group post: http://osgeo-org.1560.x6.nabble.com/GeoServer-2-5-returns-GetFeatureInfo-featureMember-geometry-as-lat-long-rather-than-projected-tt5131739.html#none
I can get around this by reverting back to the old getFeatureInfo engine by adding this JVM startup parameter:
Example of the WMS request I'm making:
Here's a sample response from GeoServer 2.1 (good):
Here's a sample response from GeoServer 2.5 (bad):
|