OpenStreetMap provider uses OpenStreetMapSources which have MaxZoomLevel 18.
When Wraparound of the Map is True and you move (with SetView or ZoomLevel + Center properties) the map to zoomlevel > 18 , no tiles are loaded.
WMTS is a standard protocol for delivery of tiles map data - see https://en.wikipedia.org/wiki/Web_Map_Tile_Service It should be possible to write code to understand pretty much any service complying with the specification. It would be good if RadMap could be extended to enable it to understand the WMTS specification and allow WMTS data to be used.
Implement OpenStreetMap search provider. Similar to BingSearchProvider (http://docs.telerik.com/devtools/wpf/controls/radmap/features/search). Currently , to implement location search with OpenStreetMap provider, you can use the Nominatim API: https://wiki.openstreetmap.org/wiki/Nominatim
Currently, when you use the BingRestMapProvider and the BingRestSearchLocationRequest the found locations are formatted using the System.Text.Encoding.Default encoding. This way if the found location contains unsupported characters they won't be shown properly. Introduce a property for the BingRestSearchLocationRequest class that allows you to set the Encoding.
Currently, you can achieve this by using RotateTransform and clipping the container that holds the RadMap control. For example: <Grid RenderTransformOrigin="0.5,0.5" Width="500" Height="500"> <Grid.RenderTransform> <RotateTransform Angle="45" /> </Grid.RenderTransform> <Grid.Clip> <EllipseGeometry Center="250,250" RadiusX="250" RadiusY="250" /> </Grid.Clip> <telerik:RadMap ZoomLevel="6" Center="37, -120"> <telerik:RadMap.Provider> <telerik:OpenStreetMapProvider /> </telerik:RadMap.Provider> </telerik:RadMap> </Grid>
RadMap with Wraparound = True. Custom TiledProvider with custom TileSource is used. GetCachedTile is overridden to get the cached tiles in the local file system. When zooming , endless invocation of GetCachedTile method is performed which leads to increasing of CPU usage.
Add a way to control the pan / zoom animation duration. Currently the properties which control these animation durations are private in MultiScaleImage.cs
Implement BING REST Traffic API in BingRestMapProvider. https://msdn.microsoft.com/en-us/library/hh441725.aspx This will allow clients request traffic incident. This WON'T be enough to display traffic tiles or get congestion data - this usage is limited. Check answer from R. Brundritt => https://social.msdn.microsoft.com/Forums/en-US/20020cb8-5e8f-4fe6-abda-ffdcc0edb77e/bing-map-rest-traffic-api-congestion?forum=bingmapssilverlightwpfcontrols Note: The following tutorial might be helpful if clients need to use BING REST Traffic API outside RadMap. https://msdn.microsoft.com/en-us/library/jj819168.aspx Note: In R2 2017 BingMapTrafficProvider will be deleted from our code base due to limitations in the BING Maps Developer API terms of use. Also the service which is behind this provider might be stopped in 2017 so applications using this provider with old version of UI for WPF/ Silverlight might also stop working properly.
MiniMapWidth and MiniMapHeight have default values 250 and 200. If you use different values, for example 250 and 250, panning the RadMap can result in jumping the minimap - unexpected zoom in/out. This is easier to observe with MiniMap, outside RadMap. Playing with Width / Height of the MiniMap might workaround the issue.
Expose a property that allows you to get the user state in the SearchLocationError event arguments (BingRestSearchLocationErrorEventArgs). Currently, only the SearchLocationCompleted event args give this information. You can work this around using the following approach: You can create a custom BingRestMapProvider and override its OnSearchRequestCompleted() method. There you can get the UserData from the DownloadStringCompletedEventArgs. Check the attached project.
The UriImageProvider will support loading the geotiff image header to find the location boundaries. When the geotiff image contains this information then the GeoBounds of the UriImageProvider will be specified automatically.
An OutOfMemmoryException is thrown under the following conditions: 1. The map displays its data using the VisualizationLayer populated with MapShapeData object. 2. The zoom level is changed to Neighborhood using the Zoom button from the map's navigation. 3. The zoom button is hovered Note: The MapShapeData should be visible when the zoom is applied The exception is not reproducible if the project's Platform is set to x64. Since Q1 2016, the BitMapCaching of RadMap is turned off by default and the issue is not reproducible unless you turn the caching on. Possible Workarounds: - the exception is not reproducible if the project's Platform is set to x64 - double check that UseBitMapCahe property of the Visualizationlayer is set to False. When False, the issue is not reproducible.
It should be possible to rotate camera in the birds eye mode of the Bing map provider.
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.