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:
Add support for reading JSON files encoded in GeoJSON format.
Implement AzureMaps Provider in RadMap based on the following API https://azure.microsoft.com/en-us/services/azure-maps/
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:
Many tasks on RadMap require smooth zooming for the better user experience. For example, floor plans or facility layouts. Default zoom increments are too large for those tasks. We should provide a way to make zoom smooth while keeping zoom level as integer value.
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;