We have created an application where a map fills most of the page, but we also have menus on the left and right side that will open and close depending on what the user is doing. In some cases the user will want to keep one or both the menus open all the time, so we have also provided the possibility to pin the menus.

The problem is that when the menus are pinned, we also change the size of the map, and when we do this any shapes that are drawn on the map disappear. We can make them reappear by zooming in or out, and this is only a problem when UseSpringAnimations is set to false, as setting this to true makes the map force some zoom action.

The caption of map shape should be updated automatically when the CaptionTemplate is changed. When its content is changed then it should be located according to hotspot if it used in the template.
The caption should be updated according to the map shape properties. For example when the MapShape.Visibility property is set to Collapsed then the caption should be collapsed. Also if the shape is moved using the information layer API functionality, then its caption should be moved too.

Also it should be possible to define different font size, foreground color, font name for individual shapes.

Implement WrapAround mode in Silverlight, just like it behaves in WPF. http://docs.telerik.com/devtools/wpf/controls/radmap/features/wraparound

When a user clicks the center button on the separate navigation control (the standard buttons are collapsed) then a line appears at the center-bottom position.

Reason for closing/ declining:

The separate MapNavigationControl is designed to be used outside RadMap.

The bug is only reproducible when the control is placed in the ItemsCollection of the RadMap which is not supported. 

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).

RadMap with Clustering enabled on Visualization layer. Pushpins whose locations have equal or almost equal Latitudes or Longitudes are shown on particular zoom level (for example 19). You see them when clicking on the cluster. If the MaxZoomLEvel is set to be lower than 19, the pushpins are not placed in their correct positions after clicking on clusters and zooming out with mouse multiple times.

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.

MapPolyline (Informationlayer) or PolylineData (VisualizationLayer) disappear on higher zoom levels.


The origin of this issue is that Silverlight has limitation for the size of the polyline objects. Once this limit is reached, the calculations are wrong and the polyline is displayed incorrectly.

Possible workaround could be adding multiple smaller polylines / lines instead of one big polyline with many intermediate points.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

Any errors related to the image, however, cause the ImageFailed event from the UriImageProvider.Image property to fire repeatedly and never stop. This has been caused by 404 File Not found errors from missing images and also by a strange issue with Internet Explorer where large PNG images sometimes won't show.

Workaround:
Remove the image provider that works incorrectly using the Image.ImageFailed event.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

Bing map provider does not work over HTTPS due to the fact that the tile images of Bing currently use different URLs for HTTP and HTTPS.

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.