When NavigationVisibility is set to Collapsed, a circle is left in our latest themes.

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

When RadMap is in DataTemplate / ControlTemplate of other control and its ZoomLevel (or the new Zoom) property is bound to ViewModel's property, the binding is broken by internal setting of the ZoomLevel/Zoom property and the expected ViewModel property is not set successfully.

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

Adding big-sized FrameworkElements in VisualizationLayer and then zooming in might result in disappearing of the element although it should cover the whole or large part of the viewport.

In some scenarios with fractional zoom, SetView method zooms higher than expected and the requested rect area is not entirely visible in the viewport.

Good Afternoon,

we use the RadMap's SelectionRectangleChanged event to allow the user to (de)select map elements with the box. In the event handler we use the layer's GetItemsInRectangle function to see what is within the selected area but this is where we encounter a problem with LineData objects. Dragging a selection rectangle that does not touch an edge but is close enough to it (likely within the bounding box of the LineData) it incorrectly recognizes the line as within the rectangle. See the attached screenshot for an example of a selection rectangle that should contain no elements within but actually reports the long line to its right as an element it contains. This can also be reproduced with the attached project:

• Ctrl + Mouse Left to drag a selection rectangle
• Mouse Left to pan, mouse wheel zo zoom. Shift + Mouse Left for zoom rectangle

1. Draw a selection rectangle on the very left or right outside the elements: Debug Output reports "Selected Edges: 0"
2. Draw a selection rectangle close to an edge but not touching it: Debug Output reports "Selected Edges: 1"
3. Draw selection rectangle that contains (parts of) an edge: Debug Output reports "Selected Edges: 1"

Regards
Dominik Schacht

 

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.

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.

When the VisualizationLayer is populated with FrameworkElement objects (often through the ItemTemplate) and the MapLayer.Location value of a FrameworkElement is updated at runtime, the element itself is not moved to the new location. This happens only if the FrameworkElement is outside of the viewport during the location change action.

To work this around, on location change, remove the data element from the ItemsSource and add it again.

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

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.

When the PathData contains Arc segment which looks as vertical half-circle then it is not displayed in VisualizationLayer.

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. 

The exception occurs in the SetLogicalWidth method of the MapShapeData class. 

Hello,

after setting the `ZoomStep` in our project to something smaller than 1 (a feature we are very pleased to receive in the latest update) we encountered a problem when zooming in and out of our map view. I have attached screenshots and an example project to reproduce the issue. It occurs wether the renderer is set to SoftwareOnly or default.

Steps to reproduce:

1. Start the example project (MapZoomInitial.png)
   
2. Scroll the mouse wheel one click in to zoom in one step
3. Scroll the mouse wheel one click out to zoom out again
4. Artifacts appear (MapViewAfterZoomInAndOut.png)