Currently the InformationLayer.GetBestView method takes in account visible size of the markers (in pixels) and makes best possible assumption about its geographical size when calculating location rectangle. But size in pixels corresponds to different geographical size (in latitude/longitude degrees) depends on the zoom level. So it could take 2-3 times to get really optimal zoom level depends on the initial zoom level. The InformationLayer.GetBestView method should be changed to provide precise result at once regardless of the initial zoom level.

Current implementation of the SearchResultSet have not AvailableFilters property and BingSearchProvider don't pass these values to the response.

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

The BingSearchProvider should be able to use StructuredSearchQuery in the SearchRequest.
The BingSearchProvider should be able to use UserLocation in the UserProfile.

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.

Add Oracle spatial support to RadMap.

The Bing Map provider displays the "no camera" icons from bing’s imagery server when the images is absent for the current zoom on high zoom levels. The default behavior should be changed to zooming the lowest available resolution instead of showing the "no camera" icon.

The Altitude coordinate should be supported by the Location class.

The RadMap control should support for a Crosshair to appear at the current Center.

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.