Changes between Version 3 and Version 4 of MapGuideRfc105


Ignore:
Timestamp:
Jul 20, 2010, 1:29:50 PM (14 years ago)
Author:
brucedechant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc105

    v3 v4  
    3030The 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.
    3131
     32Here is a subset of the WFS capabilities showing the differences.
     33
     34WFS provider returned capabilites (existing API):
     35{{{
     36<Filter>
     37  <SupportsGeodesicDistance>false</SupportsGeodesicDistance>
     38  <SupportsNonLiteralGeometricOperations>true</SupportsNonLiteralGeometricOperations>
     39</Filter>
     40}}}
     41
     42WFS provider returned capabilites (NEW API with server specified in connection string):
     43{{{
     44<Filter>
     45  <Condition>
     46    <Type>Comparison</Type>
     47    <Type>Like</Type>
     48    <Type>Spatial</Type>
     49  </Condition>
     50  <Spatial>
     51    <Operation>EnvelopeIntersects</Operation>
     52    <Operation>Intersects</Operation>
     53  </Spatial>
     54  <SupportsGeodesicDistance>false</SupportsGeodesicDistance>
     55  <SupportsNonLiteralGeometricOperations>true</SupportsNonLiteralGeometricOperations>
     56</Filter>
     57}}}
     58
    3259== Proposed Solution ==
    3360