ThinkGeo.com    |     Documentation    |     Premium Support

Bing Maps and Keys (Azure Maps)

#1

Looks like Bing maps has rolled over to Azure Maps and that is where you get subscription keys from. You can’t get keys from the links the demo app has.

Before I sign up with “Azure”, does the BingMapsLayer use any keys etc from Azure maps, or does there need to be a new AzureMapsLayer created in ThinkGeo?

2 Likes
#2

Hi Chris,

Azure Maps is not supported through BingMapsLayer. I’ve added to the list and we will add the AzureMapsLayer.

And just for your reference, Azure Maps serves raster maps through Static Image (based on CenterPoint) instead of XYZ which is what BingMaps is using, Also Azure Maps supports Vector Tiles which BingMaps doesn’t support. We will dig in a bit more but I think we will support the raster images first.

Thanks,
Ben

#3

Thanks for the heads up,

Saves me a nasty trip down that Rabbit Hole for now.

Chris

#4

Any news on Azure Maps support?

#5

Hi Mustafa, we are aiming for having it by next major release v14.3, around May this year.

#6

Any news on this? I can see 14.3 is released, but unsure if it contains support for Azure Maps overlay.

#7

Hi Mustafa,

AzureRasterMapAsyncLayer is already available in the latest beta v14.4.0-beta020, and it will be available in v14.3.1 (which will be released next week). Here is the code:

var layer = new AzureRasterMapAsyncLayer("AzureMapKey", AzureMapsRasterTileSet.Imagery);

We are doing the test and the BingMap Sample in HowDoI will be replaced by AzureMaps.

Thanks,
Ben

#8

Hi @Mustafa_Temiz,

The v14.3.1 is now released, AzureMapsRasterAsyncLayer (we renamed it) and AzureMapsRasterOverlay are now available. Here is the changelog: Changelog - ThinkGeo Docs

Please note: Microsoft requires all Azure Maps users to display attribution on the map.

  • The new AzureMapsRasterOverlay handles this automatically.
  • If you’re using AzureMapsRasterAsyncLayer , please note that it is a low-level API and does not have access to the map canvas. As a result, you are responsible for rendering the attribution manually. The layer provides an API— AzureMapsRasterAsyncLayer.GetAttributionAsync —which returns the required attribution information based on the current extent and scale.

Thanks,
Ben