Ah, thank you. A comment about this in the documentation would have been useful.
Whast about WebGL, couldn't that solve this? Just a thought... The data I'm working with is photographic (aerial photography), so I'll have to do server side reprojection... I assume the same issue is present if you try to add multiple tile based layers (e.g. OSM and WMS) with allOverlays = true, that is, they all have to be in the same projection? Best regards, Egil On 08/21/2013 12:05 AM, Phil Scadden wrote: > you are correct - if you are going to overlay images, then they must > be on the same projection. Re-projecting an image on the fly is costly > (and degrades the image quality), and beyond what a browser running JS > can do in reasonable time. Geoserver can do on-the-fly reprojection of > image sources but that doesnt solve image quality issues (and is > expensive on server cpu resources). You want to look hard at how the > image was created in the first place. If it is photographic or > similar, then offline reprojection to 900913 using high-quality > (cpu-intensive) options is best path. If it originated from vector > data, then go back to the original vector data and use a WMS server to > deliver it in the desired projection on the fly. > > Notice: This email and any attachments are confidential. > If received in error please destroy and immediately notify us. > Do not copy or disclose the contents. > > _______________________________________________ > Users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/openlayers-users
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
