Looks like the fix was applied to 2.5-SNAPSHOT? Ok, fix committed. Tomorrow it should be in the nightly build, anyone has > time to verify it? (mind, the build must be from Apr 28, or later)
http://ares.boundlessgeo.com/geoserver/2.5.x/ If it is not fixed for you please comment on the issue, and we can re-open the bug. Jody Garnett On Mon, Aug 11, 2014 at 7:51 AM, Ben Khoo <[email protected]> wrote: > Hi, > > I'd just like to check my understanding of > https://jira.codehaus.org/browse/GEOS-6420 (WMS GetFeatureInfo does > reproject the featureMember geometry in GeoServer 2.5) > > According to the issue and documentation > http://docs.geoserver.org/latest/en/user/services/wms/reference.html it > appears that the returned geometry should be reprojected into the specified > SRS no matter the projection of the layer in Geoserver. > > Here is a test case using a layer that is deployed with Geoserver. > > If you use the link below, it will return the geometry in EPSG:4326 as > expected because the SRS is set to EPSG:4326. > > > http://localhost:8080/geoserver/topp/wms?REQUEST=GetFeatureInfo&EXCEPTIONS=application/vnd.ogc.se_xml&BBOX=141.228065,-46.65732,152.113183,-37.586388&SERVICE=WMS&INFO_FORMAT=application/json&QUERY_LAYERS=topp:tasmania_state_boundaries&FEATURE_COUNT=50&Layers=topp:tasmania_state_boundaries&WIDTH=600&HEIGHT=500&format=image/png&styles=&srs=EPSG:4326&version=1.1.1&x=303&y=249 > > If you use this link with an SRS of EPSG:900913 I would expect the > returned geometry to be in EPSG:900913 however it is still EPSG:4326. > > > http://192.168.2.211:8080/geoserver/topp/wms?REQUEST=GetFeatureInfo&EXCEPTIONS=application/vnd.ogc.se_xml&BBOX=15721436.2815,-5886318.25325,16933162.0745,-4521159.95999&SERVICE=WMS&INFO_FORMAT=application/json&QUERY_LAYERS=topp:tasmania_state_boundaries&FEATURE_COUNT=50&Layers=topp:tasmania_state_boundaries&WIDTH=600&HEIGHT=500&format=image/png&styles=&srs=EPSG:900913&version=1.1.1&x=303&y=249 > > This behaviour seems to be the same as what is seen in GEOS-6420. > > I'd appreciate if anyone could test the issue above and let me know if > this is a misunderstanding on my part or a regression in Geoserver. > > I have also tried to use the workaround > (-Dorg.geoserver.wms.featureinfo.render.enabled=false) specified in the > Jira issue but to no avail. > > My geoserver version is, > > Version > 2.5-SNAPSHOT > Git Revision > 469f323f1f53f64ab3e65ff2746848b49c5426ed > Build Date > 03-Aug-2014 16:56 > GeoTools Version > 11-SNAPSHOT (rev d365f33a505349746b15bef1dfffc99cde2cde68) > GeoWebCache Version > 1.5-SNAPSHOT (rev > e44af36fc28054134ace0ba3902d0645bddf857e/e44af36fc28054134ace0ba3902d0645bddf857e) > > > Kind Regards, > Ben > > ------------------------------------ > Ben Khoo > Gaia Resources > p +61 8 9227 7309 > w www.gaiaresources.com.au > e [email protected] > > > ------------------------------------------------------------------------------ > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
