[Geotools-devel] [jira] Created: (GEOT-2810) GridCoverageRenderer still not able to handle rotated coverages.

2009-10-29 Thread Per S Hustad (JIRA)
Components: core render Affects Versions: 2.5.8 Environment: java version "1.6.0_16" Java(TM) SE Runtime Environment (build 1.6.0_16-b01) Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode) Windows XP 64 bit Reporter: Per S Hustad Assignee: A

[Geotools-devel] [jira] Reopened: (GEOT-2534) StreamingRenderer does not handle rotated views

2009-10-05 Thread Per S Hustad (JIRA)
[ http://jira.codehaus.org/browse/GEOT-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Per S Hustad reopened GEOT-2534: This is really a bit embarrassing but I've detected a bug in the patch provided for GEOT-2534

[Geotools-devel] [jira] Created: (GEOT-2538) GEOT-2073 fix intoduced severere performance degradation due to open SUN Bug ID:6568969

2009-06-08 Thread Per S Hustad (JIRA)
: GeoTools Issue Type: Bug Components: core render, core styling Environment: WinXP, java 1.6 Reporter: Per S Hustad Assignee: Andrea Aime Attachments: patch-stroke-bug.txt, StrokeBugDemo.java The Stroke fix for GEOT-2073 introduced in

[Geotools-devel] [jira] Created: (GEOT-2534) StreamingRenderer does not handle rotated views

2009-06-05 Thread Per S Hustad (JIRA)
Versions: 2.5.5 Environment: Windows XP, Java 1.6.0_13 Reporter: Per S Hustad Assignee: Andrea Aime Attachments: ZoomPaneMapViewer.java The {{StreamingRenderer}} does handle rotated view as the attached program demonstrates. This has been known for several

[Geotools-devel] [jira] Created: (GEOT-2305) Patch: Support for DIMENSION and EXTEND in WMSCapabilities

2009-01-26 Thread Per Engstrom (JIRA)
Components: core main Affects Versions: 2.5.2 Environment: Patch created with Eclipse 3.4.1 and Subclipse (SVN Team Provide Core) 1.4.7 plugin Reporter: Per Engstrom Assignee: Jody Garnett Priority: Minor Attachments: Geotools-2.5.2-DIM_PATCH.txt

[Geotools-devel] GeoTools 2.3.0: Nasty bug in SubFeatureCollection.isEmpty() ?

2007-04-10 Thread per
{ return iterator.hasNext(); } finally { close( iterator ); } } It looks like (and yes - its the case) that the "isEmpty" method returns "true" if the iterator has some data - and "false"