Leaflet (software)

A basic demo using Leaflet.

A typical use of Leaflet involves binding a Leaflet "map" element to an HTML element such as a div. Layers and markers are then added to the map element.

 // create a map in the "map" div, set the view to a given place and zoom
 var map = L.map('map').setView([51.505, -0.09], 13);
 
 // add an OpenStreetMap tile layer
 // Tile Usage Policy applies: https://operations.osmfoundation.org/policies/tiles/
 L.tileLayer('http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png', {
     attribution: '&amp;copy; <a href="http://openstreetmap.org/copyright">OpenStreetMap</a> contributors'
 }).addTo(map);

A unique feature of leaflet is displaying maps in non-spherical Mercator projections.[4] The Leaflet library itself is accessible through the variable L.

Leaflet supports Web Map Service (WMS) layers, GeoJSON layers, Vector layers and Tile layers natively. Many other types of layers are supported via plugins.

Like other web map libraries, the basic display model implemented by Leaflet is one basemap, plus zero or more translucent overlays, with zero or more vector objects displayed on top.

Leaflet is directly comparable with OpenLayers, as both are open source, client-side only JavaScript libraries. The library as a whole is much smaller, around 7,000 lines of code compared to OpenLayers' 230,000 (as of 2015).[12] It has a smaller code footprint than OpenLayers (around 123 KB[13] vs 423 KB[14]) due partly to its modular structure. The code base is newer, and takes advantage of recent features of JavaScript, plus HTML5 and CSS3. However, Leaflet lacks features OpenLayers supports, such as Web Feature Service (WFS)[15] and native support for projections other than Google Web Mercator (EPSG 3857).[16]

It is also comparable to the proprietary, closed source Google Maps API (debuting in 2005) and Bing Maps API, both of which incorporate a significant server-side component to provide services such as geocoding, routing, search and integration with features such as Google Earth. Google Maps API provides speed and simplicity, but is not flexible, and can only be used to access Google Maps services. The new DataLayer part of Google's API does allow external data sources to be displayed, however.[17]

Leaflet began life in 2010 as "Web Maps API", a JavaScript library for the CloudMade mapping provider, where Agafonkin worked at the time. In May 2011, CloudMade announced the first release of Leaflet, built from scratch but using parts of the old API code.[18]

• 0.1: May 17, 2011
• 0.2: June 18, 2011
• 0.3: Feb 14, 2012
• 0.4: Jul 30, 2012
• 0.5: Jan 17, 2013
  • This release introduced Retina support and many usability and user experience improvements.[19]
• 0.6: Jun 26, 2013
  • This release expanded the API's range of methods and events, improved usability, and added GeoJSON saving. It was completed in a 2-day code sprint supported by Mapbox.[20]
• 0.7: Nov 22, 2013
  • This release focused on bug fixing, announcing that refactoring and potential backward incompatibilities would come soon.[21]
• 1.0: Sep 27, 2016
  • This release contained over 400 changes compared to v0.7.7:[22]
    • Performance improvements in all aspects of the library and vector layers in particular.
    • Flyover animations (zooming and panning in a curve).
    • Fractional zoom level support.
    • Better tile loading algorithm with less flickering.
    • Custom pane management (including multiple vector layer panes and interleaving vectors and tile layers).
    • Better support for non-standard projections.
    • More accessibility features.
    • Improved documentation.
    • Stability improvements.
• 1.1: Jun 27, 2017
  • This release adds video overlays and makes a transition to ECMAScript 6 modules.
• 1.2: Oct 25, 2017
• 1.3: Jan 15, 2018
• 1.3.2: Jul 17, 2018
• 1.3.3: Jul 18, 2018
• 1.3.4: Aug 21, 2018
• 1.4.0: Dec 30, 2018
• 1.5.0 and 1.5.1 : May 8, 2019
• 1.6.0: Nov 17, 2019
• 1.7.1 : September 4, 2020

• openstreetmap:leaflet
• Leaflet Official Site
• Leaflet Tutorials