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
};
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[0]);
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.
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.
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.
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.
Map: DataTemplate is not applied correctly. On second click /zoom in/zoom out the items appear. The issue is not reproducible with Visualization Layer.
InformationLayer.GetBestView(...)) method produces incorrect results when working on MapPinPoint items that are part of the information layer. Please note that this issue is not reproducible with Visualization Layer.
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.
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.
Clusters may not be updated if users expand or collapse them while zooming animation is not finished.
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.
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.
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 the custom map provider supports levels range other than 1 to 20 then it could affect to tiles downloading performance.