[Geoserver-devel] Build failed in Hudson: geoserver-trunk-online #352

Hudson · January 4, 2011, 4:04am

See <http://hudson.opengeo.org/hudson/job/geoserver-trunk-online/352/>

------------------------------------------
[...truncated 13522 lines...]
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
  at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.657 sec
Running org.geoserver.wms.wms_1_3.GetFeatureInfoIntegrationTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.946 sec
Running org.geoserver.kml.KMLTransformerTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.383 sec
Running org.geoserver.wms.decoration.MapDecorationLayoutTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running org.geoserver.wms.WMSServiceExceptionTest
04 Jan 04:04:43 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: Could not find layer foobar
  at org.geoserver.wms.map.GetMapKvpRequestReader.parseLayers(GetMapKvpRequestReader.java:1154)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:197)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:73)
  at org.geoserver.ows.Dispatcher.parseRequestKVP(Dispatcher.java:1144)
  at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:482)
  at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:226)
  at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
  at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
  at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
  at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
  at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
  at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at org.geoserver.test.GeoServerAbstractTestSupport$3.service(GeoServerAbstractTestSupport.java:1090)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at com.mockrunner.mock.web.MockFilterChain.doFilter(MockFilterChain.java:50)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1109)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1050)
  at org.geoserver.test.GeoServerAbstractTestSupport.getAsServletResponse(GeoServerAbstractTestSupport.java:478)
  at org.geoserver.wms.WMSServiceExceptionTest.assertResponse111(WMSServiceExceptionTest.java:25)
  at org.geoserver.wms.WMSServiceExceptionTest.testException111(WMSServiceExceptionTest.java:17)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at junit.framework.TestCase.runTest(TestCase.java:164)
  at org.geoserver.test.GeoServerAbstractTestSupport.runTest(GeoServerAbstractTestSupport.java:132)
  at junit.framework.TestCase.runBare(TestCase.java:130)
  at junit.framework.TestResult$1.protect(TestResult.java:106)
  at junit.framework.TestResult.runProtected(TestResult.java:124)
  at junit.framework.TestResult.run(TestResult.java:109)
  at junit.framework.TestCase.run(TestCase.java:120)
  at junit.framework.TestSuite.runTest(TestSuite.java:230)
  at junit.framework.TestSuite.run(TestSuite.java:225)
  at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
  at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
  at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
04 Jan 04:04:43 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: Could not find layer foobar
  at org.geoserver.wms.map.GetMapKvpRequestReader.parseLayers(GetMapKvpRequestReader.java:1154)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:197)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:73)
  at org.geoserver.ows.Dispatcher.parseRequestKVP(Dispatcher.java:1144)
  at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:482)
  at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:226)
  at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
  at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
  at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
  at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
  at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
  at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at org.geoserver.test.GeoServerAbstractTestSupport$3.service(GeoServerAbstractTestSupport.java:1090)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at com.mockrunner.mock.web.MockFilterChain.doFilter(MockFilterChain.java:50)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1109)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1050)
  at org.geoserver.test.GeoServerAbstractTestSupport.getAsServletResponse(GeoServerAbstractTestSupport.java:478)
  at org.geoserver.wms.WMSServiceExceptionTest.assertResponse111(WMSServiceExceptionTest.java:25)
  at org.geoserver.wms.WMSServiceExceptionTest.testException110(WMSServiceExceptionTest.java:21)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at junit.framework.TestCase.runTest(TestCase.java:164)
  at org.geoserver.test.GeoServerAbstractTestSupport.runTest(GeoServerAbstractTestSupport.java:132)
  at junit.framework.TestCase.runBare(TestCase.java:130)
  at junit.framework.TestResult$1.protect(TestResult.java:106)
  at junit.framework.TestResult.runProtected(TestResult.java:124)
  at junit.framework.TestResult.run(TestResult.java:109)
  at junit.framework.TestCase.run(TestCase.java:120)
  at junit.framework.TestSuite.runTest(TestSuite.java:230)
  at junit.framework.TestSuite.run(TestSuite.java:225)
  at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
  at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
  at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
04 Jan 04:04:44 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: Could not find layer foobar
  at org.geoserver.wms.map.GetMapKvpRequestReader.parseLayers(GetMapKvpRequestReader.java:1154)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:197)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:73)
  at org.geoserver.ows.Dispatcher.parseRequestKVP(Dispatcher.java:1144)
  at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:482)
  at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:226)
  at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
  at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
  at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
  at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
  at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
  at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at org.geoserver.test.GeoServerAbstractTestSupport$3.service(GeoServerAbstractTestSupport.java:1090)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at com.mockrunner.mock.web.MockFilterChain.doFilter(MockFilterChain.java:50)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1109)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1050)
  at org.geoserver.test.GeoServerAbstractTestSupport.getAsServletResponse(GeoServerAbstractTestSupport.java:478)
  at org.geoserver.wms.WMSServiceExceptionTest.assertResponse130(WMSServiceExceptionTest.java:41)
  at org.geoserver.wms.WMSServiceExceptionTest.testException130(WMSServiceExceptionTest.java:37)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at junit.framework.TestCase.runTest(TestCase.java:164)
  at org.geoserver.test.GeoServerAbstractTestSupport.runTest(GeoServerAbstractTestSupport.java:132)
  at junit.framework.TestCase.runBare(TestCase.java:130)
  at junit.framework.TestResult$1.protect(TestResult.java:106)
  at junit.framework.TestResult.runProtected(TestResult.java:124)
  at junit.framework.TestResult.run(TestResult.java:109)
  at junit.framework.TestCase.run(TestCase.java:120)
  at junit.framework.TestSuite.runTest(TestSuite.java:230)
  at junit.framework.TestSuite.run(TestSuite.java:225)
  at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
  at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
  at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.742 sec
Running org.geoserver.wms.capabilities.CapabilitiesXmlReaderTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.geoserver.wms.map.GIFMapResponseTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec
Running org.geoserver.wms.RenderingBufferTest
04 Jan 04:04:45 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
04 Jan 04:04:45 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
04 Jan 04:04:45 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.044 sec
Running org.geoserver.wms.capabilities.GetCapabilitiesTransformerTest
04 Jan 04:04:45 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:45 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:45 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:45 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.27 sec
Running org.geoserver.wms.map.RenderedImageMapOutputFormatTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.55 sec
Running org.geoserver.wms.ProxyBaseURLIntegrationTest
04 Jan 04:04:46 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
04 Jan 04:04:46 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
04 Jan 04:04:46 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.235 sec
Running org.geoserver.kml.GeoSearchKMLTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.144 sec
Running org.geoserver.wms.WMSDisabledTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.395 sec
Running org.geoserver.wms.wms_1_1_1.GetFeatureInfoTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.77 sec
Running org.geoserver.wms.featureinfo.FeatureTimeTemplateTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.174 sec
Running org.geoserver.wms.DefaultWebMapServiceTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.162 sec
Running org.geoserver.kml.KMZMapProducerTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.236 sec
Running org.geoserver.wms.wms_1_1_1.CapabilitiesTest
04 Jan 04:04:50 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.14 sec
Running org.geoserver.wms.map.OpenLayersMapTemplateTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.183 sec
Running org.geoserver.wms.capabilities.CapabilitiesKvpReaderTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.geoserver.wms.map.QuickTileCacheTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec

Results :

Failed tests:
testValidateCapabilitiesXML(org.geoserver.wms.wms_1_3.CapabilitiesSystemTest)

Tests run: 231, Failures: 1, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.

Please refer to <http://hudson.opengeo.org/hudson/job/geoserver-trunk-online/ws/wms/target/surefire-reports> for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 13 seconds
[INFO] Finished at: Tue Jan 04 04:04:52 UTC 2011
[INFO] Final Memory: 60M/303M
[INFO] ------------------------------------------------------------------------

Gabriel_Roldan2 · January 4, 2011, 4:12am

The build failure at
org.geoserver.wms.wms_1_3.CapabilitiesSystemTest.testValidateCapabilitiesXML() _seems_ to come from some recent change in some geotool's coverage class?

The error message is: AssertionFailedError: WMS 1.3.0 capabilities
validation error: cvc-maxInclusive-valid: Value '180.25' is not
facet-valid with respect to maxInclusive '1.8E2' for type
'longitudeType'.

Which is consistent with the lat long bbox for the wcs:World layer:
<EX_GeographicBoundingBox>
   <westBoundLongitude>-179.75</westBoundLongitude>
   <eastBoundLongitude>180.25</eastBoundLongitude>
   <southBoundLatitude>-90.25</southBoundLatitude>
   <northBoundLatitude>89.75</northBoundLatitude>
</EX_GeographicBoundingBox>

Any easy fix/workaround that someone could think of (besides getting rid
of the validation test)?

Cheers,
Gabriel

On Tue, 2011-01-04 at 04:04 +0000, Hudson wrote:

See <http://hudson.opengeo.org/hudson/job/geoserver-trunk-online/352/>

------------------------------------------
[...truncated 13522 lines...]
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
  at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.657 sec
Running org.geoserver.wms.wms_1_3.GetFeatureInfoIntegrationTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.946 sec
Running org.geoserver.kml.KMLTransformerTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.383 sec
Running org.geoserver.wms.decoration.MapDecorationLayoutTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running org.geoserver.wms.WMSServiceExceptionTest
04 Jan 04:04:43 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: Could not find layer foobar
  at org.geoserver.wms.map.GetMapKvpRequestReader.parseLayers(GetMapKvpRequestReader.java:1154)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:197)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:73)
  at org.geoserver.ows.Dispatcher.parseRequestKVP(Dispatcher.java:1144)
  at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:482)
  at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:226)
  at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
  at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
  at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
  at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
  at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
  at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at org.geoserver.test.GeoServerAbstractTestSupport$3.service(GeoServerAbstractTestSupport.java:1090)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at com.mockrunner.mock.web.MockFilterChain.doFilter(MockFilterChain.java:50)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1109)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1050)
  at org.geoserver.test.GeoServerAbstractTestSupport.getAsServletResponse(GeoServerAbstractTestSupport.java:478)
  at org.geoserver.wms.WMSServiceExceptionTest.assertResponse111(WMSServiceExceptionTest.java:25)
  at org.geoserver.wms.WMSServiceExceptionTest.testException111(WMSServiceExceptionTest.java:17)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at junit.framework.TestCase.runTest(TestCase.java:164)
  at org.geoserver.test.GeoServerAbstractTestSupport.runTest(GeoServerAbstractTestSupport.java:132)
  at junit.framework.TestCase.runBare(TestCase.java:130)
  at junit.framework.TestResult$1.protect(TestResult.java:106)
  at junit.framework.TestResult.runProtected(TestResult.java:124)
  at junit.framework.TestResult.run(TestResult.java:109)
  at junit.framework.TestCase.run(TestCase.java:120)
  at junit.framework.TestSuite.runTest(TestSuite.java:230)
  at junit.framework.TestSuite.run(TestSuite.java:225)
  at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
  at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
  at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
04 Jan 04:04:43 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: Could not find layer foobar
  at org.geoserver.wms.map.GetMapKvpRequestReader.parseLayers(GetMapKvpRequestReader.java:1154)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:197)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:73)
  at org.geoserver.ows.Dispatcher.parseRequestKVP(Dispatcher.java:1144)
  at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:482)
  at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:226)
  at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
  at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
  at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
  at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
  at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
  at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at org.geoserver.test.GeoServerAbstractTestSupport$3.service(GeoServerAbstractTestSupport.java:1090)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at com.mockrunner.mock.web.MockFilterChain.doFilter(MockFilterChain.java:50)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1109)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1050)
  at org.geoserver.test.GeoServerAbstractTestSupport.getAsServletResponse(GeoServerAbstractTestSupport.java:478)
  at org.geoserver.wms.WMSServiceExceptionTest.assertResponse111(WMSServiceExceptionTest.java:25)
  at org.geoserver.wms.WMSServiceExceptionTest.testException110(WMSServiceExceptionTest.java:21)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at junit.framework.TestCase.runTest(TestCase.java:164)
  at org.geoserver.test.GeoServerAbstractTestSupport.runTest(GeoServerAbstractTestSupport.java:132)
  at junit.framework.TestCase.runBare(TestCase.java:130)
  at junit.framework.TestResult$1.protect(TestResult.java:106)
  at junit.framework.TestResult.runProtected(TestResult.java:124)
  at junit.framework.TestResult.run(TestResult.java:109)
  at junit.framework.TestCase.run(TestCase.java:120)
  at junit.framework.TestSuite.runTest(TestSuite.java:230)
  at junit.framework.TestSuite.run(TestSuite.java:225)
  at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
  at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
  at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
04 Jan 04:04:44 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: Could not find layer foobar
  at org.geoserver.wms.map.GetMapKvpRequestReader.parseLayers(GetMapKvpRequestReader.java:1154)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:197)
  at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpRequestReader.java:73)
  at org.geoserver.ows.Dispatcher.parseRequestKVP(Dispatcher.java:1144)
  at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:482)
  at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:226)
  at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
  at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
  at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
  at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
  at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
  at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at org.geoserver.test.GeoServerAbstractTestSupport$3.service(GeoServerAbstractTestSupport.java:1090)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at com.mockrunner.mock.web.MockFilterChain.doFilter(MockFilterChain.java:50)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1109)
  at org.geoserver.test.GeoServerAbstractTestSupport.dispatch(GeoServerAbstractTestSupport.java:1050)
  at org.geoserver.test.GeoServerAbstractTestSupport.getAsServletResponse(GeoServerAbstractTestSupport.java:478)
  at org.geoserver.wms.WMSServiceExceptionTest.assertResponse130(WMSServiceExceptionTest.java:41)
  at org.geoserver.wms.WMSServiceExceptionTest.testException130(WMSServiceExceptionTest.java:37)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at junit.framework.TestCase.runTest(TestCase.java:164)
  at org.geoserver.test.GeoServerAbstractTestSupport.runTest(GeoServerAbstractTestSupport.java:132)
  at junit.framework.TestCase.runBare(TestCase.java:130)
  at junit.framework.TestResult$1.protect(TestResult.java:106)
  at junit.framework.TestResult.runProtected(TestResult.java:124)
  at junit.framework.TestResult.run(TestResult.java:109)
  at junit.framework.TestCase.run(TestCase.java:120)
  at junit.framework.TestSuite.runTest(TestSuite.java:230)
  at junit.framework.TestSuite.run(TestSuite.java:225)
  at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
  at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
  at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:592)
  at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
  at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.742 sec
Running org.geoserver.wms.capabilities.CapabilitiesXmlReaderTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.geoserver.wms.map.GIFMapResponseTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec
Running org.geoserver.wms.RenderingBufferTest
04 Jan 04:04:45 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
04 Jan 04:04:45 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
04 Jan 04:04:45 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.044 sec
Running org.geoserver.wms.capabilities.GetCapabilitiesTransformerTest
04 Jan 04:04:45 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:45 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:45 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:45 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
04 Jan 04:04:46 ERROR [org.geoserver] - Extension lookup occured, but ApplicationContext is unset.
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.27 sec
Running org.geoserver.wms.map.RenderedImageMapOutputFormatTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.55 sec
Running org.geoserver.wms.ProxyBaseURLIntegrationTest
04 Jan 04:04:46 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
04 Jan 04:04:46 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
04 Jan 04:04:46 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.235 sec
Running org.geoserver.kml.GeoSearchKMLTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.144 sec
Running org.geoserver.wms.WMSDisabledTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.395 sec
Running org.geoserver.wms.wms_1_1_1.GetFeatureInfoTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.77 sec
Running org.geoserver.wms.featureinfo.FeatureTimeTemplateTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.174 sec
Running org.geoserver.wms.DefaultWebMapServiceTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.162 sec
Running org.geoserver.kml.KMZMapProducerTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.236 sec
Running org.geoserver.wms.wms_1_1_1.CapabilitiesTest
04 Jan 04:04:50 ERROR [geotools.map] - Call MapContent dispose() to prevent memory leaks
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.14 sec
Running org.geoserver.wms.map.OpenLayersMapTemplateTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.183 sec
Running org.geoserver.wms.capabilities.CapabilitiesKvpReaderTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.geoserver.wms.map.QuickTileCacheTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec

Results :

Failed tests:
  testValidateCapabilitiesXML(org.geoserver.wms.wms_1_3.CapabilitiesSystemTest)

Tests run: 231, Failures: 1, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.

Please refer to <http://hudson.opengeo.org/hudson/job/geoserver-trunk-online/ws/wms/target/surefire-reports> for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 13 seconds
[INFO] Finished at: Tue Jan 04 04:04:52 UTC 2011
[INFO] Final Memory: 60M/303M
[INFO] ------------------------------------------------------------------------

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Gabriel Roldan
groldan@anonymised.com
Expert service straight from the developers

Andrea_Aime4 · January 4, 2011, 7:54am

On Tue, Jan 4, 2011 at 5:12 AM, Gabriel Roldán <groldan@anonymised.com> wrote:

The build failure at
org.geoserver.wms.wms_1_3.CapabilitiesSystemTest.testValidateCapabilitiesXML() _seems_ to come from some recent change in some geotool's coverage class?

The error message is: AssertionFailedError: WMS 1.3.0 capabilities
validation error: cvc-maxInclusive-valid: Value '180.25' is not
facet-valid with respect to maxInclusive '1.8E2' for type
'longitudeType'.

Which is consistent with the lat long bbox for the wcs:World layer:
<EX_GeographicBoundingBox>
<westBoundLongitude>-179.75</westBoundLongitude>
<eastBoundLongitude>180.25</eastBoundLongitude>
<southBoundLatitude>-90.25</southBoundLatitude>
<northBoundLatitude>89.75</northBoundLatitude>
</EX_GeographicBoundingBox>

Any easy fix/workaround that someone could think of (besides getting rid
of the validation test)?

As far as I can see this may be a result of the fix for
http://jira.codehaus.org/browse/GEOT-3368.

I looked up the file and run gdalinfo on it:

aaime@anonymised.com:~/devel/git-gs/src/main$ gdalinfo
src/test/java/org/geoserver/data/test/world.tiff
Driver: GTiff/GeoTIFF
Files: src/test/java/org/geoserver/data/test/world.tiff
Size is 720, 360
Coordinate System is:
GEOGCS["WGS 84",
    DATUM["WGS_1984",
        SPHEROID["WGS 84",6378137,298.257223563,
            AUTHORITY["EPSG","7030"]],
        AUTHORITY["EPSG","6326"]],
    PRIMEM["Greenwich",0],
    UNIT["degree",0.0174532925199433],
    AUTHORITY["EPSG","4326"]]
Origin = (-179.750000000000000,89.750000000000000)
Pixel Size = (0.500000000000000,-0.500000000000000)
Metadata:
  TIFFTAG_XRESOLUTION=1
  TIFFTAG_YRESOLUTION=1
  TIFFTAG_RESOLUTIONUNIT=1 (unitless)
  AREA_OR_POINT=Point
Image Structure Metadata:
  COMPRESSION=DEFLATE
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left (-179.7500000, 89.7500000) (179d45'0.00"W, 89d45'0.00"N)
Lower Left (-179.7500000, -90.2500000) (179d45'0.00"W, 90d15'0.00"S)
Upper Right ( 180.2500000, 89.7500000) (180d15'0.00"E, 89d45'0.00"N)
Lower Right ( 180.2500000, -90.2500000) (180d15'0.00"E, 90d15'0.00"S)
Center ( 0.2500000, -0.2500000) ( 0d15'0.00"E, 0d15'0.00"S)
Band 1 Block=256x256 Type=Byte, ColorInterp=Red
Band 2 Block=256x256 Type=Byte, ColorInterp=Green
Band 3 Block=256x256 Type=Byte, ColorInterp=Blue

As far as I can see the code is reporting the true bounds, which as you say
are going beyond the natural range of the lon/lat ordinates.
It seems to me we have to fix the data, and eventually any test that
depends on the data having the wrong coordinates

Simone, what do you think?

Cheers
Andrea

-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------

Andrea_Aime4 · January 4, 2011, 8:28am

On Tue, Jan 4, 2011 at 8:54 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:

On Tue, Jan 4, 2011 at 5:12 AM, Gabriel Roldán <groldan@anonymised.com> wrote:

The build failure at
org.geoserver.wms.wms_1_3.CapabilitiesSystemTest.testValidateCapabilitiesXML() _seems_ to come from some recent change in some geotool's coverage class?

The error message is: AssertionFailedError: WMS 1.3.0 capabilities
validation error: cvc-maxInclusive-valid: Value '180.25' is not
facet-valid with respect to maxInclusive '1.8E2' for type
'longitudeType'.

Which is consistent with the lat long bbox for the wcs:World layer:
<EX_GeographicBoundingBox>
<westBoundLongitude>-179.75</westBoundLongitude>
<eastBoundLongitude>180.25</eastBoundLongitude>
<southBoundLatitude>-90.25</southBoundLatitude>
<northBoundLatitude>89.75</northBoundLatitude>
</EX_GeographicBoundingBox>

Any easy fix/workaround that someone could think of (besides getting rid
of the validation test)?

As far as I can see this may be a result of the fix for
http://jira.codehaus.org/browse/GEOT-3368.

I looked up the file and run gdalinfo on it:

aaime@anonymised.com:~/devel/git-gs/src/main$ gdalinfo
src/test/java/org/geoserver/data/test/world.tiff
Driver: GTiff/GeoTIFF
Files: src/test/java/org/geoserver/data/test/world.tiff
Size is 720, 360
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (-179.750000000000000,89.750000000000000)
Pixel Size = (0.500000000000000,-0.500000000000000)
Metadata:
TIFFTAG_XRESOLUTION=1
TIFFTAG_YRESOLUTION=1
TIFFTAG_RESOLUTIONUNIT=1 (unitless)
AREA_OR_POINT=Point
Image Structure Metadata:
COMPRESSION=DEFLATE
INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left (-179.7500000, 89.7500000) (179d45'0.00"W, 89d45'0.00"N)
Lower Left (-179.7500000, -90.2500000) (179d45'0.00"W, 90d15'0.00"S)
Upper Right ( 180.2500000, 89.7500000) (180d15'0.00"E, 89d45'0.00"N)
Lower Right ( 180.2500000, -90.2500000) (180d15'0.00"E, 90d15'0.00"S)
Center ( 0.2500000, -0.2500000) ( 0d15'0.00"E, 0d15'0.00"S)
Band 1 Block=256x256 Type=Byte, ColorInterp=Red
Band 2 Block=256x256 Type=Byte, ColorInterp=Green
Band 3 Block=256x256 Type=Byte, ColorInterp=Blue

As far as I can see the code is reporting the true bounds, which as you say
are going beyond the natural range of the lon/lat ordinates.
It seems to me we have to fix the data, and eventually any test that
depends on the data having the wrong coordinates

Simone, what do you think?

Mumble mumble. I tried to regenerate that file, by looking at it it's
pretty clear it was generated by a GetMap request in GeoTiff format.
Something like this one:

http://localhost:8080/geoserver/wms?service=WMS&version=1.1.0&request=GetMap&layers=topp:ne_countries&styles=&bbox=-180.0,-90.0,180.0,90&width=720&height=360&srs=EPSG:4326&format=image/geotiff

(which is using natural earth continents).

However the GeoTiff file generated by it still has the wrong bounds:

Corner Coordinates:
Upper Left (-179.7500000, 89.7500000) (179d45'0.00"W, 89d45'0.00"N)
Lower Left (-179.7500000, -90.2500000) (179d45'0.00"W, 90d15'0.00"S)
Upper Right ( 180.2500000, 89.7500000) (180d15'0.00"E, 89d45'0.00"N)
Lower Right ( 180.2500000, -90.2500000) (180d15'0.00"E, 90d15'0.00"S)
Center ( 0.2500000, -0.2500000) ( 0d15'0.00"E, 0d15'0.00"S)

I guess that probably before the read and write side compensated each other,
whilst now the write side is still off? Odd that it's quarter of a
pixel instead of
the more common half a pixel issue

Cheers
Andrea

-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------

Simone_Giannecchini3 · January 4, 2011, 8:28am

Ciao a tutti,
yeah, this is related to the jira I closed yesterday.
Let me run a sanity check on the data, however beware that GDAL has
only recently addressed the PixelIsArea vs PixelIsPoint issue,
therefore sometimes there is an half pixel translation in data.

Ciao,
Simone.
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313
mob: +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini
http://twitter.com/simogeo

-------------------------------------------------------

On Tue, Jan 4, 2011 at 8:54 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:

On Tue, Jan 4, 2011 at 5:12 AM, Gabriel Roldán <groldan@anonymised.com> wrote:

The build failure at
org.geoserver.wms.wms_1_3.CapabilitiesSystemTest.testValidateCapabilitiesXML() _seems_ to come from some recent change in some geotool's coverage class?

The error message is: AssertionFailedError: WMS 1.3.0 capabilities
validation error: cvc-maxInclusive-valid: Value '180.25' is not
facet-valid with respect to maxInclusive '1.8E2' for type
'longitudeType'.

Which is consistent with the lat long bbox for the wcs:World layer:
<EX_GeographicBoundingBox>
<westBoundLongitude>-179.75</westBoundLongitude>
<eastBoundLongitude>180.25</eastBoundLongitude>
<southBoundLatitude>-90.25</southBoundLatitude>
<northBoundLatitude>89.75</northBoundLatitude>
</EX_GeographicBoundingBox>

Any easy fix/workaround that someone could think of (besides getting rid
of the validation test)?

As far as I can see this may be a result of the fix for
http://jira.codehaus.org/browse/GEOT-3368.

I looked up the file and run gdalinfo on it:

aaime@anonymised.com:~/devel/git-gs/src/main$ gdalinfo
src/test/java/org/geoserver/data/test/world.tiff
Driver: GTiff/GeoTIFF
Files: src/test/java/org/geoserver/data/test/world.tiff
Size is 720, 360
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (-179.750000000000000,89.750000000000000)
Pixel Size = (0.500000000000000,-0.500000000000000)
Metadata:
TIFFTAG_XRESOLUTION=1
TIFFTAG_YRESOLUTION=1
TIFFTAG_RESOLUTIONUNIT=1 (unitless)
AREA_OR_POINT=Point
Image Structure Metadata:
COMPRESSION=DEFLATE
INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left (-179.7500000, 89.7500000) (179d45'0.00"W, 89d45'0.00"N)
Lower Left (-179.7500000, -90.2500000) (179d45'0.00"W, 90d15'0.00"S)
Upper Right ( 180.2500000, 89.7500000) (180d15'0.00"E, 89d45'0.00"N)
Lower Right ( 180.2500000, -90.2500000) (180d15'0.00"E, 90d15'0.00"S)
Center ( 0.2500000, -0.2500000) ( 0d15'0.00"E, 0d15'0.00"S)
Band 1 Block=256x256 Type=Byte, ColorInterp=Red
Band 2 Block=256x256 Type=Byte, ColorInterp=Green
Band 3 Block=256x256 Type=Byte, ColorInterp=Blue

As far as I can see the code is reporting the true bounds, which as you say
are going beyond the natural range of the lon/lat ordinates.
It seems to me we have to fix the data, and eventually any test that
depends on the data having the wrong coordinates

Simone, what do you think?

Cheers
Andrea

-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Andrea_Aime4 · January 4, 2011, 8:29am

On Tue, Jan 4, 2011 at 9:28 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:

Mumble mumble. I tried to regenerate that file, by looking at it it's
pretty clear it was generated by a GetMap request in GeoTiff format.
Something like this one:

http://localhost:8080/geoserver/wms?service=WMS&version=1.1.0&request=GetMap&layers=topp:ne_countries&styles=&bbox=-180.0,-90.0,180.0,90&width=720&height=360&srs=EPSG:4326&format=image/geotiff

Oh, btw, you don't need that layer to reproduce the issue, this
request will show the same issue as well:

http://localhost:8080/geoserver/wms?service=WMS&version=1.1.0&request=GetMap&layers=topp:states&styles=&bbox=-180.0,-90.0,180.0,90&width=720&height=360&srs=EPSG:4326&format=image/geotiff

Cheers
Andrea

-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------

Andrea_Aime4 · January 4, 2011, 8:41am

On Tue, Jan 4, 2011 at 9:28 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:

Corner Coordinates:
Upper Left (-179.7500000, 89.7500000) (179d45'0.00"W, 89d45'0.00"N)
Lower Left (-179.7500000, -90.2500000) (179d45'0.00"W, 90d15'0.00"S)
Upper Right ( 180.2500000, 89.7500000) (180d15'0.00"E, 89d45'0.00"N)
Lower Right ( 180.2500000, -90.2500000) (180d15'0.00"E, 90d15'0.00"S)
Center ( 0.2500000, -0.2500000) ( 0d15'0.00"E, 0d15'0.00"S)

I guess that probably before the read and write side compensated each other,
whilst now the write side is still off? Odd that it's quarter of a
pixel instead of
the more common half a pixel issue

Correction, it's half a pixel since the pixel size is 0.5

In any case, there is a mismatch between read and write sides now, I ask
GeoServer to write the world bounds (-180,-90,180,90), write it down to disk
as world.tiff, and what is read back by GeoServer is apparently
shifted half a pixel

Cheers
Andrea

-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------

Simone_Giannecchini3 · January 4, 2011, 3:21pm

Everything should be fine now, althought the original geotiff needs to be fixed.

As a side effect, I have change the way we write geotiff files, still
respecting the spec.
Now we write them with the corner convention, so that also older
versions of gdal/qgis/arcmap/etc. are happy (gdal in the past was
not interpreting the center convetion correctly).

Ciao,
Simone
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313
mob: +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini
http://twitter.com/simogeo

-------------------------------------------------------

On Tue, Jan 4, 2011 at 9:41 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:

On Tue, Jan 4, 2011 at 9:28 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:

Corner Coordinates:
Upper Left (-179.7500000, 89.7500000) (179d45'0.00"W, 89d45'0.00"N)
Lower Left (-179.7500000, -90.2500000) (179d45'0.00"W, 90d15'0.00"S)
Upper Right ( 180.2500000, 89.7500000) (180d15'0.00"E, 89d45'0.00"N)
Lower Right ( 180.2500000, -90.2500000) (180d15'0.00"E, 90d15'0.00"S)
Center ( 0.2500000, -0.2500000) ( 0d15'0.00"E, 0d15'0.00"S)

I guess that probably before the read and write side compensated each other,
whilst now the write side is still off? Odd that it's quarter of a
pixel instead of
the more common half a pixel issue

Correction, it's half a pixel since the pixel size is 0.5

In any case, there is a mismatch between read and write sides now, I ask
GeoServer to write the world bounds (-180,-90,180,90), write it down to disk
as world.tiff, and what is read back by GeoServer is apparently
shifted half a pixel

Cheers
Andrea

-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Andrea_Aime4 · January 4, 2011, 3:39pm

On Tue, Jan 4, 2011 at 4:21 PM, Simone Giannecchini
<simone.giannecchini@anonymised.com> wrote:

Everything should be fine now, althought the original geotiff needs to be fixed.

Actually, nope, that was not necessary either. As you suggested the
bounds were misread
by a change that forced a fixed pixel interpretation, once that was
made to respect the
one in the geotiff reader the tests went back to work without the need to change
the world.tiff file.

Cheers
Andrea

-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-----------------------------------------------------

Gabriel_Roldan2 · January 4, 2011, 3:52pm

Thanks Simone and Andrea.

So, if I read correctly, with your change there should be absolutely no
behavior change, just that the gtiff writer will properly report bounds,
whether the original data comes with center pixel or corner pixel
bounds?

Cheers,
Gabriel
On Tue, 2011-01-04 at 16:21 +0100, Simone Giannecchini wrote:

Everything should be fine now, althought the original geotiff needs to be fixed.

As a side effect, I have change the way we write geotiff files, still
respecting the spec.
Now we write them with the corner convention, so that also older
versions of gdal/qgis/arcmap/etc. are happy (gdal in the past was
not interpreting the center convetion correctly).

Ciao,
Simone
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313
mob: +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini
http://twitter.com/simogeo

-------------------------------------------------------

On Tue, Jan 4, 2011 at 9:41 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:
> On Tue, Jan 4, 2011 at 9:28 AM, Andrea Aime
> <andrea.aime@anonymised.com> wrote:
>> Corner Coordinates:
>> Upper Left (-179.7500000, 89.7500000) (179d45'0.00"W, 89d45'0.00"N)
>> Lower Left (-179.7500000, -90.2500000) (179d45'0.00"W, 90d15'0.00"S)
>> Upper Right ( 180.2500000, 89.7500000) (180d15'0.00"E, 89d45'0.00"N)
>> Lower Right ( 180.2500000, -90.2500000) (180d15'0.00"E, 90d15'0.00"S)
>> Center ( 0.2500000, -0.2500000) ( 0d15'0.00"E, 0d15'0.00"S)
>>
>> I guess that probably before the read and write side compensated each other,
>> whilst now the write side is still off? Odd that it's quarter of a
>> pixel instead of
>> the more common half a pixel issue
>
> Correction, it's half a pixel since the pixel size is 0.5
>
> In any case, there is a mismatch between read and write sides now, I ask
> GeoServer to write the world bounds (-180,-90,180,90), write it down to disk
> as world.tiff, and what is read back by GeoServer is apparently
> shifted half a pixel
>
> Cheers
> Andrea
>
> -----------------------------------------------------
> Ing. Andrea Aime
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584962313
> fax: +39 0584962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -----------------------------------------------------
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

--
Gabriel Roldan
groldan@anonymised.com
Expert service straight from the developers

Simone_Giannecchini3 · January 4, 2011, 4:09pm

Ciao Gabriel,
sorry for the confusion and for mixing topics.

The problems you had was due to a bug I introduced a few days ago
while trying to reduce the amount of code we had around for
managing geotiff metadata. That is fixed now.

Aside from that I also changed the behavior of the writer, so that we
still respect the geotiff spec but we use a convention that makes
happy other software like gdal which in the past (at least IMHO) did
not interprete correctly the pixel datum.

Simone.
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313
mob: +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini
http://twitter.com/simogeo

-------------------------------------------------------

On Tue, Jan 4, 2011 at 4:52 PM, Gabriel Roldán <groldan@anonymised.com> wrote:

Thanks Simone and Andrea.

So, if I read correctly, with your change there should be absolutely no
behavior change, just that the gtiff writer will properly report bounds,
whether the original data comes with center pixel or corner pixel
bounds?

Cheers,
Gabriel
On Tue, 2011-01-04 at 16:21 +0100, Simone Giannecchini wrote:

Everything should be fine now, althought the original geotiff needs to be fixed.

As a side effect, I have change the way we write geotiff files, still
respecting the spec.
Now we write them with the corner convention, so that also older
versions of gdal/qgis/arcmap/etc. are happy (gdal in the past was
not interpreting the center convetion correctly).

Ciao,
Simone
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313
mob: +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini
http://twitter.com/simogeo

-------------------------------------------------------

On Tue, Jan 4, 2011 at 9:41 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:
> On Tue, Jan 4, 2011 at 9:28 AM, Andrea Aime
> <andrea.aime@anonymised.com> wrote:
>> Corner Coordinates:
>> Upper Left (-179.7500000, 89.7500000) (179d45'0.00"W, 89d45'0.00"N)
>> Lower Left (-179.7500000, -90.2500000) (179d45'0.00"W, 90d15'0.00"S)
>> Upper Right ( 180.2500000, 89.7500000) (180d15'0.00"E, 89d45'0.00"N)
>> Lower Right ( 180.2500000, -90.2500000) (180d15'0.00"E, 90d15'0.00"S)
>> Center ( 0.2500000, -0.2500000) ( 0d15'0.00"E, 0d15'0.00"S)
>>
>> I guess that probably before the read and write side compensated each other,
>> whilst now the write side is still off? Odd that it's quarter of a
>> pixel instead of
>> the more common half a pixel issue
>
> Correction, it's half a pixel since the pixel size is 0.5
>
> In any case, there is a mismatch between read and write sides now, I ask
> GeoServer to write the world bounds (-180,-90,180,90), write it down to disk
> as world.tiff, and what is read back by GeoServer is apparently
> shifted half a pixel
>
> Cheers
> Andrea
>
> -----------------------------------------------------
> Ing. Andrea Aime
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584962313
> fax: +39 0584962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -----------------------------------------------------
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

--
Gabriel Roldan
groldan@anonymised.com
Expert service straight from the developers

Gabriel_Roldan2 · January 4, 2011, 5:15pm

Ciao Simone,

not a problem, I got the two concerns separated.

The reason I ask is because I've been working on a "quarter to half"
pixel mismatch in raster outputs from arcsde rasters, and as I managed
to fix the mismatch at the arcsde plugin (it was assuming pixel corner
whilst arcsde reports bounds based on pixel center), I figured out once
that was fixed, the remaining apparent mismatch was due to the inherent
nature of nearest neighbour interpolation, the fact that geoserver
almost always needs to resample the coverage, and now I wondered if this
geotiff writer mismatch had something to do too (as one method of
testing was saving two overlapping geotiff responses to files and
loading them in udig), and if so, just wanted to make sure (though I'm
pretty confident about) that your recent fix won't have a negative
impact on such an output, like in if the originating coverage (comming
from arcsde) reports bounds with pixel center datum, the resulting
geotiff with pixel corner datum will properly be calculated.

Again, just double checking.

Cheers,
Gabriel

On Tue, 2011-01-04 at 17:09 +0100, Simone Giannecchini wrote:

Ciao Gabriel,
sorry for the confusion and for mixing topics.

The problems you had was due to a bug I introduced a few days ago
while trying to reduce the amount of code we had around for
managing geotiff metadata. That is fixed now.

Aside from that I also changed the behavior of the writer, so that we
still respect the geotiff spec but we use a convention that makes
happy other software like gdal which in the past (at least IMHO) did
not interprete correctly the pixel datum.

Simone.
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584962313
fax: +39 0584962313
mob: +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/simonegiannecchini
http://twitter.com/simogeo

-------------------------------------------------------

On Tue, Jan 4, 2011 at 4:52 PM, Gabriel Roldán <groldan@anonymised.com> wrote:
> Thanks Simone and Andrea.
>
> So, if I read correctly, with your change there should be absolutely no
> behavior change, just that the gtiff writer will properly report bounds,
> whether the original data comes with center pixel or corner pixel
> bounds?
>
> Cheers,
> Gabriel
> On Tue, 2011-01-04 at 16:21 +0100, Simone Giannecchini wrote:
>> Everything should be fine now, althought the original geotiff needs to be fixed.
>>
>> As a side effect, I have change the way we write geotiff files, still
>> respecting the spec.
>> Now we write them with the corner convention, so that also older
>> versions of gdal/qgis/arcmap/etc. are happy (gdal in the past was
>> not interpreting the center convetion correctly).
>>
>> Ciao,
>> Simone
>> -------------------------------------------------------
>> Ing. Simone Giannecchini
>> GeoSolutions S.A.S.
>> Founder
>>
>> Via Poggio alle Viti 1187
>> 55054 Massarosa (LU)
>> Italy
>>
>> phone: +39 0584962313
>> fax: +39 0584962313
>> mob: +39 333 8128928
>>
>>
>> http://www.geo-solutions.it
>> http://geo-solutions.blogspot.com/
>> http://www.linkedin.com/in/simonegiannecchini
>> http://twitter.com/simogeo
>>
>> -------------------------------------------------------
>>
>>
>>
>> On Tue, Jan 4, 2011 at 9:41 AM, Andrea Aime
>> <andrea.aime@anonymised.com> wrote:
>> > On Tue, Jan 4, 2011 at 9:28 AM, Andrea Aime
>> > <andrea.aime@anonymised.com> wrote:
>> >> Corner Coordinates:
>> >> Upper Left (-179.7500000, 89.7500000) (179d45'0.00"W, 89d45'0.00"N)
>> >> Lower Left (-179.7500000, -90.2500000) (179d45'0.00"W, 90d15'0.00"S)
>> >> Upper Right ( 180.2500000, 89.7500000) (180d15'0.00"E, 89d45'0.00"N)
>> >> Lower Right ( 180.2500000, -90.2500000) (180d15'0.00"E, 90d15'0.00"S)
>> >> Center ( 0.2500000, -0.2500000) ( 0d15'0.00"E, 0d15'0.00"S)
>> >>
>> >> I guess that probably before the read and write side compensated each other,
>> >> whilst now the write side is still off? Odd that it's quarter of a
>> >> pixel instead of
>> >> the more common half a pixel issue
>> >
>> > Correction, it's half a pixel since the pixel size is 0.5
>> >
>> > In any case, there is a mismatch between read and write sides now, I ask
>> > GeoServer to write the world bounds (-180,-90,180,90), write it down to disk
>> > as world.tiff, and what is read back by GeoServer is apparently
>> > shifted half a pixel
>> >
>> > Cheers
>> > Andrea
>> >
>> > -----------------------------------------------------
>> > Ing. Andrea Aime
>> > Senior Software Engineer
>> >
>> > GeoSolutions S.A.S.
>> > Via Poggio alle Viti 1187
>> > 55054 Massarosa (LU)
>> > Italy
>> >
>> > phone: +39 0584962313
>> > fax: +39 0584962313
>> >
>> > http://www.geo-solutions.it
>> > http://geo-solutions.blogspot.com/
>> > http://www.linkedin.com/in/andreaaime
>> > http://twitter.com/geowolf
>> >
>> > -----------------------------------------------------
>> >
>> > ------------------------------------------------------------------------------
>> > Learn how Oracle Real Application Clusters (RAC) One Node allows customers
>> > to consolidate database storage, standardize their database environment, and,
>> > should the need arise, upgrade to a full multi-node Oracle RAC database
>> > without downtime or disruption
>> > http://p.sf.net/sfu/oracle-sfdevnl
>> > _______________________________________________
>> > Geoserver-devel mailing list
>> > Geoserver-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>> >
>
> --
> Gabriel Roldan
> groldan@anonymised.com
> Expert service straight from the developers
>
>
>

--
Gabriel Roldan
groldan@anonymised.com
Expert service straight from the developers

Hudson · January 5, 2011, 4:11am

See <http://hudson.opengeo.org/hudson/job/geoserver-trunk-online/353/>