npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@maptiler/leaflet-maptilersdk

v2.0.0

Published

Vector tiles basemap plugin for Leaflet - multi-lingual basemaps using MapTiler SDK

Downloads

9,708

Readme

This is a binding from MapTiler SDK JS/TS to the familiar Leaflet API.

MapTiler SDK JS is an extension of MapLibre GL JS, fully backward compatible, tailored for MapTiler Cloud and with plenty of extra features!

Usage

From ES module using import

For the following examples, we are using the Vite vanilla JS app as a starting point.

The typical Leaflet plugin usualy adds new elements directly in the global object L and even though this API design is now a bit dated and somewhat frown uppon, we did not want to disrupt the dev experiece for those used to this. For this reason, you will need to import the plugin but not a specific object from it, as MaptilerLayer is internally added to L:

// import Leaflet and its style
import L from "leaflet";
import "leaflet/dist/leaflet.css";

// Import the Leaflet MapTiler Plugin
import "@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 exactely 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 L.MaptilerLayer({
  // Get your free API key at https://cloud.maptiler.com
  apiKey: "YOUR_MAPTILER_API_KEY",
}).addTo(map);

If you would rather stick to more modern API design and do not feel like using the L object, we got you covered:

import { MaptilerLayer } from "@maptiler/leaflet-maptilersdk";

// ...

const mtLayer = new MaptilerLayer( options );

From ES module, the async way

Some frontend frameworks always are very opinionated regarding Server-Side-rendering and will attemp 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 in importing Leaflet dynamically, and then @maptiler/leaflet-maptilersdk can also be imported.

The React lifecycle method .componentDidMount() of a class component is only called on the frontend so this is why we have decided to dynamically import from there, but feel free to adapt your code if you are using a function component or a non-React app:

componentDidMount() {
  // assuming this was init with React.createRef()
  const container = this.mapContainer.current;
  
  // 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(container).setView([51.505, -0.09], 10);

    // Creating the MapTiler Layer
    const mtLayer = new leafletmaptilersdk.MaptilerLayer({
      apiKey: "YOUR_API_KEY",
    }).addTo(map);

  })()
}

From CDN with the UMD bundle

The UDM leaflet-maptilersdk bundle is not package with Leaflet nor with MapTiler SDK, so those will have to be imported as <script> separately as follow in the <head> HTML element:

<!-- Leaflet -->
<link rel="stylesheet" href="https://unpkg.com/[email protected]/dist/leaflet.css" />
<script src="https://unpkg.com/[email protected]/dist/leaflet.js"></script>

<!-- MapTiler SDK -->
<script src="https://cdn.maptiler.com/maptiler-sdk-js/latest/maptiler-sdk.umd.js"></script>
<link href="https://cdn.maptiler.com/maptiler-sdk-js/latest/maptiler-sdk.css" rel="stylesheet" />

<!-- Leaflet plugin for MapTiler SDK Layers -->
<script src="../build/leaflet-maptilersdk.umd.js"></script>

Then, in the HTML <body>, decalre 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.maptilerLayer({
  // Get your free API key at https://cloud.maptiler.com
  apiKey: "YOUR_MAPTILER_API_KEY",
}).addTo(map);

The notation L.maptilerLayer is the typical Leaflet way to expose a factory function that creates a layer. Though, our plugin exposes other ways to do exactely the same thing but that may suit your programming style better.
The following are all yielding the same result:

  • const mtLayer = L.maptilerLayer( options )
  • const mtLayer = new L.MaptilerLayer( options ) (mind the upper case M)
  • const mtLayer = leafletmaptilersdk.maptilerLayer( options )
  • const mtLayer = new leafletmaptilersdk.MaptilerLayer( options ) (mind the upper case M)

API and options

Constructor and Factory function

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 is using 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 may suit your particular need. 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.

    • L.MaptilerStyle.STREETS, reference style for navigation and city exploration
      • L.MaptilerStyle.STREETS.DARK (variant)
      • L.MaptilerStyle.STREETS.LIGHT (variant)
      • L.MaptilerStyle.STREETS.PASTEL (variant)
    • L.MaptilerStyle.SATELLITE reference style satellite and airborne imagery (no variants)
    • L.MaptilerStyle.HYBRID reference style satellite and airborne imagery with labels (no variants)
    • L.MaptilerStyle.OUTDOOR reference style for adventure
      • L.MaptilerStyle.OUTDOOR.DARK (variant)
    • L.MaptilerStyle.WINTER reference style for winter adventure
      • L.MaptilerStyle.WINTER.DARK (variant)
    • L.MaptilerStyle.DATAVIZ, the perfect style for data visualization, with very little noise
      • L.MaptilerStyle.DATAVIZ.DARK (variant)
      • L.MaptilerStyle.DATAVIZ.LIGHT (variant)
    • L.MaptilerStyle.BASIC reference style for minimalist design and general purpose
      • L.MaptilerStyle.BASIC.DARK (variant)
      • L.MaptilerStyle.BASIC.LIGHT (variant)
    • L.MaptilerStyle.BRIGHT reference style for high contrast navigation
      • L.MaptilerStyle.BRIGHT.DARK (variant)
      • L.MaptilerStyle.BRIGHT.LIGHT (variant)
      • L.MaptilerStyle.BRIGHT.PASTEL (variant)
    • L.MaptilerStyle.TOPO reference style for topographic study
      • L.MaptilerStyle.TOPO.SHINY (variant)
      • L.MaptilerStyle.TOPO.PASTEL (variant)
      • L.MaptilerStyle.TOPO.TOPOGRAPHIQUE (variant)
    • L.MaptilerStyle.VOYAGER reference style for stylish yet minimalist maps
      • L.MaptilerStyle.VOYAGER.DARK (variant)
      • L.MaptilerStyle.VOYAGER.LIGHT (variant)
      • L.MaptilerStyle.VOYAGER.VINTAGE (variant)
    • L.MaptilerStyle.TONER reference style for very high contrast stylish maps
      • L.MaptilerStyle.TONER.BACKGROUND (variant)
      • L.MaptilerStyle.TONER.LITE (variant)
      • L.MaptilerStyle.TONER.LINES (variant)
    • L.MaptilerStyle.OPENSTREETMAP reference style for the classic OSM look
    • L.MaptilerStyle.OCEAN reference style with seabed isoline, hilshading and trenches info

    You can also create your custom styles on cloud.maptiler.com/maps

  • apiKey: [string] your MapTiler Cloud API key. Default: empty string

The MaptilerLayer constructor and/or maptilerLayer factory function returns a Leaflet Maptiler layer, that we will call mtLayer.

Method .addTo(map)

Same behavior as .addTo on any Leaflet layer: this adds the layer to a given map or group.

Method .getMaptilerMap(): maptilerLayer.Map

Returns mapltilersdk.Map object.

Method .getContainer(): HTMLDivElement

Returns layer's DOM container div.

Method .getCanvas(): HTMLCanvasElement

Returns maptilerLayer.Map canvas.

Method .getSize(): L.Point

Returns layer size in pixels including padding.

Method .getBounds(): L.LatLngBounds

Returns layer bounds including padding.

Method .getPaneName(): string

Returns the pane name set in options if it is a valid pane, defaults to tilePane.

Method .setStyle(s)

Update the style with a style ID, style URL or a style definition. The easiest is to use a built-in style ID such as listed above with the form L.MaptilerStyle.STREETS.

Method .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.

Methods to add vector layers

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_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 easily add polyline / point / polygon / heatmap layers
  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 Switzerlanld, displayed on the dark Backdrop MapTiler style:

Event "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.

Bug Reports & Feature Requests

Please use the issue tracker to report any bugs or file feature requests.

Licence

ISC © MapTiler