GeoWebCache does not return the correct tiles for an extent when using a
gridset created for EPSG:3031
------------------------------------------------------------------------------------------------------
Key: GEOS-4886
URL: https://jira.codehaus.org/browse/GEOS-4886
Project: GeoServer
Issue Type: Bug
Components: GWC
Affects Versions: 2.1.2
Environment: Running GeoWebCache as part of GeoServer.
Reporter: Brendan Barrett
Assignee: Andrea Aime
Priority: Critical
Attachments: GeoWebCacheBug_Files.zip
I created a WMS server to host LIMA data (Landsat Imagery Mosaic of
Antarctica). You can find the original imagery as a GeoTiff here:
http://lima.usgs.gov/tiff_90pct.zip.
I set up the Layer (specifying EPSG:3031), and when I preview using Layer
Preview it displays exactly as expected, and I can overlay KML data over it in
OpenLayers. This means that the coordinates are correct.
I then need to set up a gridset to be able to use this layer with GeoWebCache
so that it knows what bounds to create the tiles between. I attached the
geowebcache.xml file in the zip file attached to this bug report.
When I view the map again, using geowebcache, I get strange results. Each layer
that I zoom into starts with a rendering of the first tile of the layer, and
then each tile after that looks exactly the same. See the two attached screen
grabs in the zip file to see what I am talking about.
The tiles are stored exactly like this in the cache folder too.
If I change the values for extents, or specify resolutions in the gridset, I
get the same result.
My conclusion is that geowebcache cannot handle EPSG:3031.
I have marked the issue as critical... as it is for those of us that need to
view data in EPSG:3031, which is basically anyone looking at Antarctic data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
