Changes between Version 2 and Version 3 of MapGuideRfc16

Timestamp:

Feb 22, 2007, 8:45:06 AM (17 years ago)

Author:

chrisclaydon

Comment:

--

MapGuideRfc16

@@ -9 +9 @@
 ||RFC Template Version||(1.0)|| 
 ||Submission Date||(Date/Time submitted)||
-||Last Modified||chrisclaydon [[Timestamp]]||
+||Last Modified||Chris Claydon[[Timestamp]]||
 ||Author||Chris Claydon||
 ||RFC Status||draft||
@@ -23 +23 @@
 == Overview ==
 
-This section brefly describes the problem set, and the proposed solution in general terms.  It should be deliberately short, a couple of sentences or so.
+The purpose of this RFC is to allow MapGuide users to configure elevation and extrusion parameters in a layer definition, and to use those settings to extrude features vertically in the KML generated for consumption by Google Earth. This provides a highly compelling way to visualize spatial data that contains a vertical component.
 
 == Motivation ==
 
-This is the most important part of the RFC.  It describes the problem domain in detail.  Focusing on this will allow reviewers to fully understand why the proposed change is being made, and potentially suggest different/better ways of accomplishing the desired results.  The more time we spend on understanding the problem, the better our solution will be.
+MapGuide currently supports 2D representation of spatial data. However, many spatial data sets contain height information for the features they contain, giving the potential for 2.5D representation. This RFC describes how the MapGuide Layer Definition schema can be extended to specify expressions to be used to calculate a base elevation and extrusion size. Support for 2.5D would initially be implemented by the KML service, allowing visualization of solid objects in Google Earth. An example of the potential output is shown below:
+
+
 
 == Proposed Solution ==