Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Fusion Editor to replace Bing (VirtualEarth) with Bing Maps #38

Closed
6 of 7 tasks
jumpinjackie opened this issue May 3, 2017 · 0 comments
Closed
6 of 7 tasks

Update Fusion Editor to replace Bing (VirtualEarth) with Bing Maps #38

jumpinjackie opened this issue May 3, 2017 · 0 comments
Assignees
@jumpinjackie
Milestone
6.0m7

Comments

@jumpinjackie
Copy link
Owner

jumpinjackie commented May 3, 2017 •
edited

Bing v7 controls (VirtualEarth) will shutdown on Jun 30th 2017

https://blogs.bing.com/maps/June-2016/Bing-Maps-V8-Web-Control-Released

Work is already being done to make sure Fusion switches over to the apikey-based service.

http://trac.osgeo.org/fusion/changeset/2971/sandbox/adsk/3.2o

To make sure Maestro can create/edit Fusion layouts with this change in place, we need to:

  • Remove existing Bing (VirtualEarth) layer types.
  • Add Bing Maps equivalent layer types to the UI. NOTE: When saving, the Fusion base layer type is still VirtualEarth
    • Aerial
    • Road
  • Provide a field to enter the Bing Maps API key. When saving, put this value into a top-level BingMapKey extension element of the Application Definition. When loading, load the API key into the field from this location if it exists.
  • Optionally/Ideally:
    • If we load an appdef and it has references to the old Bing (VirtualEarth) layers, raise some kind of warning about this.
    • Detect this case in the Maestro resource validator.
@jumpinjackie jumpinjackie added this to the 6.0m7 milestone May 3, 2017
@jumpinjackie jumpinjackie self-assigned this May 3, 2017
jumpinjackie added a commit to jumpinjackie/mapguide-react-layout that referenced this issue May 3, 2017
@jumpinjackie
Add Bing Maps support.
72077c2 
NOTE: If loading from an Application Definition, you will need to put your Bing Maps API key in the top-level <BingMapKey> extension property of the Application Definition document. This viewer will look for this key and require it in order to add Bing Maps layers.

Maestro will be updated to be able to edit this (see: jumpinjackie/mapguide-maestro#38)

Fixes #189
jumpinjackie added a commit that referenced this issue Jun 26, 2017
@jumpinjackie
#38: Update Fusion editor to replace Bing (VirtualEarth) with Bing Maps.
b443a56 
 - Hybrid is replaced with AerialsWithLabels
 - A new field is included to input the (now required) Bing Maps API key. This is stored in the top-level "BingMapKey" extension element of the edited Application Definition
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jumpinjackie jumpinjackie

Labels
None yet
Projects
None yet
Milestone
6.0m7
Development

No branches or pull requests
1 participant
@jumpinjackie