Need help with WMS and Projections
ken at SANDNARROWS.COM
Thu Dec 2 19:59:04 EST 2004
Sorry, let me expand a bit on my setup.
I have mapserver setup and running on my server. Using chameleon I have
applications working, which is what I mean by 'client'. The
application includes my MAP file with some local layers (shp files), as
well it is using chameleon's WMS Browser to load in remote WMS layers on
the fly. So in the case of my client/application I am setting its
projections in the MAP file for that specific application.
So client, is my chameleon application thats running on my server, in
conjunction with mapserver.
Remote layer, would be any WMS served up on the internet that I can access.
Is that enough information?
Ed McNierney wrote:
> Ken -
> I'm having a hard time parsing your usage of "client", "my mapserver",
> and "remote". Could you explain the data flow a little more clearly?
> You say that your "client" requests a "remote" layer and asks for it in
> its desired projection, and if it can't get it, then "my mapserver"
> somehow appears to reproject it and save the day <g>. Where did your
> mapserver come from? Is it always there, acting as a WMS client to the
> "remote WMS layer"? What application is your "client"? Feel free to
> throw in a little ASCII art....
> - Ed
> Ed McNierney
> President and Chief Mapmaker
> TopoZone.com / Maps a la carte, Inc.
> 73 Princeton Street, Suite 305
> North Chelmsford, MA 01863
> Phone: +1 978 251-4242 Fax: +1 978 251-1396
> -----Original Message-----
> From: UMN MapServer Users List [mailto:MAPSERVER-USERS at LISTS.UMN.EDU] On
> Behalf Of Ken Sanderson
> Sent: Thursday, December 02, 2004 7:30 PM
> To: MAPSERVER-USERS at LISTS.UMN.EDU
> Subject: [UMN_MAPSERVER-USERS] Need help with WMS and Projections
> I am trying to get my head around how remote WMS layers work with
> projections and hoping that someone here can steer me in the right
> Here is how I have assumed it works. My client goes to a remote WMS
> layer and first asks for the layer in the projection of the client, if
> it doesnt support that it looks through the SRS tags of the WMS layer
> and finds the first one that it understands, by understands I mean thats
> included in my EPSG file, requests the image and my mapserver reprojects
> it to the projection my client is using.
> Thats what I thought, but using a WMS layer has drawn this into
> question, so is this true or not?
> Here is what has brought up the problem.
> I have two clients. One is in a projection of 4326 and another 42304
> (LCC Canada). When I load a specific WMS layer it works in 4326, but
> would not work in 42304. Here is the SRS info from the remote WMS layer:
> In my thinking since I have a number of these in my EPSG file,
> specifically 4326, than I should have no problem loaded the WMS layer
> into my client, regardless of what projection my client was using.
> In order to get this to work in both of my clients I had to add a new
> projection to my EPSG file. 102190 is BC Albers 42102 projection. As
> 102190 was the projection listed in the bounding box tag, I simply
> copied the 42102 and put a new one into my EPSG file with the number
> Works fine now. While this is working for me, I dont think its really a
> good solution as I cant be adding new entries to my EPSG file for every
> WMS layer my users may want to load.
> Sorry for this being long, but I really wanted to give all the details.
> How this has worked out has made me think my prior beliefs to how
> projections with remote WMS layers worked are wrong. So my question is,
> how do they work if they dont work the way I thought they did?
More information about the mapserver-users