MapGuide RFC 146 - Stamen tile layer support for Fusion

This page contains a change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.

Status

RFC Template Version	(1.0)
Submission Date	5 Sep 2014
Last Modified	14 Sep 2014
Author	Jackie Ng
RFC Status	adopted
Implementation Status	completed
Proposed Milestone	3.0
Assigned PSC guide(s)	(when determined)
Voting History	(vote date)
+1	Jackie,Kevin,Trevor
+0
-0
-1
no vote	Crispin,Haris,Gordon

Overview

This RFC proposes to add support for stamen tiles in Fusion

Motivation

​Stamen maps provides stylish cartographic renderings of OpenStreetMap data.

Adding support for stamen tiles in Fusion will increase our list of available options for real-world contextual backdrops for our Map Definitions.

Proposed Solution

For Fusion applications to have stamen tiles, they will need this script defined in their ApplicationDefinition xml in the root Extension element.

<StamenScript>http://maps.stamen.com/js/tile.stamen.js?v1.3.0</StamenScript>

In the MapGroup element, the user can define up to 3 different Map elements:

• Type is Stamen
• Extension/Options/type must be one of the 3 supported stamen layer types:
  • toner
  • terrain
  • watercolor

For reference, the valid XML for these 3 layer types are specified below:

  <Map>
    <Type>Stamen</Type>
    <SingleTile>true</SingleTile>
    <Extension>
      <Options>
        <name>Stamen Toner</name>
        <type>toner</type>
      </Options>
    </Extension>
  </Map>
  <Map>
    <Type>Stamen</Type>
    <SingleTile>true</SingleTile>
    <Extension>
      <Options>
        <name>Stamen Terrain</name>
        <type>terrain</type>
      </Options>
    </Extension>
  </Map>
  <Map>
    <Type>Stamen</Type>
    <SingleTile>true</SingleTile>
    <Extension>
      <Options>
        <name>Stamen WaterColor</name>
        <type>watercolor</type>
      </Options>
    </Extension>
  </Map>

Fusion will be updated to recognise these new elements. The BasemapSwitcher widget will be updated to recognize these new stamen layer types.

This implementation has already been carried out in the ​stamen fusion sandbox. Upon adoption of this RFC, this sandbox will be merged into Fusion trunk.

Implications

Stamen 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.

Stamen is not a replacement for OpenStreetMap layers. Stamen will be an additional option to Google/Bing/OpenStreetMap.

Client-side authoring tools will need to be updated to add and recognize these new XML elements.

Usage 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.

Test Plan

Test with sample Application Definitions with the above XML elements included.

Funding / Resources

Community