@maptiler/leaflet-maptilersdk
Advanced tools
Vector tiles basemap plugin for Leaflet - multi-lingual basemaps using MapTiler SDK
Vector Tiles in Leaflet JS tutorial →
Add a layer to your Leaflet app that displays MapTiler SDK basemaplayer!
MapTiler SDK JS is an extension of MapLibre GL JS, fully backward compatible, tailored for MapTiler Cloud, and with plenty of extra features, including TypeScript support!
The UDM leaflet-maptilersdk bundle is not packaged with Leaflet nor with MapTiler SDK, so those will have to be imported as <script> separately in the <head> HTML element as follows:
<!-- Leaflet -->
<link rel="stylesheet" href="https://unpkg.com/leaflet@1.9.3/dist/leaflet.css" />
<script src="https://unpkg.com/leaflet@1.9.3/dist/leaflet.js"></script>
<!-- MapTiler SDK -->
<script src="https://cdn.maptiler.com/maptiler-sdk-js/v3.0.0/maptiler-sdk.umd.min.js"></script>
<link href="https://cdn.maptiler.com/maptiler-sdk-js/v3.0.0/maptiler-sdk.css" rel="stylesheet" />
<!-- Leaflet plugin for MapTiler SDK Layers -->
<script src="https://cdn.maptiler.com/leaflet-maptilersdk/v3.0.0/leaflet-maptilersdk.js"></script>
Then, in the HTML <body>, declare the container that will host the map:
<div id="map"></div>
Finally, add a <script> to initialize the Leaflet Map that contains a MapTiler SDK Layer:
// Center the map on Manhattan, zoom level 13
const map = L.map('map').setView([40.7468, -73.98775], 13);
// Add a marker with a popup
L.marker([40.7468, -73.98775])
.bindPopup("Hello <b>Leaflet with MapTiler SDK</b>!<br>Whoa, it works!")
.addTo(map)
.openPopup();
// Create a MapTiler Layer inside Leaflet
const mtLayer = L.maptiler.maptilerLayer({
// Get your free API key at https://cloud.maptiler.com
apiKey: "YOUR_MAPTILER_API_KEY",
}).addTo(map);
The notation L.maptiler.maptilerLayer() is the typical Leaflet way to expose a factory function that creates a layer. Even though our plugin exposes other ways to do exactly the same thing, this notation may suit your programming style better.
The following are all yielding the same result:
const mtLayer = L.maptiler.maptilerLayer( options ) (mind the lowercase m, it's a factory function)const mtLayer = new L.maptiler.MaptilerLayer( options ) (mind the uppercase M, it's a class)const mtLayer = leafletmaptilersdk.maptilerLayer( options ) (mind the lowercase m, it's a factory function)const mtLayer = new leafletmaptilersdk.MaptilerLayer( options ) (mind the upper case M, it's a class)importWe use the Vite vanilla JS app as a starting point for the following examples.
The typical Leaflet plugin usually adds new elements directly in the global object L. ⚠️ Since the version 3.0.0 (and the addition of TypeScript support), this plugin no longer adds anything to the global L namespace in ES mode. Instead, the library opts for a cleaner and more modern design:
// import Leaflet and its style
import L from "leaflet";
import "leaflet/dist/leaflet.css";
// Import some elements from the Leaflet-MapTiler Plugin
import { Language, MaptilerLayer, MapStyle } from "@maptiler/leaflet-maptilersdk";
// Import your custom style,
// depending on your configuration, you may have to change how this is done
import './style.css';
Then, in the Vite vanilla app, we would have to do exactly like in regular vanilla JS:
// Center the map on Manhattan, zoom level 13
const map = L.map("map").setView([40.7468, -73.98775], 13);
// Center the map on Manhattan, zoom level 13
L.marker([40.7468, -73.98775])
.bindPopup("Hello <b>Leaflet with MapTiler SDK</b>")
.addTo(map)
.openPopup();
// Create a MapTiler Layer inside Leaflet
const mtLayer = new MaptilerLayer({
// Get your free API key at https://cloud.maptiler.com
apiKey: "YOUR_MAPTILER_API_KEY",
}).addTo(map);
// Alternatively, we can call the factory function (mind the lowercase `m`)
const mtLayer = maptilerLayer({
// Get your free API key at https://cloud.maptiler.com
apiKey: "YOUR_MAPTILER_API_KEY",
}).addTo(map);
Some frontend frameworks are very opinionated regarding Server-Side-rendering and will attempt to perform it; that's the case of Next.js. But Leaflet does not play well with it because there are some direct calls to the global window object, and this would crash on a server. The fix consists of importing Leaflet dynamically, and then @maptiler/leaflet-maptilersdk can also be imported.
The React lifecycle .componentDidMount() of a class component of the useEffect [] functional equivalent is only called on the frontend when the component is ready. It's a good moment to dynamically import Leaflet because the window globale object is accessible:
useEffect(() => {
// A self-callable async function because importing packages dynamically is an async thing to do
(async () => {
// dynamic import of Leaflet
const L = await import('leaflet');
// dynamic import of the library
const leafletmaptilersdk = await import('@maptiler/leaflet-maptilersdk');
// Creating the Leaflet map
const map = L.map(containerRef.current).setView([51.505, -0.09], 10);
// Creating the MapTiler Layer
const mtLayer = new leafletmaptilersdk.MaptilerLayer({
apiKey: "YOUR_MAPTILER_API_KEY",
}).addTo(map);
})();
}, []);
The option object passed to the factory function maptilerLayer or to the constructor MaptilerLayer is then passed to the constructor of the Maptiler SDK Map class. Read more about the possible options on our SDK documentation.
Here are the major options:
geolocate: [boolean] if true, will locate the user and center the map accordingly. Note that Leaflet still requires the use of .setView(), but this will be ignored. Default: false.language: [string] by default uses the language from the system settings and falls back to local names. Yet the language can be enforced with one from the list below. Depending on how you are importing, you could use L.MaptilerLanguage.ENGLISH, MaptilerLanguage.ENGLISH or leafletmaptilersdk.MaptilerLanguage.ENGLISH. style: [string | style definition] MapTiler has created many professional-looking styles that suit the majority of use cases. Directly from the constructor, you can specify the short style ID. Alternatively, a style URL or a complete style definition object can also be used. Default: L.MaptilerStyle.STREETS. Depending on how you are importing, you could use L.MaptilerStyle.STREETS, MaptilerStyle.STREETS or leafletmaptilersdk.MaptilerStyle.STREETS.
You can also easily create your custom map style
apiKey: [string] your MapTiler Cloud API key. Default: empty stringThe MaptilerLayer constructor and/or maptilerLayer factory function returns a Leaflet Maptiler layer that we will call mtLayer.
.addTo(map)The same behavior as .addTo on any Leaflet layer: this adds the layer to a given
map or group.
.getMaptilerMap(): maptilerLayer.MapReturns mapltilersdk.Map object.
.setStyle(s)Update the style with a style ID, style URL, or style definition. The easiest is to use a built-in style ID such as listed above with the form L.MaptilerStyle.STREETS.
.setLanguage(l)Update the map language. For this, the best is to use a built-in language shorthand with the form L.MaptilerLanguage.JAPANESE, such as listed above.
We have added an even easier way to use the MapTiler SDK vector layer helpers, directed under the instance of the custom Leaflet layer. You can now call .addPolyline, .addPolygon, .addPoint, and .addHeatmap using a path to a file or the ID of a dataset hosted on MapTiler Cloud.
Let's see an example:
// Init the map
const map = L.map('map').setView([46.3796, 6.1518], 13);
// Creating and mounting the MapTiler SDK Layer
const mtLayer = new L.MaptilerLayer({
apiKey: "YOUR_MAPTILER_API_KEY",
style: L.MaptilerStyle.BACKDROP.DARK,
}).addTo(map);
// The custom event "ready" is triggered by the MaptilerLayer when the internal
// MapTiler Map instance is fully loaded and can be added more layers
mtLayer.on("ready", () => {
// Leverage the MapTiler SDK layer helpers to add polyline / point / polygon / heatmap layers easily
mtLayer.addPolyline({
// A Maptiler Cloud dataset ID, or URL to GeoJSON/GPX/KML
data:"74003ba7-215a-4b7e-8e26-5bbe3aa70b05",
lineColor: "#008888", // optional
outline: true, // optional
outlineWidth: 2, // optional
});
})
Here is the result, a bike ride in France and Switzerland, displayed on the dark Backdrop MapTiler style:
"ready"The "ready" event is triggered when the internal MapTiler SDK Map instance is fully loaded and can accept some more layers to be added. This corresponds to the MapTiler SDk and MapLibre load event.
Please use the issue tracker to report any bugs or file feature requests.
ISC © MapTiler
4.0.2
FAQs
Vector tiles basemap plugin for Leaflet - multi-lingual basemaps using MapTiler SDK
The npm package @maptiler/leaflet-maptilersdk receives a total of 2,002 weekly downloads. As such, @maptiler/leaflet-maptilersdk popularity was classified as popular.
We found that @maptiler/leaflet-maptilersdk demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.