Re: [Geoserver-users] Layer Groups -- GWC Capabilities
I didn't have the cache layers set. That has been fixed but for some reason the capabilities doesn't have the time dimensions listed anymore. I used to have them because my leaflet app would read it from there and let me do looping. Any ideas on that? Bryan -- CONFIDENTIALITY. This electronic mail and any files transmitted with it may contain information proprietary to BAM WX LLC, or one of its subsidiaries or affiliates, and is intended solely for the use of the individual to whom or entity to which this message is addressed and must be maintained in confidence and may not be disclosed to third parties without the written consent of the sender. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return 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
[Geoserver-users] Final releases of GeoTools 21.5, GeoWebCache 1.15.5 & GeoServer 2.15.5
The final planned releases of GeoTools 21.5, GeoWebCache 1.15.5 & GeoServer 2.15.5 have been made. If you or your organisation is still using any of these versions you need to seriously consider upgrading to a later version now. Blog posts describing the changes are at https://geotoolsnews.blogspot.com/2020/02/geotools-215-released.html & http://blog.geoserver.org/2020/02/24/geoserver-2-15-5-released/ The PMC are grateful to Astun Technology and GeoSolutions IT for Ian Turton & Andrea Aime's time respectively to make this release. -- Ian Turton ___ 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
