Changes between Initial Version and Version 1 of MapGuideRfc6


Ignore:
Timestamp:
Feb 5, 2007, 5:30:44 PM (17 years ago)
Author:
tonyfang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc6

    v1 v1  
     1= !MapGuide RFC 6 - Overriding Coordinate Systems in Feature Sources =
     2
     3This page contains a change request (RFC) for the !MapGuide Open Source project. 
     4More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
     5
     6
     7== Status ==
     8 
     9||RFC Template Version||(1.0)||
     10||Submission Date||February 5, 2007||
     11||Last Modified||Tony Fang [[Timestamp]]||
     12||Author||Tony Fang||
     13||RFC Status||draft||
     14||Implementation Status||pending||
     15||Proposed Milestone||1.2||
     16||Assigned PSC guide(s)||(when determined)||
     17||'''Voting History'''||(vote date)||
     18||+1|| ||
     19||+0|| ||
     20||-0|| ||
     21||-1|| ||
     22 
     23== Overview ==
     24
     25The coordinate systems of the data can be overridden by specifying an entry in the SupplementalSpatialContextInfo of the feature source.
     26
     27== Motivation ==
     28
     29In the feature source, there is an optional tag called SupplementalSpatialContextInfo. This can contain a SpatialContextType defining a coordinate system override. If an entry exists for a given Spatial Context, then the specified coordinate system override will be used. The coordinate system override will be given preference over the coordinate system defined in the data.
     30
     31Previously, the SupplementalSpatialContextInfo was intended for data which contained an undefined coordinate system. The SupplementalSpatialContextInfo would allow the user to specify a coordinate system for the data. The SupplementalSpatialContextInfo can now be used for all feature sources.
     32
     33== Proposed Solution ==
     34
     35The schema FeatureSource-1.0.0.xsd does not change. SupplementalSpatialContextInfo already exists in the schema. The schema documentation will be updated to reflect the new behaviour in the server.
     36
     37{{{
     38  <xs:element name="SupplementalSpatialContextInfo" type="SpatialContextType" minOccurs="0" maxOccurs="unbounded">
     39    <xs:annotation>
     40      <xs:documentation>Additional information for a spatial context when the coordinate system is overridden.
     41      </xs:documentation>
     42    </xs:annotation>
     43  </xs:element>
     44}}}
     45
     46When the server returns the data for a given feature source. it will check for entries in the SupplementalSpatialContextInfo. If there is a spatial context containing a coordinate system override, then that is the coordinate system used for the data.
     47
     48== Implications ==
     49
     50SupplementalSpatialContextInfo is an optional field. If the feature source does not contain an override, then the server will use the coordinate system contained in the data.
     51
     52For previous versions of the server, the SupplementalSpatialContextInfo field is not used. It will use the coordinate system defined by the data.
     53
     54== Test Plan ==
     55
     56Add unit tests to test coordinate system overrides.
     57
     58== Funding/Resources ==
     59
     60Autodesk to supply