Changes between Version 18 and Version 19 of MapGuideRfc16


Ignore:
Timestamp:
Mar 4, 2007, 3:51:25 PM (17 years ago)
Author:
chrisclaydon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc16

    v18 v19  
    3737=== Layer Definition Schema Modifications ===
    3838
    39 The layer definition schema contains numerous <!ExtendedData1> elements that allow the schema to be extended without breaking forward or backward compatibility. The changes proposed in this RFC would initially be added into one of these elements, and would eventually be moved to the main part of the schema whenever the next schema version update is carried out. See [wiki:MapGuideRfc10 MapGuide RFC 10] for more details.
    40 
    4139The affected section of the original schema looks like this:
    4240
    … …  
    6866        <xs:element name="PointTypeStyle" type="PointTypeStyleType">...
    6967      </xs:choice>
    70       <xs:element name="ExtendedData1" minOccurs="0" >
    71         <xs:complexType>
    72           <xs:sequence>
    73             <xs:element name="ElevationSettings" type="ElevationSettingsType" minOccurs="0" />
    74             <xs:element name="ExtendedData2" type="ExtendedDataType" minOccurs="0" />
    75           </xs:sequence>
    76         </xs:complexType>
    77       </xs:element>
     68      <xs:element name="ElevationSettings" type="ElevationSettingsType" minOccurs="0" />
     69      <xs:element name="ExtendedData1" type="ExtendedDataType" minOccurs="0" />
    7870    </xs:sequence>
    7971  </xs:complexType>
    … …  
    8375      <xs:element name="ZExtrusion" type="xs:string" minOccurs="0" />
    8476      <xs:element name="ZOffsetType" type="ElevationTypeType" minOccurs="0" />
     77      <xs:element name="Unit" type="LengthUnitType">
    8578      <xs:element name="ExtendedData1" type="ExtendedDataType" minOccurs="0" />
    8679    </xs:sequence>
    … …  
    9992Descriptions of the key parameters are given below:
    10093
    101 ||ZOffset||An expression that evaluates to the height of the base of the feature in meters||
    102 ||ZExtrusion||An expression that evaluates to the desired vertical extrusion (in meters) to be applied to the feature||
     94||ZOffset||An expression that evaluates to the height of the base of the feature in the units specified in the <Unit> element||
     95||ZExtrusion||An expression that evaluates to the desired vertical extrusion (in specified units) to be applied to the feature||
    10396||ZOffsetType||A string value, either "!RelativeToGround" or "Absolute", that indicates how to interpret the ZOffset value||
     97||Unit||A string value corresponding to one of the values in the existing LengthUnitType type||
    10498
    10599Additional !ExtendedData elements have been added to allow for future extensions to this part of the schema.
    … …  
    115109    ...
    116110    ...
    117     <ExtendedData1>
    118       <ElevationSettings>
     111    <ElevationSettings>
    119112        <ZOffset>0</ZOffset>
    120113        <ZExtrusion>HEIGHT_AGL</ZExtrusion>
    121114        <ZOffsetType>RelativeToGround</ZOffsetType>
    122       </ElevationSettings>
    123     </ExtendedData1> 
     115        <Unit>Meters</Unit>
     116    </ElevationSettings>
    124117  </VectorScaleRange>
    125118</VectorLayerDefinition>
    … …  
    129122=== MDF Model and Parser Modifications ===
    130123
    131 The MDF Model would require the addition of two new classes: '''!ElevationSettings''' and '''!VectorScaleRangeExtendedData1''', corresponding to the <!ElevationSettings> and custom <!ExtendedData1> elements respectively. Similarly, the MDF Parser would require two new classes: '''IOElevationSettings''' and '''IOVectorScaleRangeExtendedData1'''.
     124The MDF Model would require the addition of the new class: '''!ElevationSettings''', corresponding to the <!ElevationSettings> elements. Similarly, the MDF Parser would require the new class: '''IOElevationSettings'''.
    132125
    133 The parser classes would be responsible for reading and writing the elevation settings to and from XML. The model classes would be used to store and access those settings. The methods implemented by each class would be very simple get/set or read/write functions.
     126The parser class would be responsible for reading and writing the elevation settings to and from XML. The model class would be used to store and access those settings. The methods implemented by each class would be very simple get/set or read/write functions.
    134127
    135128=== Stylization Modifications ===