Ticket #8 (closed defect: worksforme)

Opened 11 months ago

Last modified 10 months ago

Strange effect when viewing EPSG:900913 WMS

Reported by: jbritton Owned by: arneke
Priority: major Milestone: 0.7.0
Component: core Version: 0.6
Keywords: Cc:

Description

When trying to cache tiles in Google projection from http://openaerialmap.org/wms/ I get a very strange problem. See attached image.

.properties file for this layer:

# Image formats, use
imagemimes=image/png,image/jpeg,image/gif

# WMS backend
wmsurl=http://openaerialmap.org/wms/
wmslayers=world
wmsstyles=

# Tile profile
srs=EPSG:900913
bbox=-20037508.34,-20037508.34,20037508.34,20037508.34
transparent=true
metatiling=3x3

# Cache backend
cachetype=org.geowebcache.cache.file.FileCache?
filecachepath=/tmp

And is added in OpenLayers? using:

var layer = new OpenLayers?.Layer.WMS( title,
"http://10.11.64.107:5050/geowebcache/wms",
{

layers: layerName,

srs: 'EPSG:900913',
format: 'image/png',
styles: ,
tiled: 'true'

},
{

'isBaseLayer': true

}
);

Attachments

geowebcacheproblem.JPG (224.2 kB) - added by jbritton 11 months ago.

Change History

Changed 11 months ago by jbritton

follow-up: ↓ 2   Changed 11 months ago by arneke

Hi,

could you post or attach the entire HTML for the client (zip it up)? (I'm primarily interested in the Map object definition, but it'd be great if I could have exactly the same that you're looking at).

Definetly a high priority, thanks for reporting.

in reply to: ↑ 1   Changed 11 months ago by jbritton

My code is all in different JavaScript? documents so it's a bit confusing sorry. Here is the code where I create the Map object though.

var options = {

projection: "EPSG:900913",
displayProjection: new OpenLayers?.Projection("EPSG:27700"),
units: "m",
maxResolution: 156543.0339,
maxExtent: new OpenLayers?.Bounds(-20037508, -20037508, 20037508, 20037508.34)

};
ChangesClient?.map = new OpenLayers?.Map(divName, options);

  Changed 10 months ago by arneke

  • status changed from new to closed
  • resolution set to worksforme
  • milestone changed from 0.8 to 0.7

I wasn't able to reproduce this exactly, especially the diagonal warping. But a lot of the internals for tiling have been replaced, so there's a good chance this bug is gone.

Sorry about the slow response, GeoServer releases came in between.

Note: See TracTickets for help on using tickets.