MapGuide RFC 105 - Enhance feature service GetCapabilities API

This page contains a change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.


RFC Template Version(1.0)
Submission DateJuly 20, 2010
Last ModifiedBruce Dechant July 27, 2010
AuthorBruce Dechant
RFC Statusadopted
Implementation Statusimplemented
Proposed Milestone2.3
Assigned PSC guide(s)Bruce Dechant
Voting History
+1Bob, Bruce, Haris, Jackie, Jason, Paul, Tom, Trevor, Zac


This RFC proposes to add a NEW GetCapabilites() API to the feature service which contains an additional connection string parameter. This new method should only be used to get connection-based capabilities on WFS and WMS providers until FDO specifies how connection-based connections should behave; use on any other providers may cause compatibility problems in the future.


The existing Feature service GetCapabilties() API works correctly for most providers, but fails to return the true capabilities of the server connected to by a WFS/WMS provider because there is no way to specify the connection string containing the server.

Here is a subset of the WFS capabilities showing the differences.

WFS provider returned capabilites (existing API):


WFS provider returned capabilites (NEW API with server specified in connection string):


Proposed Solution

Create a NEW GetCapabilities() API that takes an additional connection string parameter.

Existing API: (This will not change)

    MgByteReader* GetCapabilities(CREFSTRING providerName);

Proposed NEW API:

    MgByteReader* GetCapabilities(CREFSTRING providerName, CREFSTRING connectionString);

Note: This NEW API will behave exactly the same as the old API if it is given an empty string as the connection string parameter.


This change will NOT break existing API compatibility.

Test Plan

Build/Run on Windows/Linux.


Supplied by Autodesk.

Last modified 12 years ago Last modified on Aug 5, 2010, 10:33:37 AM
Note: See TracWiki for help on using the wiki.