[mapguide-users] Having trouble figuring out the path for wms

[Thomas M. Tuerke]

Ivan, Joanne,

Shared sympathies on that 559 response.  It's a catch-all response, theoretically "of last resort."

Joanne: in regards to WMS, let me rephrase Ivan's response a bit: "Welcome to the joys of interoperability."  When you're doing WMS, you're at the mercy of several implementations (plus conditions on the network, etc.) ;-)

Strictly speaking, a proper WMS request is:

http://someurl?request=GetCapabilities&service=WMS
               ^^^^^^^^^^^^^^^^^^^^^^^

in order to learn the capabilities of the server (where, as you might expect "someurl" is to be replaced by the URL of the server in question.)  The next step is typically

http://someurl?request=GetMap&a-bunch-of-specific-parameters
               ^^^^^^^^^^^^^^

where the parameters are determined by what you learned from GetCapabilities.

Depending on the client, you might get away with just providing the http://someurl part; the client's UI will then guide you through the selection of layers, styles, and all that.

Other -- lower-level -- clients require you to literally type out the entire http://someurl?request=GetMap&etc request.  This has the unfortunate effect of placing an (undue?) burden of WMS sophistication on the user.

To that end, I've attached a little HTML web page that helps somewhat... in that you can play with the various parameters on the web page.  When you have something you want, you can copy the URL into the client's edit control.  It's not the most sophisticated thing out there, but for 3K of text, it does a workable job.

- Thomas

-----Original Message-----
From: Ivan Milicevic [mailto:ivan at ineo.hr] 
Sent: Wednesday, July 05, 2006 7:29 AM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] Having trouble figuring out the path for wms

Wellcome to the hell of "error: (559) MgFdoException" :-)

-----Original Message-----
From: joanne cook [mailto:j.cook at oxfordarch.co.uk] 
Sent: 5. srpanj 2006 16:26
To: users at mapguide.osgeo.org
Subject: [mapguide-users] Having trouble figuring out the path for wms

Hi All,
 
I am trying to use Autodesk MapGuide Studio to connect to a wms server,
powered by MapServer, using the latest wms/wfs connectors, but I can't seem
to figure out the path and can't find any documentation on this. The
MapServer documentation suggests a path something like
 
http://yourhost/cgi-bin/mapserv.exe?map=path/to/your/map&
 
With a whole bunch of extra parameters after it, whereas a MapGuide Studio
connection to (say) geoserver seems only to require
 
http://yourhost/geoserver/wms <http://yourhost/geoserver/wms> 
 
The first option gives me an error that states 
System.Net.WebException: The remote server returned an error: (559)
MgFdoException.
   at
Autodesk.MapGuide.Studio.Site.Comm.RequestManager.ExecutePendingGetRequestTo
String(Operation operation)
   at
Autodesk.MapGuide.Studio.Site.Comm.RequestManager.TestConnection(String
resourceId, String provider, String connectionString)
   at Autodesk.MapGuide.Studio.Site.FeatureSourceInfo.TestConnection()
 
Which is fair enough since I didn't think it was correct, but has anyone
managed to make a connection from Studio to a MapServer map, and what path
did they use?
 
Many thanks
 
Jo
-------------------------------------------
Joanne Cook BSc MLitt AIFA
Information Systems Coordinator
Oxford Archaeology North
-------------------------------------------


This message has been scanned for viruses by BlackSpider MailControl -
www.blackspider.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
For additional commands, e-mail: users-help at mapguide.osgeo.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
For additional commands, e-mail: users-help at mapguide.osgeo.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20060705/20a1b050/wmsclient.html