Changes between Initial Version and Version 1 of MapGuideRfc146


Ignore:
Timestamp:
Sep 5, 2014, 6:37:32 AM (10 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc146

    v1 v1  
     1
     2= !MapGuide RFC 146 - Stamen tile layer support for Fusion =
     3
     4This page contains a change request (RFC) for the !MapGuide Open Source project.
     5More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
     6
     7
     8== Status ==
     9
     10||RFC Template Version||(1.0)||
     11||Submission Date||5 Sep 2014||
     12||Last Modified||||
     13||Author||Jackie Ng||
     14||RFC Status||draft||
     15||Implementation Status||pending||
     16||Proposed Milestone||3.0||
     17||Assigned PSC guide(s)||(when determined)||
     18||'''Voting History'''||(vote date)||
     19||+1||||
     20||+0||||
     21||-0||||
     22||-1||||
     23||no vote||||
     24
     25== Overview ==
     26
     27This RFC proposes to add support for stamen tiles in Fusion
     28
     29== Motivation ==
     30
     31[http://maps.stamen.com/ Stamen maps] provides stylish cartographic renderings of OpenStreetMap data.
     32
     33Adding support for stamen tiles in Fusion will increase our list of available options for real-world contextual backdrops for our Map Definitions.
     34
     35== Proposed Solution ==
     36
     37For Fusion applications to have stamen tiles, they will need this script defined in their ApplicationDefinition xml in the root Extension element.
     38
     39{{{
     40<StamenScript>http://maps.stamen.com/js/tile.stamen.js?v1.3.0</StamenScript>
     41}}}
     42
     43In the MapGroup element, the user can define up to 3 different Map elements:
     44 * Type is `Stamen`
     45 * Extension/Options/type must be one of the 3 supported stamen layer types:
     46    * toner
     47    * terrain
     48    * watercolor
     49
     50For reference, the valid XML for these 3 layer types are specified below:
     51{{{
     52  <Map>
     53    <Type>Stamen</Type>
     54    <SingleTile>true</SingleTile>
     55    <Extension>
     56      <Options>
     57        <name>Stamen Toner</name>
     58        <type>toner</type>
     59      </Options>
     60    </Extension>
     61  </Map>
     62  <Map>
     63    <Type>Stamen</Type>
     64    <SingleTile>true</SingleTile>
     65    <Extension>
     66      <Options>
     67        <name>Stamen Terrain</name>
     68        <type>terrain</type>
     69      </Options>
     70    </Extension>
     71  </Map>
     72  <Map>
     73    <Type>Stamen</Type>
     74    <SingleTile>true</SingleTile>
     75    <Extension>
     76      <Options>
     77        <name>Stamen WaterColor</name>
     78        <type>watercolor</type>
     79      </Options>
     80    </Extension>
     81  </Map>
     82}}}
     83
     84Fusion will be updated to recognise these new elements. The BasemapSwitcher widget will be updated to recognize these new stamen layer types.
     85
     86== Implications ==
     87
     88Stamen tiles follows the same constraints as other external tile providers: The Map Definition in question must be in WGS84.PseudoMercator for tiles to line up properly.
     89
     90Client-side authoring tools will need to be updated to add and recognize these new XML elements.
     91
     92Usage of Stamen tiles (and OpenStreetMap) requires attribution. The copy of OpenLayers used by Fusion will be updated to include the required Attribution control and the Fusion map widget will include this control when internally creating the OpenLayers.Map instance.
     93
     94== Test Plan ==
     95
     96Test with sample Application Definitions with the above XML elements included.
     97
     98== Funding / Resources ==
     99
     100Community