Thanks for your replies. Geowolf: I see..logically I can understand how "getFirstCoordinate()" might be a source of this kind of trouble for polygons, since this kind of layer has shared borders.
However it applies to certain points of an address layer. For instance https://karta.eskilstuna.se/geoserver/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&FORMAT=image%2Fpng&TRANSPARENT=true&QUERY_LAYERS=sokvyx_adresser_adresser&LAYERS=sokvyx_adresser_adresser&TILED=true&INFO_FORMAT=text%2Fhtml&feature_count=12&X=116&Y=335&WIDTH=512&HEIGHT=512&SRS=EPSG%3A3010&STYLES=&BBOX=151339.19999999972%2C6583086%2C152772.79999999973%2C6584519.6 is the result of an URL- construction with a getFeatureInfoUrl that has the point's real coordinates i.e the point we can pretend we getFeatureInfo-clicked. It will return three addresses where the first one's point is 22 meters away from the above point. So I was wondering whether the above call generates a pretty generous buffer or if something else is amiss. Regards, David -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
