But this iteration of Bing Maps now requires an API key to use it. So you sign up for an API key in the bing maps portal. Now where you do put this thing?
Well, here's a new release of MapGuide Maestro to help you with this very task among some new features and fixes.
Updated Fusion editor for Bing Maps
The fusion editor has been updated to work against the current iteration of Bing Maps. It has a new field for you to put your Bing Maps API key
When you put in the key and clicked Set API key it will write the API key into the top-level BingMapKey extension element of the Application Definition XML.
Also the available bing layer list has been updated to match what the current iteration provides.
The only difference is that the base layer formerly known as the "Hybrid" base layer has been renamed to "AerialsWithLabels". So if you use the bing hybrid layer you need to replace it with AerialsWithLabels.
This release of Maestro also includes new validation rules for Application Definitions to catch these new Bing Maps issues.
Auto-Configured Spatial Contexts in WMS Configuration Documents
In my adventures of consuming WMS services in MapGuide and building the initial WMS configuration document, I've been consistently observing a pattern like this:
The pattern being, that the names of the discovered spatial contexts usually follow the pattern of "EPSG:XXXX", yet we had to then go and manually fill in the correct coordinate systems one by one, even though the EPSG code is right there in the name!
With this release, we now automatically infer and fill in such coordinate systems for you
Other Changes
- Fixed inability to preview maps using the local viewer if the map uses a transparent background color
- Refine the error message when attempting to calculate meters-per-unit in MgCooker and you have no map or tile set selected. Selected is a misnomer, you have to actually check the respective tree node, and the error message has been updated to reflect that.
- Package updates to DockPanelSuite and Newtonsoft.Json
Download
No comments:
Post a Comment