Currently MapShapeReader can't be used to load KMZ files.
Currently shape readers (KML, ESRI shape, SQL Geospatial) don't provide information about unsupported elements in sequence. They should either return list of the detected unsupported elements or throw €œUnsupported€ exception.
The RadMap.Providers property should support databinding to a collection of MapProviderBase in a ViewModel.
The map control does not support the border. It inherits the BorderBrush and BorderThickness properties from ItemsControl, but currently they can't be used for the design of the control.
It should be possible to specify zoom range where caption of the map shape will be visible.
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.
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.
Extend KML BalloonStyle.Text to support feature entity references (e.g. $[name]) - see http://code.google.com/apis/kml/documentation/kmlreference.html#balloonstyle for more information.
Currently BalloonStyle.Text supports only <p>, <b> and <font> elements -- extend it to support table/tr/td elements as well.
It should be possible to use scrollbars for the map panning. Customer should be able to turn on/off vertical and horizontal scrollbars arond the map's view port and use them to scroll the map.
The MapShapeReader converts each dbf record to the ExtendedData value. By default it converts numeric types to integer or double .Net type etc. If it can't convert a field, then the exception is thrown and it could be handled. It will be more prefered to return it using the Error property of arguments in PreviewReadCompleted and ReadCompleted event.
When using 'Kilometer' as the DistanceUnit, the Scale switches from kilometers to meters when zooming in. But when using 'Mile' the Scale does not switches from miles to feet.
The BingSearchProvider should be able to use StructuredSearchQuery in the SearchRequest. The BingSearchProvider should be able to use UserLocation in the UserProfile.
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.
Add ability to change visibility of the information layer depending on the zoom range.
RadMap Supports reading shp, kml files. Add feature to support the opposite , the items from the Visualization layer to be exported as shp, kml files.