Currently, the RadMap control does not allow localizing the text in the vector tiles. We could include such support.

Add built-in support for elevation, routing and search location services coming from the Azure Maps service. These are the same features as in the BingRestMapProvider, which will be obsolete in 2025.

• Search Location
• Routing
• Truck Routing
• Elevation

Add a built-in API that can be invoked from the AzureMapProvider. The API should allow you to search for locations similar to the BingRestMapProvider's search location API.

This is to better address issues with missing pbf files for certain zoom levels. 
Default behavior - scaling cached map images form lower levels - could result in blurry images.
Wanted behavior - rescale lower zoom level pbf files resulting in higher quality images.

Implement AzureMaps Provider in RadMap based on the following API https://azure.microsoft.com/en-us/services/azure-maps/

Make it possible to use a vector tile provider in the RadMap control.

Add an event that allows you to listen for tiles download finished on the provided. The event should fire only after all tiles for the current viewport are downloaded.

Add support for reading JSON files encoded in GeoJSON format.

Add CombinedGeometryData  in VisualizationLayer. 
Properties:
   Geometry1 (GeometryData) ,
   Geometry2 (GeometryData) and 
   CombineMode similar to the CombinedGeometry in WPF.

The current behavior sets the ZoomLevel internally which is number rounded to the best possible zoom which is of type double.
Make this API sets the Zoom property instead.

With the current implementation of the RadMap control, the default value which will be used for connecting in the internal services is "http". This causes the tiles to not be retrieved if the firewall allows only "https".

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.

Add support for rendering heatmap visualization over the map, based on a set of points and their density.

Add support for digitizing complex wkt geometries.

Include support for adding, moving and deleting vertices.

 

/Brian

 

Add API which allows to manually parse and create MapShapeData objects from the shape file read by the AsyncShapeFileReader (part of VisualizationLayer). This will be useful if you want to modify or replace shapes during their reading. Or if you want to handle errors with invalid shape file geometries.

Currently the "FORMAT" is hardcoded to "PNG". We can expose a way to modify it through the WmsTiledProvider.

Currently, you can export the map only when it is added to the visual tree and fully rendered. Add support for an export without adding the map control to the UI. Consider adding a service that does this or something similar.

Currently user cannot hook for event notifying that clusters are regenerated. ZoomChanged is not reliable due to zoom animations and dispatching logic internally.

For example the TickMarkCount property. Modifying it, won't update the fill color of the shapes on the map.

A possible solution:

this.MyColorizer.Colorize(visualizationLayer.Items);
            foreach (var shape in this.visualizationLayer.Items.OfType<MapShapeData>())
            {
                if (shape.IsSelected)
                    shape.UseSelectedFill();
                else if (shape.IsHighlighted) shape.UseHighlightFill();
                else shape.UseRegularFill();
            };

Add an API to load Dark tiles in the provider.

This mode can be achieved by showing tiles from the Carto Dark tile server.