MapPath shape doesn't support data binding on the level of the MapPathFigure and MapPathSegment in WPF. This feature is implemented in the new visualization engine -Visualization layer and the bindable wrappers - PathView, PathVigureView, PathSegementView , etc.
InformationLayer.GetBestView(...)) method produces incorrect results when working on MapPinPoint items that are part of the information layer. Deleting this item because there is a copy of it here => https://feedback.telerik.com/Project/143/Feedback/Details/88878-map-informationlayer-getbestview-produces-incorrect-results-when-working-on Also please have in mind tha this bug is not reproducible with VisualizationLayer.
Map: DataTemplate is not applied correctly. On second click /zoom in/zoom out the items appear. The issue is not reproducible with Visualization Layer.
When the custom map provider supports levels range other than 1 to 20 then it could affect to tiles downloading performance.
BirdsEye view doesn't work after trying to look at an area which does not contain birds eye imagery data Steps for reproducing: 1. Zoom into area with no birds eye view imagery data. Enable Birds eye view. Verify that no tiles are loaded. 2. Change back to Road view, navigate to an area where you know there is bird's eye view imagery. 3. Zoom into the area. Enable Bird's Eye view a second time: The tiles are not loaded.
Visualization layers are removed from the RadMap in a moment when MapShapeData objects are being processes (their geometries are processed). This leads to exception in MapShapeData.cs ' SetLogicalWidth method. Available in R2 2017 SP
Polyline object in VisualizationLayer is not updated if you clear its Points collection. The expected behavior is that the Polyline is not visible on the Map. As a workaround, you can remove the PolylineData directly from the Layer. this.layer.Items.Remove(polylineData);
When you have two providers - BingMapProvider and custom TiledProvider - and the map source of the second provider (the custom one) is changed, the updated provider is drawn under the provider defined before it in the Providers collection (the BingMapProvider). To work this around you can call the BingMapProvider's SetMapSource() method after the source of the custom provider is changed. // set the custom provider source bingMapProvider.SetMapSource(bingMapProvider.SupportedSources);
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.
Concurreny issue - exception in PathGeometryData.GetScreeenGeometry() when the geometry is updated runtime. Custom MapGeometryView which updates its GeometryData runtime. This leads to cocncurrency issue in VisualizationLayer and its shape processcing code. This leads to Exception in GetScreenGemetry() method of PathGeometryData.
Width / Height of the MapEllipseView are bound to doubles from ViewModel. Runtime change to 0 does not hide / remove the Ellipse from the Map. This is a bug in the MapShapeBindableWrapper's Geometry update code. The workaround is to use the Visibility of the MapEllipseView in order to hide it. Other workaround could be using FrameworkElements (Ellipse, Polyline, Rectangle) instead of BindableWrappers (MapEllipseView, MapPolylinerView, MapRectangleView).
Map with VisualizationLayer (VL) bound to collection of objects. VL uses an ItemTemplate consisting of MapEllipseView object whose Location Width and Height properties are bound to ViewModel's properties. On a button click, the ItemsSource of the VL is refreshed. However, the ellipses do not appear until a zoom action is performed.
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.
Map has 2 providers initially - BingMapProvider and Custom Provider A. Runtime we remove A and add B - other custom provider. As a result - the image from bingmapprovider (world continents) is not displayed. As a workaround, users need to clear all providers and then Add BingMapProvider then add provider B.
In the KML file , Locations are separated witch commas instead of whitespaces , for example: 34.84161774,32.11002378,0,34.8416625,32.10999705,0 The RadMap produces "Input string is in icorrect format" exception. However, other tools read the kml file successfully.
Map with ItemsSource bound to collection is hosted in RadPane . By closing the pane or by using LoadLayout() of RadPane - NulReferenceException is thrown. Available in LIB version: 2015.1.1603
BirdsEye view doesn't work after trying to look at an area which does not contain birds eye imagery data Steps for reproducing: 1. Zoom into area with no birds eye view imagery data. Enable Birds eye view. Verify that no tiles are loaded. 2. Change back to Road view, navigate to an area where you know there is bird's eye view imagery. 3. Zoom into the area. Enable Bird's Eye view a second time: The tiles are not loaded. Reason for declination: The feedback item is declined due to duplication with the one below: http://feedback.telerik.com/Project/143/Feedback/Details/113358-map-fix-a-problem-when-birdseye-view-doesnt-work-after-trying-to-look-at-an-are Please follow it instead.
When the PathData contains Arc segment which looks as vertical half-circle then it is not displayed in VisualizationLayer.