Changes between Version 16 and Version 17 of MapGuideRfc14

Timestamp:

02/02/07 13:02:52 (18 years ago)

Author:

robertbray

Comment:

--

MapGuideRfc14

@@ -234 +234 @@
 [[Image(ex4b.jpg)]]
 
+
 '''Example 5:'''  line style with a special cross-tick offset requirement
 
-
+[[Image(ex5.jpg)]]
+
+This line style is one that the current MapGuide stylization code can’t handle.  The problem is that the cross tick decoration needs to have a different start offset than the other decorations.  Our new stylization schema handles this easily though.  We have to create a compound symbol definition since we have two symbol components with different distributions.
+
+{{{
+<CompoundSymbolDefinition>
+  <Name>MTYP1500a</Name>
+  <Symbols>
+    <SimpleSymbolDefinition>
+      <Name>UpperLowerDashing</Name>
+      <Graphics>
+        <Path>
+          <Geometry>
+            M 0,-2.5 H 8 M 10,-2.5 H 8, M 20,-2.5 H 2
+            M 0, 2.5 H 8 M 10, 2.5 H 8, M 20, 2.5 H 2
+          </Geometry>
+        </Path>
+      </Graphics>
+      <LineUsage>
+        <VertexControl>OverlapWrap</VertexControl>
+        <Repeat>24</Repeat>
+      </LineUsage>
+    </SimpleSymbolDefinition>
+    <SimpleSymbolDefinition>
+      <Name>OffsetCrossTick</Name>
+      <Graphics>
+        <Path>
+          <Geometry>M 0.0,-2.5 V 5</Geometry>
+        </Path>
+      </Graphics>
+      <LineUsage>
+        <VertexControl>OverlapWrap</VertexControl>
+        <StartOffset>28</StartOffset>
+        <Repeat>24</Repeat>
+      </LineUsage>
+    </SimpleSymbolDefinition>
+  </Symbols>
+</CompoundSymbolDefinition>
+}}}
+
+The upper / lower dashing has zero start offset, whereas the cross tick has a 28 mm offset.  This horizontally positions the first cross tick at the center of the first long dash in the second cycle of upper / lower dashing.
 
 = Implications =
 
-This section allows discussion of the repercussions of the change, such as whether there will be any breakage in backwards compatibility, if documentation will need to be updated, etc.
+MapGuide will rock even more then it already does!!!
 
 = Test Plan =
 
-How the proposed change will be tested, if applicable.  New unit tests should be detailed here???
+Unit tests will be written to verify the new cartographic styling engine. In addition we will also create a sample symbol library to use for testing.
 
 = Funding/Resources =
 
-This section will confirm that the proposed feature has enough support to proceed.  This would typically mean that the entity making the changes would put forward the RFC, but a non-developer could act as an RFC author if they are sure they have the funding to cover the change.
+Autodesk (possibly with some resource contribution from DM Solutions) will provide resources to implement the core symbolization engine and detailed implementation for point symbols and label symbols.  If time allows we will also implement some portion of the line symbolization. In the future we plan to finish the symbolization engine to also include area symbolization.  Timing for this has yet to be determined.