TileLayer has 2 renderers: canvas and gl(default). When browser doesn't support webgl(IE9/10), it will switch to canvas automatically.
The differences between them are:
| renderer | IE9/10 | 3D | CORS required |
|---|---|---|---|
| gl | NO | YES | YES |
| canvas | YES | NO | NO* |
* When exporting map's image by calling map.toDataURL, CORS is required and TileLayer must set crossOrigin in options.
<!DOCTYPE html>
<html>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>TileLayer and Geo-Projections - TileLayer with Canvas renderer</title>
<style type="text/css">
html,body{margin:0px;height:100%;width:100%}
.container{width:100%;height:100%}
</style>
<link rel="stylesheet" href="https://unpkg.com/maptalks/dist/maptalks.css">
<script type="text/javascript" src="https://unpkg.com/maptalks/dist/maptalks.min.js"></script>
<body>
<div id="map" class="container"></div>
<script>
var map = new maptalks.Map('map', {
center: [-0.113049,51.498568],
zoom: 13,
baseLayer : new maptalks.TileLayer('base',{
renderer : 'canvas', // set TileLayer's renderer to canvas
// crossOrigin : 'anonymous',
urlTemplate: 'https://{s}.basemaps.cartocdn.com/light_all/{z}/{x}/{y}.png',
subdomains: ["a","b","c","d"],
attribution: '© <a href="http://osm.org">OpenStreetMap</a> contributors, © <a href="https://carto.com/">CARTO</a>'
})
});
</script>
</body>
</html>