Add CombinedGeometryData  in VisualizationLayer. 
Properties:
   Geometry1 (GeometryData) ,
   Geometry2 (GeometryData) and 
   CombineMode similar to the CombinedGeometry in WPF.

The current behavior sets the ZoomLevel internally which is number rounded to the best possible zoom which is of type double.
Make this API sets the Zoom property instead.

With the current implementation of the RadMap control, the default value which will be used for connecting in the internal services is "http". This causes the tiles to not be retrieved if the firewall allows only "https".

Make it possible to use a vector tile provider in the RadMap control.

Currently the "FORMAT" is hardcoded to "PNG". We can expose a way to modify it through the WmsTiledProvider.

Currently user cannot hook for event notifying that clusters are regenerated. ZoomChanged is not reliable due to zoom animations and dispatching logic internally.

The fix for this issue is available with LIB (version 2018.3.1210) released on Monday, December 10.

Implement AzureMaps Provider in RadMap based on the following API https://azure.microsoft.com/en-us/services/azure-maps/

There is a change in the Open Street Map Cycle and CylcleTransport services and they require an API key. Without it the service will returned tiles with a watermark saying "API KEY REQUIRED". Currently, the OpenStreetProvider doesn't expose a mechanism for providing a key. 

At this point you can provide a key by creating a custom map provider deriving from OpenStreeMapProvider and also a custom OsmTileMapSource. And override the original URL to use also an API Key.

public class CustomOpenStreetMapProvider : OpenStreetMapProvider
{
    public CustomOpenStreetMapProvider()
    {
        string sourceKey = (typeof(OpenStreetCycleTransportSource)).FullName;
        this.MapSources[sourceKey] = new CustomOpenStreetCycleTransportSource("your api key here");           
    }
}
 
public class CustomOpenStreetCycleTransportSource : OsmTileMapSource
{
    private static string UrlFormat = @"http://{prefix}.tile.thunderforest.com/transport/{zoom}/{x}/{y}.png?apikey={apikey}";
    private string apiKey;
 
    public CustomOpenStreetCycleTransportSource(string apiKey)
        : base(UrlFormat)
    {
        this.apiKey = apiKey;
    }
 
    protected override Uri GetTile(int tileLevel, int tilePositionX, int tilePositionY)
    {
        Uri originalUri = base.GetTile(tileLevel, tilePositionX, tilePositionY);
        string newUri = originalUri.OriginalString.Replace("{apikey}", this.apiKey);
        return new Uri(newUri);
    }
}

<telerik:RadMap>
    <telerik:RadMap.Provider>
        <local:CustomOpenStreetMapProvider/>
    </telerik:RadMap.Provider>
</telerik:RadMap>

Add the CanvasDark, CanvasLight, CanvasGray, RoadOnDemand and AerialOnDemand modes in the BingRestMapProvider.

Currently it supports only Aerial, Road and BirdsEye and their variants with labels.

Check the imagerySet parameter here: https://msdn.microsoft.com/en-us/library/ff701724.aspx

Ordnance Survey will not be added among with these modes.

Add public GetCoercedLocationRect method to support the existing GetCoercedLocation.

This is crucial in WrapAround + Virtualization scenarios because 180 longitude location is generally considered in the rande [-180;180] but Region with west-east Longitudes like [180-240] should be coerced to [-180; -120].


Available in LIB version: 2016.3.1114

Currently RadMaps Geocode, Search and Route providers are based on SOAP.

The Bing Maps discontinue their SOAP services in June 2017.

https://blogs.msdn.microsoft.com/rbrundritt/2016/06/22/bing-maps-v8-web-control-released/ 

The Bing REST Services API  (https://msdn.microsoft.com/en-us/library/ff701713.aspx?f=255&MSPPError=-2147217396) includes:

- Imagery API 

    -- Imagery metadata (used for downloading image tiles - already implemented in BingRestMapProvider)

- Routes API 

- Location API

- Elevations API


For R1 2016 we will implement:

Routes API which will be replacement of SOAP based BingRouteProvider

Locations API which will be replacement of SOAP based BingGeocodeProvider

Elevations API which will be new API and has no existing SOAP replacement
==================================================================================
Available in R1 2017 Official Release Version.

Many tasks on RadMap require smooth zooming for the better user experience. For example, floor plans or facility layouts. Default zoom increments are too large for those tasks. We should provide a way to make zoom smooth while keeping zoom level as integer value.

When the selection is started on map control then it can be cancelled using the Escape key.

Currently only Mercator projection is supported. We should add support for other projections. Shape file reader should be able process .prj file and setup correspondent projection to the EmptyProvider. The Bing and OpenStreet map providers show map using Mercator projection, so they can't use any other projections to show map shapes (KML or ESRI).

Is there a way to get the map to continuously scroll without seeing the gray area? As an example, GoogleMaps, MapQuest, etc.. let you scroll left to right without getting to the "end of the world", it just continues to wrap around. I'm trying to avoid seeing the gray when I scroll too far left or right.

The feature for WPF will be available with R3 2016 in September.

Export RadMap to screenshot.

WPF: We will add ExportToImage public method for WPF in R1 2017 with option whether to include map objects from Information/VisualizationLayer.

SL: There is a Silverlight limitation in WriteableBitmap:

https://social.msdn.microsoft.com/Forums/en-US/a5d59a36-ec26-4715-a707-dd0463ff0f46/writeablebitmap-has-protected-content-pixel-access-is-not-allowed?forum=bingmapssilverlightwpfcontrols

https://msdn.microsoft.com/en-us/library/system.windows.media.imaging.writeablebitmap%28VS.95%29.aspx?f=255&MSPPError=-2147217396

One partial solution if you use Bing Maps in RadMap is to use the Bing REST Static Map Imagery in order to download Image replicating the current viewport and zoomlevel of the RadMap.

     Bing REST Static Map => https://msdn.microsoft.com/en-us/library/ff701724.aspx 

     Using Bing REST API with .NET => https://msdn.microsoft.com/en-us/library/jj819168.aspx

Available in R1 2017 Official Release Version.