Changes between Version 9 and Version 10 of MapGuideRfc26


Ignore:
Timestamp:
Aug 6, 2007, 12:25:31 AM (17 years ago)
Author:
yangm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc26

    v9 v10  
    2222== Overview ==
    2323
    24 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.
     24The purpose of this RFC is to allow !MapGuide to stylize the elevation data, which configured surface style in its layer definition.
    2525
    2626== Motivation ==
    2727
    28 For elevation data, such as DEM file, which would not be displayed in !MapGuide as it does in Map 3D, because the !MapGuide do not have the stylization mechanism for grid surface data as Map does. So, in this release, we will make !MapGuide has the ability to stylize the elevation layer.
    29 If publish a elevation layer from Map 3D to !MapGuide, the user would see Figure 1 in MapGuide Studio in the future, not the Figure 2, which is the current status for elevation data in MapGuide.
     28Map 3D can publish stylized elevation layer, such as DEM and GeoTIFF file to !MapGuide. The layer definition for an elevation data in Map 3D would like below, with surface style:
     29{{{
     30<LayerDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:noNamespaceSchemaLocation="LayerDefinition-1.0.0.xsd" version="1.0.0">
     31<GridLayerDefinition>
     32  <ResourceId>Library://Publish/Data/Raster_1.FeatureSource</ResourceId>
     33  <FeatureName>rasters:davenport</FeatureName>
     34  <Geometry>Image</Geometry>
     35  <GridScaleRange>
     36    <SurfaceStyle>
     37      <Band>1</Band>
     38      <DefaultColor>0000FF00</DefaultColor>
     39    </SurfaceStyle>
     40    <ColorStyle>
     41      <HillShade>
     42        <Band>1</Band>
     43        <Azimuth>45</Azimuth>
     44        <Altitude>45</Altitude>
     45      </HillShade>
     46      <ColorRule>
     47        <LegendLabel>-1.79e+308 to 1.79e+308</LegendLabel>
     48        <Filter>(Height(1) > -1.7976931348623158e+308) AND (Height(1) < 1.7976931348623158e+308)</Filter>
     49        <Color>
     50          <ExplicitColor>FF00FF00</ExplicitColor>
     51        </Color>
     52      </ColorRule>
     53      <ColorRule>
     54        <LegendLabel>{DEFAULT}</LegendLabel>
     55        <Color>
     56          <ExplicitColor>FF006423</ExplicitColor>
     57          </Color>
     58      </ColorRule>
     59    </ColorStyle>
     60    <RebuildFactor>1</RebuildFactor>
     61  </GridScaleRange>
     62</GridLayerDefinition>
     63}}}
     64
     65While, !MapGuide cannot display this elevation data published from Map 3D with surface style, because the !MapGuide do not have the stylization mechanism for grid surface data.
     66So, in this release, we will make !MapGuide has the ability to stylize the elevation layer. If publish a stylized elevation layer from Map 3D to !MapGuide, the user would see Figure 1 in !MapGuide Studio in the future, not the Figure 2, which is the current status for elevation data in !MapGuide.
    3067
    3168||[[Image(After.JPG, align=center)]]|| instead of ||[[Image(Before.JPG, align=center)]]||
     
    3471== Proposed Solution ==
    3572
    36 This is a more detailed description of the actual changes desired.  The contents of this section will vary based on the target of the RFC, be it a technical change, website change, or process change.  For example, for a technical change, items such as files, XML schema changes, and API chances would be identified.  For a process change, the new process would be laid out in detail.  For a website change, the files affected would be listed.
     73The proposed solution contains modifications to: Platformbase and Stylization projects.
     74
    3775
    3876== Implications ==
    3977
    40 This RFC does not describe any GUI modifications. The layer definition xml document was published from Map 3D.
    41 There are no changes to the existing public API.
     78This RFC does not describe any GUI modifications and does not affect the existed published API.
    4279
    4380== Test Plan ==
    4481
    45 Publish a Grid Surface data from Map 3D to !MapGuide server, at the end the surface image should display as it was shown in Map 3D.
     82After publishing a elevation data from Map 3D to !MapGuide server, the elevation image should display as it was shown in Map 3D.
    4683
    4784== Funding/Resources ==