Problem with WMS Connection

[Dennis Megarry]

Ahh.. yup.. that was it!  Stupid me.. I fought with this for 5 days now..  lol  Thanks!
 
So..  I take it if you have data with different projections you need to set this at the layer level?  I had setup the main projection which all my data is in and thought by setting the layer projection for the WMS server is would work, but it certainly did not...  I removed the Projection all together and things started to display.
 
Dennis

________________________________

From: UMN MapServer Users List on behalf of Ed McNierney
Sent: Fri 2/24/2006 11:37 AM
To: MAPSERVER-USERS at LISTS.UMN.EDU
Subject: Re: [UMN_MAPSERVER-USERS] Problem with WMS Connection


Dennis -
 
Thanks - the server seems fine.  But you're not defining a PROJECTION block for the WMS layer - you need to tell MapServer that the input image is in EPSG:4269 projection rather than in the default LCC projection of your output image.  Without that, MapServer will treat it as LCC input coordinates, and the resulting image will be way off-screen somewhere.
 
I might be wrong on that - I got in the habit of specifying PROJECTION blocks for WMS layers a long time ago, when they were required.  That might have changed, but it's worth a try.
 
    - Ed
 
P.S.
Ed McNierney
President and Chief Mapmaker
TopoZone.com / Maps a la carte, Inc.
73 Princeton Street, Suite 305
North Chelmsford, MA  01863
ed at topozone.com
(978) 251-4242 


________________________________

From: Dennis Megarry [mailto:dennis at megarry.com] 
Sent: Friday, February 24, 2006 11:01 AM
To: Ed McNierney
Subject: RE: [UMN_MAPSERVER-USERS] Problem with WMS Connection


I do get a response from it...  The actual MAP file is below (since this is sent off-list).  I tried your suggestion and put "&" on the end (see below) and still nothing..  ARGH! 
 
 [MAP file contents removed by Ed before replying on-list]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20060224/75f82fe5/attachment.htm>