Hi Rémy, thanks again for your support.
here some answers... Point 1: I make tests on MGOS on a remote server and on a local AIMS. On Qgis I use localhost for local AIMS (configured himsel as localhost) and I use IP for remote server (configured himself with his IP) Point 2: yes, I already know and I've already played with it with no success. I don't think the problem is here. Point 3: I can't clear EPSG:4326. If I do, then QGis give me an error on BBOX=0,0,0,0. This happens because without EPSG:4326 in row header, AIMS/MGOS returns capabilities without tag "EX_GeographicBoundingBox". I think that this is a very important xml tag for QGis, I will explain you later why. I discovered the following interesting thing by use of fiddler on QGis and on Map3D. Here capabilities for the layer: - <Layer> <Title>Infrastructure Map Server - Web Map Service</Title> <CRS>EPSG:4326</CRS> - - <Layer queryable="0" cascaded="0" noSubsets="0" opaque="0"> <Name>WMS-WFS/Common/Layers/LayerDefinitionSHPComuni</Name> <Title>LayerDefinitionSHPComuni</Title> <CRS>EPSG:4326</CRS> <CRS>EPSG:21781</CRS> + <EX_GeographicBoundingBox> <westBoundLongitude>8.371</westBoundLongitude> <eastBoundLongitude>9.174</eastBoundLongitude> <southBoundLatitude>45.825</southBoundLatitude> <northBoundLatitude>46.629</northBoundLatitude> </EX_GeographicBoundingBox> <BoundingBox CRS="EPSG:4326" minx="8.371" miny="45.825" maxx="9.174" maxy="46.629" /> <BoundingBox CRS="EPSG:21781" minx="672480" miny="75270" maxx="732911" maxy="165701" /> </Layer> </Layer> </Capability> Map3D build BBOX values getting them from BoundingBox CRS="EPSG:21781" and it works. QGis assign BBOX values with an extention a bit wider, getting values from EX_GeographicBoundingBox (from capabilities) and transforming in something very closed to this but a bit wider, only a bit: in that case AIMS/MGOS returns an error without message. If I get QGis request (got from fiddler) and replace BBOX with values from BoundingBox CRS="EPSG:21781" (from capabilities), then it works fine. Conclusion: AIMS/MGOS works with BBOX equal or shorter than what expressed in GetCapabilities values. BBOX with values outside generate an error. I think that this is a bug. With this limitation a wide range of WMS client will not work. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/WMS-from-MGOS-can-t-be-read-by-QGIS-tp5029828p5029966.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users