When you inherit BingRestMapProvider and BingRestTileMapSource, following the custom map provider approach
https://docs.telerik.com/devtools/wpf/controls/radmap/how-to/howto-custom-provider

the map does not display any tiles. This is due to internal property TopLayer not set correctly to the TileMapSource class.

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.

The ZIndex property change is not detected by the VisualizationLayer at runtime. 

Workaround: remove and then add back the item where the ZIndex is changed.

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

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)
   

Using wraparound True and Virtualization in VisualizationLayer.
When panning from left to right and placing rectangles over the requested regions, a gap could be seen on the left side. This is because the regions that get into viewport fire data request event when their top left point is inside the viewport. To cover the viewport, the topright point of the regions should be used instead.

If you update the Location of a map shape data object (for example, EllipseData, PolygonData, ect.) at run-time, while the clustering feature is enabled, the shape disappears.

To work this around, reset the clustering via the IsClusteringEnabled property when the Location changes.

this.ellipseShapeData = new Location(newLatitude, newLongitude);
this.visualizationLayer.ClusteringEnabled = false;
this.visualizationLayer.ClusteringEnabled = true;

The behavior can be observed with the following setups:

new WmsTiledProvider("http://4maps.geo-solutions.it/geoserver/osm/wms")

            {
                Layers = "osm",
                Version = "1.3.0",
                Projection = "CRS:84" // WGS84, 1.3.0 Standard compatible
            };

and 

new WmsTiledProvider("http://4maps.geo-solutions.it/geoserver/osm/wms")

            {
                Layers = "osm",
                Version = "1.1.0",
                Projection = "EPSG:4326" // WGS84, 1.1.0 Standard compatible
            };