Changes between Version 6 and Version 7 of MapGuideRfc170


Ignore:
Timestamp:
May 21, 2019, 8:00:04 AM (5 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc170

    v6 v7  
    88||RFC Template Version||(1.0)||
    99||Submission Date||||
    10 ||Last Modified||16 Apr 2019||
     10||Last Modified||22 May 2019||
    1111||Author||Jackie Ng||
    12 ||RFC Status||draft||
     12||RFC Status||Ready for review||
    1313||Implementation Status||sandbox in progress||
    1414||Proposed Milestone||3.3||
     
    3636
    3737This RFC will tie up the following loose ends:
    38 
    39 === Ability to create MgMap instances from Map Definitions linked to XYZ tile sets ===
    40 
    41 The initial implementation did not allow an MgMap instance to be created from a Map Definition that links to a TileSetDefinition that uses the XYZ tile provider.
    42 
    43 The reason for this was at the time, we didn't know what finite scale list to assign to such a MgMap which is required to properly determine the correct scale index parameter when requesting tiles. A tile set using the Default tile provider would provide this information, yet the XYZ one does not.
    44 
    45 In actuality, the finite scale list for an XYZ tile set is actually hard-coded and already known. It is the same scale list generated by Maestro/Infr. Studio for a WGS84.PseudoMercator Map Definition so that it would line up with Google/Bing/OSM layers when viewed within a Fusion Flexible Layout. So by providing this same scale list to the MgMap, we can allow MgMap instances to be created from Map Definitions that link to XYZ tile sets.
    4638
    4739=== Configurable TileExtentOffset ===