WMS - coordinate system overriding fails

[gBecker]

In MGOS 2.0.1 coordinate system overriding for WMS fails. No WMS layers showing up anymore. With version 1.2 there was no problem. I've tested it with Windows Vista and Windows Server 2003.

I recognized some logging entries in Error.log. It says the coordinate system of the layer is not the same as the one for the map. It seems that MapGuide doesn't look up the SpatialContext-Node of my Config.xml. Maybe doesn't look up the configuration file at all.

By the way, the same configuration in MapGuide Enterprise 2009 works fine.

Gunter

[gBecker]

Coordinate System Overriding

[gBecker]

Sample Package

[tomfukushima]

The map and the feature source/layer are in different coordinate systems. The problem is exactly what the server is saying. There is a web page on the wiki that describes how to configure a WMS feature source so that it uses the correct coordinate system (for your case DHDN.Gauss3d-3 (DHDN.Gauss3d-3)). When you find that link, please add it to this ticket so that others can find it. Closing this ticket.

[gBecker]

Sorry for reopening this ticket but I think it is really a bug. As I mentioned i've got it working with MGOS 1.2 and MGE 2009.

I know the document you pointed me to. The configuration described there is exactly what I've done before I opened this ticket. You can see it in the attached package and the Config.xml file. The coordinate system I use in my MapDefinition is DHDN.Gauss3d-3 and its pendant in Config.xml is EPSG:31467.

Some more information:

When preview the LayerDefinition in MapGuide Studio 2009 our server logs requests with the correct CS (EPSG:31467) but with BoundingBox in lat/lon-coordinates:

wrong: ... &SRS=EPSG:31467&BBOX=8.050927,48.543305,8.309285,48.673315 ... (correct: ... &SRS=EPSG:31467&BBOX=3498000,5283000,3510000,5300000 ...)

When preview the map I got the message I've described in my first post. The log says that the layer CS is EPSG:4326. I've never used this CS. But it is the first CS in the GetCapabilites document from the WMS server (which I thought I have overridden in the configuration document). MapGuide seems to ignore my CS settings and always passes the coordinates in the format of the first CS from WMS server.

Another point is that when I'm dragging the LayerDefinition from Site-Explorer in MG Studio to the MapDefinition the coordinate system that shows up in the CS textbox is LL84 (WGS 84). I tried this also with WMS servers that have other CS at the first position and it always takes the first one in the list (EPSG:31467 results in DHDN.Gauss3d-3). At this point I've also tried to override the coordinate system setting of my FeatureSource (<SupplementalSpatialContextInfo>) with no success.

I hope this will clarify my situation!

[tomfukushima]

Oh, sorry, I missed the config.xml file last time, I use lower case config.xml instead of Config.xml and that is why I couldn't find it. I can reproduce that this works in AMGE 2009 but does not work with MGOS 2.0.1. I would think that this is a problem with Proj.4, but I'm just guessing.

[loudent]

Patch that addresses the missing spatial context association for wms layers

[brucedechant]

Fixed in sandbox/adsk/2.1 r4273

[brucedechant]

Some of the changes required for this fix were addressed with the fix for ticket 1091.

Fixed in trunk r4404