The VisualizationLayer will support using the collection views such as System.Windows.Data.ListCollectionView as its items source.
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.
Add support for reading JSON files encoded in GeoJSON format.
Add support for digitizing complex wkt geometries.
Include support for adding, moving and deleting vertices.
/Brian
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
};
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);
Add an API to load Dark tiles in the provider.
This mode can be achieved by showing tiles from the Carto Dark tile server.
Here maps has the ability to render map tiles with traffic. They include a freemium tier unlike some of the others.
https://developer.here.com/documentation/map-tile/topics/quick-start-map-tile.html
https://developer.here.com/documentation/map-tile/topics/resource-base-tile-intro.html
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]);