Changes between Version 6 and Version 7 of MapGuideRfc140

Timestamp:

03/17/15 04:00:53 (10 years ago)

Author:

jng

Comment:

--

MapGuideRfc140

@@ -1122 +1122 @@
 Client applications have already been modified to handle this expectation.
 
-An important constraint of the XYZ tiling scheme is that XYZ resolves to real world coordinates. Therefore any map you wish to make available as an XYZ tileset must be in a coordinate system that is either ~~LL84~~ WGS84.PseudoMercator or transformable from ~~LL84~~ WGS84.PseudoMercator. Maps based on arbitrary coordinate systems cannot be served as XYZ tile sets.
+An important constraint of the XYZ tiling scheme is that XYZ resolves to real world coordinates. Therefore any map you wish to make available as an XYZ tileset must be in a coordinate system that is either ~~LL84~~ WGS84.PseudoMercator or transformable to ~~LL84~~ WGS84.PseudoMercator. Maps based on arbitrary coordinate systems cannot be served as XYZ tile sets.
 
 As mentioned above, the MgMap::Create() method now supports Tile Set Definitions. However for the public API, the method will only support Tile Set Definitions using the "Default" tile provider. The reason for this is that when creating a MgMap, it also needs to be initalized with the coordinate system and finite scale lists, and only Tile Set Definitions using the "Default" tile provider can provide this information. It is not possible to create a MgMap using a Tile Set Definition that uses the XYZ provider. Such attempts will throw a MgUnsupportedTileProviderException.