And with even more testing, it appears that the problem is due to the Halo option set for displaying the values of extracted contours. Also, it only happens when the gs:Contour AND the TextSymbolizer (with Halo) are used at the same time : - with gs:Contour, with TextSymbolizer, without Halo : the rendering seems to be fine. - without gs:Contour (here I extracted manually the contours using gdal and published a postgis layer), with TextSymbolizer, with Halo : then rendering also seems to be fine - with gs:Contour, without TextSymbolizer, with Halo : the bug
Cyril -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Possible-regression-in-the-gs-Contour-rendering-transformation-tp5271797p5272525.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohomanageengine _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
