@inelo/leaflet-control-geocoder

A few words on diversity in tech

I need to take some of your time. I can't believe we let shit like the Kathy Sierra incident or what happened to Brianna Wu happen over and over again. I can't believe we, the open source community, let sexist, misogynous shit happen over and over again.

I strongly believe that it is my — and your — duty to make the open source community, as well as the tech community at large, a community where everyone feel welcome and is accepted. At the very minimum, that means making sure the community and its forums both are safe, and are perceived as safe. It means being friendly and inclusive, even when you disagree with people. It means not shrugging off discussions about sexism and inclusiveness with handwaving about censorship and free speech. For a more elaborate document on what that means, the NPM Code of Conduct is a good start, Geek Feminism's resources for allies contains much more.

While I can't force anyone to do anything, if you happen to disagree with this, I ask of you not to use any of the open source I have published. Nor am I interested in contributions from people who can't accept or act respectfully towards other humans regardless of gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics. If you think feminism, anti-racism or the LGBT movement is somehow wrong, disturbing or irrelevant, I ask you to go elsewhere to find software.

Leaflet Control Geocoder

A simple geocoder for Leaflet that by default uses OSM/Nominatim.

The plugin supports many different data providers:

• LatLng to parse basic latitude/longitude strings
• OSM/Nominatim
• Bing Locations API
• Google Geocoding API
• Mapbox Geocoding
• MapQuest Geocoding API
• What3Words
• Photon
• Pelias, geocode.earth (formerly Mapzen Search), Openrouteservice
• HERE Geocoder API (legacy)
• Neutrino API
• Plus codes (formerly OpenLocationCode) (requires open-location-code)
• ArcGIS

The plugin can easily be extended to support other providers. Current extensions:

• DAWA Geocoder - support for Danish Address Web API by Niels Kjøller Hansen

Demos

• Leaflet Control Geocoder Demo hosted on liedman.net
• See demo/
• See demo-rollup/ using the rollup.js bundler
• See demo-webpack/ using the webpack bundler

Usage

Download latest release, or obtain the latest release via unpkg.com:

<link rel="stylesheet" href="https://unpkg.com/leaflet-control-geocoder/dist/Control.Geocoder.css" />
<script src="https://unpkg.com/leaflet-control-geocoder/dist/Control.Geocoder.js"></script>

Add the control to a map instance:

var map = L.map('map').setView([0, 0], 2);
L.tileLayer('https://{s}.tile.osm.org/{z}/{x}/{y}.png', {
  attribution: '&copy; <a href="https://osm.org/copyright">OpenStreetMap</a> contributors'
}).addTo(map);
L.Control.geocoder().addTo(map);

Customizing

By default, when a geocoding result is found, the control will center the map on it and place a marker at its location. This can be customized by listening to the control's markgeocode event. To remove the control's default handler for marking a result, set the option defaultMarkGeocode to false.

For example:

var geocoder = L.Control.geocoder({
  defaultMarkGeocode: false
})
  .on('markgeocode', function(e) {
    var bbox = e.geocode.bbox;
    var poly = L.polygon([
      bbox.getSouthEast(),
      bbox.getNorthEast(),
      bbox.getNorthWest(),
      bbox.getSouthWest()
    ]).addTo(map);
    map.fitBounds(poly.getBounds());
  })
  .addTo(map);

This will add a polygon representing the result's boundingbox when a result is selected.

API

• latest → https://www.liedman.net/leaflet-control-geocoder/docs/
• version 1.13.0 → https://github.com/perliedman/leaflet-control-geocoder/tree/1.13.0#api