georeference.org
Subscribe to this thread
Home - Scripting / All posts - WMS layers with commercial basemaps in openlayers
jluchette

151 post(s)
#26-Mar-08 05:09

Manifold WMS/WFS overlays nicely on the openlayers default basemap, but when the basemap is changed to VE, Yahoo, Google or Multimap, the WMS is askew, strangely, the closer one zooms in, the WMS begins to overlay correctly.

Any ideas? Perhaps someone has had the chance to play around with openlayers a bit more than myself and has an idea or solution to this already... I've only begun to look into it...

kgj28 post(s)
#26-Mar-08 06:08

This is probably because the projections used by the VE/Yahoo/Google layers are not quite the same as what you are generating from Manifold, so you'll need to configure OpenLayers accordingly. (The difference is greatest when zoomed out, but once you zoom in to a small area, the difference diminishes, as you describe.)

See these notes on the current recommended way of handling this: http://trac.openlayers.org/wiki/SphericalMercator

You might also want to search for more in the OpenLayers list archives: http://openlayers.org/mailman/listinfo/users

Cheers,

Keith

tib0r13 post(s)
#12-Jun-08 07:23

What is the Manifold WMS/WFS projection that can be used for this? (Even though it would be off at distant zoom levels) When I setup Standard/Cylindrical/Mercator it's reprojected to EPSG:4326 in the Manifold WMS service.

Anybody else struggling with the Manifold restriction to publish only WMS services with defined EPSG? None of the projections we happen to use is standardized with a EPSG code. So we cannot publish them as WMS (without reprojection). Interoperability is not an issue for us becuase we only need the WMS service to get tiles for OpenLayers and Tilecache.

Tibor

adamhill1 post(s)
#13-Jun-08 10:15

Tibor,

This might make your life easier - http://www.iter.dk/post/2008/05/SphericalWeb-Mercator-EPSG-code-3785.aspx

All I can say is it is about fracking time!

chrismarx

815 post(s)
#11-Nov-08 11:00

Hi, just found this post, and wondering if you every had any success with this. it's in reference to this post

http://forum.manifold.net/forum/t73819.7

jluchette

151 post(s)
#11-Nov-08 12:06

for the openlayers basemap it was working well. but for google and other commercial basemaps, i was getting very similar results, with the offsets. i have nothing available to show right now unfortunately. i'll try to recreate and get soemthing up to show...

chrismarx

815 post(s)
#11-Nov-08 12:30

yeah, i had the same experience, openlayers worked fine for me too-

i put up a sample if you want to play with that, so we can replicate the same problems. feel free to grab the code from the site as well, nothing is obfuscated, although if it's my code thats to blame, perhaps it would be good to see other examples-

jluchette

151 post(s)
#11-Nov-08 13:45

just to clarify. i was doing all my testing within the openlayers api, and when i added google or yahoo or VE basemap to it, there were issues. hopefully i get a chance to snag your code and poke around with this a bit.

chrismarx

815 post(s)
#11-Nov-08 14:04

ah, well i did try the openlayers api, but then i just went straight to my posted project, where im overlaying the tiles right on top of the google maps-

chrismarx

815 post(s)
#13-Nov-08 17:05

so are we saying then, that manifold needs to add this coordinate system?

http://www.iter.dk/post/2008/05/SphericalWeb-Mercator-EPSG-code-3785.aspx

jluchette

151 post(s)
#14-Nov-08 06:44

maybe that is all it boils down too. my experimentation kind of stopped abruptly so i never pursued this. if that is what we are saying, lets let them know...

0 msec Copyright (C) 2007-2008 Manifold.net. All rights reserved.