Thanks very much for the swift response. I have set the following in the JVM startup parameters: -Dorg.geoserver.wms.featureinfo.render.enabled=false And it is back working as before.
I have logged the bug here: http://jira.codehaus.org/browse/GEOS-6420 On 28 March 2014 13:40, John O'Toole <[email protected]> wrote: > Thanks very much for the swift response. I have set the following in the > JVM startup parameters: > -Dorg.geoserver.wms.featureinfo.render.enabled=false > And its back working as before. > > I'll log the bug later today. > > Thanks again, > John > > > On 28 March 2014 09:40, Andrea Aime <[email protected]> wrote: > >> On Fri, Mar 28, 2014 at 10:25 AM, John O'Toole <[email protected]>wrote: >> >>> We are using GeoServer 2.1 to display data that is stored in Oracle >>> sdo_geometry. The data is stored in Irish Transverse Mercator (EPSG:2157) >>> and we want display it on a map in that projection. >>> With release 2.1.0 we are making the following GetFeatureInfo request >>> when a user clicks on the map: >>> >>> http://<server>:8080/geoserver/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&LAYERS=TownlandLayer&QUERY_LAYERS=TownlandLayer&STYLES=,,,&BBOX=618565.0,707446.2,620258.3,708216.1&FEATURE_COUNT=10&HEIGHT=582&WIDTH=1280&FORMAT=image%2Fpng&INFO_FORMAT=application/vnd.ogc.gml&SRS=EPSG:2157&X=587&Y=354 >>> >>> This returns the id of the feature clicked on, plus the geometry as GML >>> (in EPSG:2157 coordinates) so we can highlight the feature on the map. >>> >>> This all works perfectly. >>> >>> This week we upgraded to GeoServer 2.5 and now the same GetFeatureInfo >>> request >>> returns the geometry in lat long rather than in EPSG:2157. As far as I can >>> see the layers are configured exactly the same on both GeoServer instances >>> and they are both feeding off the same database. >>> >>> We're a bit lost on this. Any ideas why we're now getting the geometry >>> back as lat/long rather than EPSG:2157? >>> >> The vector GetFeatureInfo subsystem got completely rewritten in 2.5 to >> ensure better identification accuracy against >> odd shaped or dinamically sized icons, you can read about it here: >> http://blog.geoserver.org/2014/01/21/geoserver-2-5-beta-released/ >> >> I guess we did not consider reprojection during that rewrite. However, >> the old feature info engine is still available, and you can >> re-activate it adding the following parameter among the JVM startup >> options: >> -Dorg.geoserver.wms.featureinfo.render.enabled=true >> >> Could you open a bug report about this issue on >> http://jira.codehaus.org/browse/GEOS ? >> >> Cheers >> Andrea >> >> >> -- >> == >> Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK >> for more information. >> == >> >> Ing. Andrea Aime >> @geowolf >> Technical Lead >> >> GeoSolutions S.A.S. >> Via Poggio alle Viti 1187 >> 55054 Massarosa (LU) >> Italy >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> mob: +39 339 8844549 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> ------------------------------------------------------- >> > >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
