ClusterGenerator's AutoExpandWhenSingle property is set to true by default.

Adding a single item in the VisualizationLayer with Clustering enabled results in a single cluster which is not expanded but it should be.

Available in LIB Version 2014.3.1326.

VS2010 crashes when the map is used within RadTabItem
After the BingMapProvider is added to the radMap the VS2010 crashes and has to be restarted.

Unspecified error shows in VS when RadMap dragged to design time.

The RadMap does not release all resources by the Dispose method when it uses the BingMapProvider.

When the DBF-file has short length of record and it contains a few number of records then the AsyncShapeFileReader causes the following error: 'The DBF file is invalid or has unsupported format'.

When the clustering is enabled in the visualization layer and the location of map item is changed dynamically then the item disappears if it is a single item (not within a cluster).

The pinch gesture does not zoom in/out the map in Silverlight.

Index Out of Range  Exception is produced sometimes when removing and adding points in PolylineData object runtime.

As a workaround,  you can use MS Polyline (MS shapes) or PolylineView (Bindable wrappers) added in the Layer.

Available in LIB Version: 2015.3.1026.

The tiles returned from the Bing rest imagery api are not using the latest road tile source. Customers are comparing our integrated maps to the Bing Maps website and complaining that our integrated maps are out of date. Microsoft has added "RoadOnDemand" as an imagerySet value to target the latest tiles. The currently implemented "Road" value is considered legacy.
Docs: https://msdn.microsoft.com/en-us/library/ff701716.aspx
Attached are images comparing the new Bing tiles and legacy.

Please follow this feature request already logged in our portal. 
https://feedback.telerik.com/Project/143/Feedback/Details/218677-map-add-the-canvas-modes-roadondemand-and-ordnanceservey-modes-in-the-bingrestm
Currently, you can implement custom map provider and hardcode the link addressing the RoadOnDemand service.

We will not add OrdnanceSurvey mode when we add CanvasModes and OnDemandmodes, as it requires more effort and different development setup.

The RadMap control does not support the mouse wheel zoom when it is used inside a ChildWindow.

The problem happens in the VisualizationLayer when map is zoomed in on a shape with the stroke thickness set. The stroke doesn't scale down until the map has stopped zooming. This creates an unwanted side effect where the borders of the shape can get really huge/thick while the user is zooming into the shape, and when the zooming stops, the borders jump down to thickness of 1. We should improve map shape visualization in the VisualizationLayer to avoid this side effect.

The MapShapeBindableWrappers such as the MapPolylineView should support binding to properties like the Visibility property.

If I have a list a RadObservableCollectio<Route> and I clear the collection, routes disappear form the map, but if I remove them one by one, they stay on the map at all times, even are clickable and all. 

When the RadMap contains visualization layer with map shapes and the RadMap is removed from visual tree while zooming is in process then the TargetInvocationException is thrown.

When the map shape is removed from the visualization layer while zooming is in process then the NullReferenceException is thrown.

RadMap's VisualizationLayer is bound to collection of business objects - MapItems.

If you perform replace in the ItemsSource collection: items[0] = new MapItem(), the RadMap throws "Collection Add Event Missing Item: ..." exception.

Available in LIB version: 2015.1.0604

RadMap's KML Reader throws argument exception if the KML file contains Styles with equal ids.

<Style id="inline1">

...

<Style id="inline1">

...

<Style id="inline1">

....

An exception is thrown (for each empty date) if the loaded data file (.dbf ) have a column with date time values and there are empty values. 

Available in LIB version: 2015.1.0604

InfrormationLayer has some Elements in it. Their attached property  telerik:MapLayer.Location is bound to Location from the ViewModel. The Radmap produces Exception.

The workaround is to set the Loacations directly in XAML or use the VisualizationLayer instead of the InformationLayer.

Fix is available in LIB Version 2015.2.914.