@asymmetrik/ngx-leaflet
Advanced tools
IMPORTANT NOTE: We have renamed this project from angular2-leaflet to ngx-leaflet.
Leaflet packages for Angular 2+. Provides flexible and extensible components for integrating Leaflet v0.7.x and v1.x into Angular 2+ projects. Now supports Angular v4, Ahead-of-Time compilation (AOT), and use in Angular-CLI based projects.
Install the package and its peer dependencies via npm (or yarn):
npm install leaflet
npm install @asymmetrik/ngx-leaflet
If you intend to use this library in a typescript project (utilizing the typings), you will need to also install the leaflet typings via npm:
npm install @types/leaflet
If you want to run the demo, clone the repository, perform an npm install, gulp dev and then go to http://localhost:9000/src/demo/index.html
To use this library, there are a handful of setup steps to go through that vary based on your app environment (e.g., Webpack, ngCli, SystemJS, etc.). Generally, the steps are:
For leaflet to work, you need to have the leaflet stylesheets loaded into your application.
If you've installed via npm, you will need to load ./node_modules/leaflet/dist/leaflet.css.
How you include the stylesheet will depend on your specific setup. Here are a few examples:
If you are just building a webpage and not using a bundler for your css, you'll want to directly import the css file in your HTML page.
<head>
...
<link rel="stylesheet" type="text/css" href="./node_modules/leaflet/dist/leaflet.css">
...
</head>
If you are using Webpack, you will need to import the css file and have a style-loader configured. You can use the demo included in this application as a reference.
Generally, in vendor.ts:
import 'leaflet/dist/leaflet.css';
And then in your webpack config file:
{
...
"module" : {
loaders: [
...
{ test: /\.css$/, loaders: [ 'style-loader', 'css-loader' ] },
...
]
},
...
}
If you are using Angular CLI, you will need to add the Leaflet CSS file to the styles array contained in .angular-cli.json
{
...
"apps": [
{
...
"styles": [
"styles.css",
"../node_modules/leaflet/dist/leaflet.css"
],
...
}
]
...
}
This project is exported using UMD and it includes typings. So, you shouldn't have to do anything special to use it if you're building your project in Typescript.
Before you can use the module in your Angular 2+ app, you'll need to import it in your application.
For example, in your app.module.ts, add:
import { LeafletModule } from '@asymmetrik/ngx-leaflet';
...
imports: [
...
LeafletModule.forRoot()
]
...
You brave soul. The code is exported using UMD (bundles are in the ./dist dir) so you should be able to import is using whatever module system/builder you're using, even if you aren't using Typescript.
Once the dependencies are installed and you have imported the LeafletModule, you're ready to add a map to your page.
To get a basic map to work, you have to:
leaflet attribute directive (see the example below) to an existing DOM element.leafletOptions or by binding to leafletZoom, leafletCenter, and leafletLayers.Template:
<div style="height: 300px;"
leaflet
[leafletOptions]="options">
</div>
Example leafletOptions object:
options = {
layers: [
tileLayer('http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png', { maxZoom: 18, attribution: '...' })
],
zoom: 5,
center: latLng(46.879966, -121.726909)
};
Changes to leafletOptions are ignored after they are initially set. This is because these options are passed into the map constructor, so they couldn't be updated easily regardless. So, make sure the object exists before the map is created. You'll want to create the object in ngOnInit or hide the map DOM element with ngIf until you can create the options object.
The leafletLayersControl input bindings give you the ability to add the layers control to the map.
The layers control lets the user toggle layers and overlays on and off.
Template:
<div style="height: 300px;"
leaflet
[leafletOptions]="options"
[leafletLayersControl]="layersControl">
</div>
Example layersControl object:
layersControl = {
baseLayers: {
'Open Street Map': tileLayer('http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png', { maxZoom: 18, attribution: '...' }),
'Open Cycle Map': tileLayer('http://{s}.tile.opencyclemap.org/{z}/{x}/{y}.png', { maxZoom: 18, attribution: '...' })
},
overlays: {
'Big Circle': circle([ 46.95, -122 ], { radius: 5000 }),
'Big Square': polygon([[ 46.8, -121.55 ], [ 46.9, -121.55 ], [ 46.9, -121.7 ], [ 46.8, -121.7 ]])
}
}
You can add any kind of Leaflet layer you want to the overlays map.
This includes markers, shapes, geojson, custom layers from other libraries, etc.
You can add layers (baselayers, markers, or custom layers) to the map without showing them in the layer control using the leafletLayers directive.
Template:
<div style="height: 300px;"
leaflet
[leafletOptions]="options"
[leafletLayers]="layers">
</div>
Layers array:
layers = [
circle([ 46.95, -122 ], { radius: 5000 }),
polygon([[ 46.8, -121.85 ], [ 46.92, -121.92 ], [ 46.87, -121.8 ]]),
marker([ 46.879966, -121.726909 ])
];
Layer inputs (arrays and maps) are mutable Previous versions of this plugin treated layers arrays and layer control objects as immutable data structures. We've changed that behavior. Now, mutable changes to the
leafletLayers,leafletBaseLayers, andleafletLayersControlinputs are detected.
The plugin is now using internal ngx iterable and key/value differs to detect and track changes to mutable data structures. This approach requires a deep compare of the contents of the data structure (which can be slow when the contents are really big). For immutable data structures, all that is needed is a top-level instance equality check (which is way faster). This change is backwards compatible and was motivated by feedback and confusion. While there is a performance impact for some use cases, this approach is more intuitive.
There are at least two good approaches to improving performance when there are a lot of layers bound to the map. First, you can use the OnPush change detection strategy. There's an example of this in the demo. Second, you can wrap a large number of layers into a Leaflet layer group, which will reduce the number of layers the plugin actually has to track during diffs.
This section includes more detailed documentation of the functionality of the directives included in this library.
There are several input bindings available for configuring the map.
<div leaflet style="height: 300px;"
[leafletOptions]="options"
[leafletPanOptions]="panOptions"
[leafletZoomOptions]="zoomOptions"
[leafletZoomPanOptions]="zoomPanOptions"
[leafletFitBoundsOptions]="fitBoundsOptions">
</div>
Input binding for the initial leaflet map options (see Leaflet's docs). These options can only be set initially because they are used to create the map. Later changes are ignored.
Input binding for pan options (see Leaflet's docs). These options are stored and used whenever pan operations are invoked.
Input binding for zoom options (see Leaflet's docs). These options are stored and used whenever zoom operations are invoked.
Input binding for zoom/pan options (see Leaflet's docs). These options are stored and used whenever zoom/pan operations are invoked.
Input binding for FitBounds options (see Leaflet's docs). These options are stored and used whenever FitBounds operations are invoked.
<div leaflet style="height: 300px;"
[leafletOptions]="options"
[leafletZoom]="zoom"
[leafletCenter]="center"
[leafletFitBounds]="fitBounds">
</div>
Input bind a zoom level to the map.
zoom: number
On changes, the component applies the new zoom level to the map. There is no output binding or events emitted for map zoom level changes made using the map controls.
Input bind a center position to the map.
center: LatLng
On changes, the component re-centers the map on the center point. There is no output binding or events emitted for map pan changes made using map controls.
Zoom/Center operations cancel each other. If both changes are picked up at the same time, they will be applied as a map.setView() operation so both are processed.
Input bind a fitBounds operation to the map.
fitBounds: LatLngBounds
On changes, the component calls map.fitBounds using the bound parameter.
There is a convenience input binding for setting the baselayers on the map called leafletBaseLayers.
You can also provide leafletLayersControlOptions if you want to show the control on the map that allows you to switch between baselayers.
If you plan to show more than just baselayers, you should use the more advanced layers controls described in Advanced Layer Management below.
For an example of the basic map setup, you should check out the Simple Base Layers demo.
<div leaflet style="height: 300px;"
[leafletOptions]="options"
[leafletBaseLayers]="baseLayers"
[leafletLayersControlOptions]="layersControlOptions">
</div>
Input bind an Control.LayersObject to be synced to the map.
baseLayers: {
'layer1': Layer,
'layer2': Layer
}
On changes, the component syncs the baseLayers on the map with the layers in this object.
Syncing is performed by tracking the current baselayer and on changes, searching the map to see if any of the current baselayers is added to the map.
If it finds a baselayer that is still added to the map, it will assume that is still the baselayer and leave it.
If none of the baselayers can be found on the map, it will add the first layer it finds in the Control.LayersObject and use that as the new baselayer.
Layers are compared using instance equality.
If you use this directive, you can still manually use the leafletLayers directive, but you will not be able to use the leafletLayersControl directive.
This directive internally uses the layers control, so if you add both, they'll interfere with each other.
Because it uses control.layers under the hood, you can still provide options for the layers control.
Input binding for Control.Layers options (see Leaflet's docs). These options are passed into the layers control constructor on creation.
The leafletLayers and leafletLayersControl input bindings give you direct access to manipulate layers and the layers control.
When the array bound to leafletLayers is changed, the directive will synchronize the layers on the map to the layers in the array.
This includes tile layers and any added shapes.
The leafletLayersControl input binding allows you to provide a set of base layers and overlay layers that can be managed within leaflet using the layers control.
When the user manipulates the control via Leaflet, Leaflet will automatically manage the layers, but the input bound layer array isn't going to get updated to reflect those changes.
So, basically, you use leafletLayers to assert what should be added to/removed from the map.
Use leafletLayersContro to tell Leaflet what layers the user can optionally turn on and off.
For an example of using the layers controls, you should check out the Layers and Layer Controls demo.
<div leaflet style="height: 300px;"
[leafletOptions]="options"
[leafletLayers]="layers"
[leafletLayersControl]="layersControl"
[leafletLayersControlOptions]="layersControlOptions">
</div>
Input bind an array of all layers to be synced (and made visible) in the map.
layers: Layer[]
On changes, the component syncs the layers on the map with the layers in this array. Syncing is performed by selectively adding or removing layers. Layers are compared using instance equality. As a result of how the map is synced, the order of layers is not guaranteed to be consistent as changes are made.
Input bind a Control.Layers specification. The object contains properties for each of the two constructor arguments for the Control.Layers constructor.
layersControl: {
baseLayers: {
'layerName': Layer
},
overlays: {
'overlayName': Layer
}
}
Input binding for Control.Layers options (see Leaflet's docs). These options are passed into the constructor on creation.
The leafletLayer input bindings gives you the ability to add a single layer to the map.
While this may seem limiting, you can nest elements inside the map element, each with a leafletLayer input.
The result of this is that each layer will be added to the map.
If you add a structural directive - *ngFor or *ngIf - you can get some added flexibiltiy when controlling layers.
<div leaflet style="height: 300px;"
[leafletOptions]="options">
<div *ngFor="let l of layers" [leafletLayer]="l"></div>
</div>
In this example, each layer in the layers array will create a new child div element.
Each element will have a leafletLayer input binding, which will result in the layer being added to the map.
For more details, you should check out the Layers and ngFor demo.
Occasionally, you may need to directly access the Leaflet map instance.
For example, to call invalidateSize() when the map div changes size or is shown/hidden.
There are a couple of different ways to achieve this depending on what you're trying to do.
The easiest and most flexible way is to use the output binding leafletMapReady.
This output is invoked after the map is created, the argument of the event being the Map instance.
The second is to get a reference to the leaflet directive itself - and there are a couple of ways to do this.
With a reference to the directive, you can invoke the getMap() function to get a reference to the Map instance.
This output is emitted when once when the map is initially created inside of the Leaflet directive. The event will only fire when the map exists and is ready for manipulation.
<div leaflet
[leafletOptions]="options"
(leafletMapReady)="onMapReady($event)">
</div>
onMapReady(map: Map) {
// Do stuff with map
}
This method of getting the map makes the most sense if you are using the Leaflet directive inside your own component and just need to add some limited functionality or register some event handlers.
In Angular 2, directives are injectable the same way that Services are.
This means that you can create your own component or directive and inject the LeafletDirective into it.
This will only work if your custom component/directive exists on the same DOM element and is ordered after the injected LeafletDirective.
<div leaflet myCustomDirective>
</div>
@Directive({
selector: '[myCustomDirective]'
})
export class MyCustomDirective {
leafletDirective: LeafletDirective;
constructor(leafletDirective: LeafletDirective) {
this.leafletDirective = leafletDirective;
}
someFunction() {
if (null != this.leafletDirective.getMap()) {
// Do stuff with the map
}
}
}
The benefit of this approach is it's a bit cleaner if you're interested in adding some reusable capability to the existing leaflet map directive.
This is how the @asymmetrik/angualr2-leaflet-draw and @asymmetrik/angualr2-leaflet-d3 packages work, so you can use them as references.
If you use this component in an Angular 2 project and your project uses a bundler like Webpack, you might run into issues using Markers on maps. The issue is related to how Leaflet manipulates the image URLs used to render markers when you are using the default marker images. The url manipulation is done at runtime and it alters the URLs in a way that breaks their format (this happens regardless of if you're using a file-loader or a url-loader). The demo contained in this project demonstrates how to get around this problem (at least in a Webpack environment). But, here is a rough overview of the steps taken to get them working.
Import the marker images in your vendor file to get Webpack to process the images in the asset pipeline
import 'leaflet/dist/images/marker-shadow.png';
import 'leaflet/dist/images/marker-icon.png';
Either host the images statically or use the file-loader Webpack plugin to generate the images.
Determine the correct URL for the marker and marker-shadow images. If you're using a file hasher, you should be able to check Webpack's output for the generated images. If you are serving them directly without chunk hashing just figure out how to resolve the images on your server.
Configure Leaflet to use the correct URLs as customer marker images
let layer = marker([ 46.879966, -121.726909 ], {
icon: icon({
iconSize: [ 25, 41 ],
iconAnchor: [ 13, 0 ],
iconUrl: '2273e3d8ad9264b7daa5bdbf8e6b47f8.png',
shadowUrl: '44a526eed258222515aa21eaffd14a96.png'
})
});
If you build your project using the Angular CLI, as of angular-cli release 1.0.0-rc.1 you can make the default leaflet marker assets available by doing the following:
Edit .angular-cli (formerly angular-cli.json)
Configure the CLI to include leaflet assets as below. Detailed instructions can be found in the asset-configuration documentation.
{
"project": {
...
},
"apps": [
{
...
"assets": [
"assets",
"favicon.ico",
{
"glob": "**/*",
"input": "../node_modules/leaflet/dist/images",
"output": "./assets/"
}
]
}
]
}
When using markers in your code, you can now use references like : icon( { iconUrl: 'assets/marker-icon.png', shadowUrl: 'assets/marker-shadow.png' } )
Added the [leafletLayer] directive for adding/removing individual layers.
Renamed the package to ngx-leaflet
PRs accepted. If you are part of Asymmetrik, please make contributions on feature branches off of the develop branch. If you are outside of Asymmetrik, please fork our repo to make contributions.
See LICENSE in repository for details.
Leaflet Is an awesome mapping package.
2.5.0
Added the [leafletLayer] directive for adding/removing individual layers.
FAQs
Angular.io components for Leaflet
The npm package @asymmetrik/ngx-leaflet receives a total of 47,095 weekly downloads. As such, @asymmetrik/ngx-leaflet popularity was classified as popular.
We found that @asymmetrik/ngx-leaflet demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 7 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
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.