It appears that the WMS render engine has a problem with "short" lines (or "sort" lines in multi-line objects) that cause it to crash on the 2.0.1 general release version for lat-lon coordinate sets.
My assumption is that somewhere a Java float instead of double to track co-ordinate values, and in lat/lon space co-ordinate values round down to the same value and cause the crash. This assumption is based on my filtering line items based on length from Oracle Spatial which are used to feed a WMS session. Where this first raised it's head was with a Google tile cache (GWC) pulling WMS from Geoserver. I noticed that if the same data was rendered for via WMS for a 256x256 tile it would work at certain lengths (around 3M). Then when GWC pulled the same area, I needed to bump that up. Then I asked WMS to render a 1024x1024 (4x4) map and found that I needed to change the minimum length to about 13M. So size of the map image also influences the minimum length of the line required before a crash occurs. So for now I have to have only allow simple lines (singles not multi) and only lines longer than 13 Meters for WMS rendering. Of course this means I am missing a fair number of these shorter objects altogether. Is this currently a known bug? Thanks in advance, Bryan -- View this message in context: http://old.nabble.com/WMS-Render-bug-for-lat-lon-short-lines-tp27773110p27773110.html Sent from the GeoServer - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
