QGIS plugin to export your project to an OpenLayers 3 or Leaflet webmap. No server-side software required.

• In QGIS, select Plugins > Manage and Install Plugins...

or:

• Download and unzip to your QGIS plugins directory

Prepare your map as far as possible in QGIS, as you want it to appear in your webmap. Specific tasks you can carry out to improve your webmap include:

• Set your project title, and background and highlight colours in Project > Project Properties...
• Give your layers human-friendly names in the Layers Panel
• Give your layer columns human friendly names via Layer > Properties > Fields > Alias

Run qgis2web from the Web menu, or via its icon. If required, choose a basemap from the list below the preview pane, and click "Update preview". CTRL/CMD-click for multiple basemaps.

The top-left pane lets you set options for each layer in your map. The bottom-left pane sets overall options. All options are written to your QGIS project, so save your proejct if you want to keep these settings.

QGIS, OpenLayers 3, and Leaflet are all different mapping technologies. This means that their respective functionality differs in many ways. qgis2web does its best to interpret a QGIS project and to export HTML, Javascript, and CSS to create a web map as close to the QGIS project as possible.

However, many elements of a QGIS project cannot be reproduced, and many are only possible in either OpenLayers 3 or Leaflet. qgis2web tries its best to produce a publish-ready map, but you can always manually edit the output code to achieve what qgis2web cannot.

• no rule-based rendering
• SVG point markers sometimes do not appear in the preview pane, but work when the map is exported
• in OL3 maps, only single rendered points cluster, not categorized or graduated
• rasters are exported unstyled
• line style (dashed/dotted) does not appear in OL3 preview, but works in export
• Leaflet cannot label lines and polygons, only points

Info popup content

Select which fields will appear in popups when features are clicked

Visible

Select whether the layer will be visible on map load. This only determines visibility - the layer will be loaded regardless of this setting

Encode to JSON

If unchecked, WFS layers will remain remote WFS layers in the webmap. If checked, the layer will be written to a local GeoJSON file

Cluster

Cluster point features

Delete unused fields

If not all fields are selected in "Info popup content", remove the undisplayed fields from the GeoJSON - helps to reduce file size

Export folder

The folder where the webmap will be saved

Mapping library location

Select whether to use a local copy of OL3/Leaflet, or whether to call the library from its CDN

Minify GeoJSON files

Remove unnecessary whitespace from exported GeoJSON to reduce file size

Precision

Simplify geometry to reduce file size

Extent

Either match the current QGIS view or show all contents of all layers (only local GeoJSON and rasters, not WFS/WMS)

Max zoom level

How far the webmap will zoom in

Min zoom level

How far the webmap will zoom out

Restrict to extent

Prevent panning or zooming beyond the selected extent

Add address search

Add field to allow searching for locations (geocode)

Add layers list

Include list of layers (with legend icons, where possible)

Add measure tool

Include interactive measuring widget

Add scale bar

Include dynamic scale bar

Geolocate user

Show user's location on map

Highlight features

Highlight features on mouseover

Match project CRS

Create webmap in same projection as QGIS project, otherwise the webmap is projected in EPSG:3857

Show popups on hover

Show popups when mouse hovers over features

Template

Select HTML template for webmap - add your own templates to the /templates directory

Please report any problems you have with qgis2web. Without this feedback, I am often completely unaware that a problem exists. To ensure no time or effort is wasted in bug reporting, please follow these steps:

1. Check the issues on Github to see whether the bug has already been reported, and if so, read through all the comments on the issue, and add any additional informaton from your experience of the bug
2. Make sure you can reproduce the bug reliably
3. Reduce the complexity of your bug conditions as far as you can, especially by reducing the number of layers, ideally to one
4. Raise a Github issue, including:
   • the qgis2web version (or make it clear you are using Github master branch)
   • any Python error text/stack trace which occurs
   • browser JS console errors - press F12 in qgis2web to open the developer toolbar and find the console
   • screenshot of your settings
   • screenshot of the output
   • a link to the data you used, if possible

The stability of qgis2web relies on your bug reports, so please keep them coming.

qgis2web is fundamentally a merge of Victor Olaya's qgis-ol3 and Riccardo Klinger's qgis2leaf. It would not exist without their work. Thank you, gentlemen. Thanks are also very much due to Paolo Cavallini, who suggested and supported the merge.

• github.com/volaya
• github.com/riccardoklinger
• github.com/pcav