|Version 2 (modified by 13 years ago) ( diff ),|
MapGuide RFC 72 - Commercial Map Service Support
This page contains an change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.
|RFC Template Version||(1.0)|
|Submission Date||(Date/Time submitted)|
|Last Modified||Arthur Liu Timestamp|
|Implementation Status||under development|
|Assigned PSC guide(s)||Tom Fukushima?|
|Voting History||(vote date)|
Fusion provide a solution to integrate the commercial map services into standard template:
- Add some script tags to index.html manually. These scripts indicate commercial mapping api providers and unique api keys supplied by these providers.
- Modify the application definition to include the commercial map service layers.
MapGuide templates should have the capability to support the commercial map services too, and we also need to provide a more convenient approach to add scripts.
- Save the commercial mapping api providers and keys as extension in application definition.
- MapGuide templates load the extension information from the application definition , and add the script tags into index.html on demand.
So users just need to provide an application definition with extension, then they will obtain the commercial mapping services.
Just add a script tag into index.html of MapGuide templates, which used for loading extension information from application definition.
For those application definitions which do not have extenstion information, there's no additional burden.
Test 5 MapGuide templates(aqua, limegold, maroon, slate and turquoiseyellow) to verify if they could support the commercial map services.
Supplied by Autodesk.