Changes between Version 2 and Version 3 of MapGuideRfc95


Ignore:
Timestamp:
Jun 11, 2010, 11:08:44 PM (14 years ago)
Author:
liuar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc95

    v2 v3  
    2020== Overview ==
    2121
    22 Enhance the WMS 1.3.0 implmentation of MapGuide according to OGC WMS 1.3.0 specification. The goal is to make sure MapGuide could pass the OGC certification for WMS 1.3.0 and 1.1.1 (http://cite.opengeospatial.org)
     22Enhance the WMS 1.3.0 implmentation of MapGuide according to OGC WMS 1.3.0 specification. The goal is to make sure MapGuide could pass the OGC certification for WMS 1.3.0 and 1.1.1 (http://cite.opengeospatial.org).
    2323
    2424== Motivation ==
    … …  
    2727
    2828== Proposed Solution ==
    29 Here are some proposed solution for two main changes in WMS 1.3.0
     29Here are some proposed solution for two main changes in WMS 1.3.0.
    3030
    3131One significant change in WMS 1.3.0 is the axis orientation. In order to align with the definitions from the EPSG database, OGC WMS 1.3.0 specification reversed the axis sequence for some EPSG code include EPSG:4326. Which means for some EPSG CRS, the meaning of (x,y) is changed from (lon,lat) to (lat,lon) or even other orientations.
    3232
    33 Some new API added in order to adapt the axis orientation issue in WMS 1.3.0
     33Some new API added in order to adapt the axis orientation issue in WMS 1.3.0.
    3434
    35 CS_MAP will provide an API to obtain the axis orientation for one particular ESPG CRS
     35CS_MAP will provide an API to obtain the axis orientation for one particular ESPG CRS.
    3636{{{
    3737// Parameter   nVendor=MgCoordinateSystemCodeFormat::Epsg
    … …  
    5050}}}
    5151
    52 It is necessary for MapGuide implement an API ProcessBoundingBoxAxes to handle different axis orientation for the bounding box parameter in GetMap and GetFeatureInfo operation. For example: change (lat,lon) back to (lon,lat)
     52It is necessary for MapGuide implement an API ProcessBoundingBoxAxes to handle different axis orientation for the bounding box parameter in GetMap and GetFeatureInfo operation. For example: change (lat,lon) back to (lon,lat).
    5353
    5454{{{
    … …  
    6767The other important change in WMS 1.3.0 specification is the CRS namespace. WMS 1.3.0 specification introduced two more CRS namespaces besides EPSG, they are CRS namespace which in the form specified by ISO 19111 and  AUTO2 namespace is used for "automatic" coordinate reference systems.
    6868
    69 In order to pass the OGC certification, the CRS CRS:84 must be supported. There's a workaround that it could be predefined in OgcWmsService.config
     69In order to pass the OGC certification, the CRS CRS:84 must be supported. There's a workaround that it could be predefined in OgcWmsService.config.
    7070
    7171{{{