[mapguide-users] RE: checking wms connections

spaceoddity rpowers at neomatix.ca
Thu Mar 29 10:24:19 EDT 2007


I'm trying to view my MGOS WMS service in ArcMap9.2 or uDig 1.18.  Both
receive and process the capabilities info but neither draw the layer.  I'm
able to manually request a map based on your helpful test tool which
generates

http://neomatix.linksysnet.com:8008/mapguide/mapagent/mapagent.fcgi?request=GetMap&service=WMS&layers=Tiger/Layers/places2&srs=EPSG:4326&bbox=-87.74,43.68,-87.69,43.815&width=500&height=500&format=image/png

but ArcMap just draws a blank and uDIG says RenderingConnection refused:
connect
Any hints on what else to look for?



Andy Morsell wrote:
> 
> What do you get from this?
> 
> http://localhost:8008/mapguide/mapagent/mapagent.fcgi?REQUEST=GetCapabilitie
> s&SERVICE=WMS&FORMAT=text/xml 
> 
> Also attached is an email from Thomas Tuerke from July that has handy
> little
> wms client test page in it.  I hope it comes through on the email list.
> 
> Andy 
> 
> -----Original Message-----
> From: joanne cook [mailto:j.cook at oxfordarch.co.uk] 
> Sent: Monday, November 13, 2006 7:40 AM
> To: users at mapguide.osgeo.org
> Subject: [mapguide-users] checking wms connections
> 
> Hi All,
> 
> I am trying to make a wms connection to some layers in my MapGuide
> OpenSource 1.0.2 map. I can't connect to my own, and assume there's some
> kind of problem with the conversion from a different coordinate system, as
> seems to have been discussed at length on this list, so I thought I'd
> better
> try the Sheboygan data first. All I am trying to do is connect to the data
> in Firefox 2, using the following URL:
> 
> http://localhost:8008/mapguide/mapagent/mapagent.fcgi?SERVICE=WMS&VERSION=1.
> 1.1&REQUEST=GetMap&LAYERS=Samples/Sheboygan/Layers/Buildings&FORMAT=image/pn
> g
> 
> This gives me the following message:
> 
> 
> An unclassified exception occurred.
> 
> An unclassified exception occurred. Exception occurred in method
> MgHttpWmsGetMap.Execute at line 204 in file
> c:\build_tux_area\mgdev_opensource\web\src\httphandler\HttpWmsGetMap.cpp
>  
> If I remove any of the parameters I get an xml document back that tells me
> I
> don't have all the parameters I need. A GetCapabilities request seems to
> validate as far as I can tell...
> The end result of all of this is that I want to be able to use my MapGuide
> Open Source data in OpenLayers, but needless to say that doesn't work at
> all
> at the moment either!
>  
> Many thanks
>  
> Jo
>  
> -------------------------------------------
> Joanne Cook BSc MLitt AIFA MBCS
> 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
> 
> 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
> 
> 
> 
> 
> Simple WMS Client
> 
> body {
>   background-color: #eee;
> }
> .frame {
>   border: 1px solid red;
> }
> 
> 
> 
> 
>           
>           
>  
>   
>    Simple WMS Client
>    
>     
>     Provide the desired values at left, then click the Update button to
> see the image here. 
>    
>   
>   
>    Site
>    
>   
>   
>    Layers
>    
>   
>   
>    SRS
>    
>   
>   
>    BBOX
>    
>   
>   
>    WIDTH
>    
>   
>   
>    HEIGHT
>    
>   
>   
>    FORMAT
>    
>   
>   
>    use Service=WMS
>    
>   
>   
>    
>    
>      
>      
>    
>   
>  
> 
> 
> 
>  
> 
> 
> ---------------------------------------------------------------------
> 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
> 

-- 
View this message in context: http://www.nabble.com/checking-wms-connections-tf2623055s16610.html#a9734357
Sent from the MapGuide Users mailing list archive at Nabble.com.



More information about the mapguide-users mailing list