Re: [Geoserver-users] GeoWebCache EPSG:3857 issues
(cc'ing back the user list, please keep messages there too for future reference) Hum... nope does not ring a bell... the code is going through a double transformation, from web mercator to geographic, and then to UTM, and failing to do so, but I don't have reports of similar issues. I've tried a quick seed of an image in EPSG:32633 (also a UTM) in 900913, zoom levels 0 to 15, without any hiccup... wondering if it's related somehow to the data or the server configuration? If you attach a geotiff in EPSG:26915 that would cause seeding to fail, and attach in a Jira ticket, it may be useful. Cheers Andrea On Thu, Feb 27, 2020 at 7:44 AM Terry N.Brown wrote: > Quoting Andrea Aime (2020-02-26 06:15:45) > > Could you please share the full stack trace of the error from the > GeoServer > > logs? > > Here's the full trace. I'm using the kartoza docker image, GeoServer > 2.16.1. > > I've found that (a) it affects at raster in a GeoTiff store, but not a > vector in a postgis store, and (b) a workaround is to specify a smaller > than default extent for the gridset (not the layers), e.g. > -14,479,413 2,536,215 -6,754,824 6,853,969 vs. the default > -20,037,508.34 -20,037,508.34 20,037,508.34 20,037,508.34. > > The trace below comes from trying to seed the default 900913 gridset > with a raster with extent > EPSG:900913: > -10828047.105450489,5378475.896535995,-9951640.485779572,6343710.361889524 > > Thanks, Terry > > 27 Feb 06:21:36 INFO [geoserver.wms] - > Request: getServiceInfo > 27 Feb 06:21:36 INFO [geoserver.flow] - Request [WMS 1.1.1 GetMap] > starting, processing through flow controllers > 27 Feb 06:21:36 INFO [geoserver.flow] - Request control-flow performed, > running requests: 1, blocked requests: 0 > 27 Feb 06:21:36 ERROR [geoserver.ows] - > org.geoserver.platform.ServiceException: Error rendering coverage on the > fast path > at > org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:362) > at > org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:276) > at > org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:133) > at org.geoserver.wms.GetMap.executeInternal(GetMap.java:707) > at org.geoserver.wms.GetMap.run(GetMap.java:287) > at org.geoserver.wms.GetMap.run(GetMap.java:110) > at > org.geoserver.wms.DefaultWebMapService.getMap(DefaultWebMapService.java:253) > at sun.reflect.GeneratedMethodAccessor339.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) > at > org.geoserver.kml.WebMapServiceKmlInterceptor.invoke(WebMapServiceKmlInterceptor.java:38) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) > at > org.geoserver.gwc.wms.CacheSeedingWebMapService.invoke(CacheSeedingWebMapService.java:55) > at > org.geoserver.gwc.wms.CacheSeedingWebMapService.invoke(CacheSeedingWebMapService.java:31) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) > at > org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:79) > at > org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:53) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) > at > org.geoserver.ows.util.RequestObjectLogger.invoke(RequestObjectLogger.java:50) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212) > at com.sun.proxy.$Proxy109.getMap(Unknown Source) > at sun.reflect.GeneratedMethodAccessor295.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.geoserver.ows.Dispatcher.execute(Dispatcher.java:879) > at > org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:265) > at > org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177) > at org.geoserver.gwc.GWC.dispatchOwsRequest(GWC.java:1376) > at >
Re: [Geoserver-users] GeoWebCache EPSG:3857 issues
Could you please share the full stack trace of the error from the GeoServer logs? Cheers Andrea On Mon, Feb 24, 2020 at 4:09 PM Terry N. Brown wrote: > [resend, I think list membership is email case sensitive] > > GeoServer Version > 2.16.1 > > Trying to see a EPSG:26915 Postgis raster layer in EPSG:3857. > > It fails because > > org.geoserver.platform.ServiceException: Error rendering coverage on the > fast path > > Caused by: org.geoserver.platform.ServiceException: > org.geotools.referencing.operation.projection.ProjectionException: > Latitude 229798992°09.8'S is too close to a pole. > > Obviously treating projected EPSG:3857 as lat/lon, but why? It does > this with the built in EPGS:900913 too. > > Everything else seems to work including caching of tiles generated by > user browsing. Alignment between layers suggests that all SRIDs are set > correctly and known by GeoServer. > > Seeding only seems to work for EPSG:4326. > > Many thanks for any pointers. > > Cheers -Terry > > > ___ > 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 > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.* ___ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] GeoWebCache EPSG:3857 issues
GeoServer Version 2.16.1 Trying to see a EPSG:26915 Postgis raster layer in EPSG:3857. It fails because org.geoserver.platform.ServiceException: Error rendering coverage on the fast path Caused by: org.geoserver.platform.ServiceException: org.geotools.referencing.operation.projection.ProjectionException: Latitude 229798992°09.8'S is too close to a pole. Obviously treating projected EPSG:3857 as lat/lon, but why? It does this with the built in EPGS:900913 too. Everything else seems to work including caching of tiles generated by user browsing. Alignment between layers suggests that all SRIDs are set correctly and known by GeoServer. Seeding only seems to work for EPSG:4326. Many thanks for any pointers. Cheers -Terry ___ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] GeoWebCache EPSG:3857 issues
[resend, I think list membership is email case sensitive] GeoServer Version 2.16.1 Trying to see a EPSG:26915 Postgis raster layer in EPSG:3857. It fails because org.geoserver.platform.ServiceException: Error rendering coverage on the fast path Caused by: org.geoserver.platform.ServiceException: org.geotools.referencing.operation.projection.ProjectionException: Latitude 229798992°09.8'S is too close to a pole. Obviously treating projected EPSG:3857 as lat/lon, but why? It does this with the built in EPGS:900913 too. Everything else seems to work including caching of tiles generated by user browsing. Alignment between layers suggests that all SRIDs are set correctly and known by GeoServer. Seeding only seems to work for EPSG:4326. Many thanks for any pointers. Cheers -Terry ___ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
