Welcome to the new QGIS Web Application
This application is the official QGIS plugins web portal.
You are strongly encouraged to use this application and report any issue on the QGIS Web Applications Bug Tracking System.
You can browse and download the plugins of this repository directly from QGIS using the plugins manager, you can also download the plugins directly from this website.
If you want to share your own plugins on this repository, you'll need to create an account on OSGeo, you can create an account and get a new OSGeo ID at OSGEO web portal.
Resources for plugin users
- If you've found a bug in one of the plugins, learn how to submit a bug report:
Resources for plugin authors
- The pyQGIS cookbook is an ongoing effort to collect tips and tricks about QGIS python programming.
- The QGIS API is the ultimate reference for plugins creators
- Please consider adding your code as a subplugin of Processing, rather than as a separate plugin: you save coding, and the users have more consistent and powerful tools, that can be integrated in a model, run in batch, and more
How to add your plugin to this repository
- Go to QGIS plugin repo and click on Share a plugin. The approval procedure should take 2 weeks maximum. If not approved, a e-mail will be sent to you. For a prompt approval, please check that your plugin:
- has no malicious code
- goes to the appropriate menu (Vector, Raster, Web, Database)
- has at least minimal documentation
- does not duplicate of existing functionalities or plugin, unless there is a good reason
- has a proper license
- does not contain architecture-dependant binaries
- supports English language
- provides a minimal data set for testing
- has (in the metadata) a link to the code repository and to a bug tracking system of your choice (you can use github or other infrastructures)
- is of reasonable size (try to keep it small, and not exceed 10 Mb)
- english language is used in code (comments, identifiers)
- source repository is in good shape:
- no generated file is left in repository (ui_*.py, resources_rc.py, gen. help files…)
- good code organization (subfolders)
- code comments are available
- PEP8 & Python/QGIS guidelines compliance
- a README file and a LICENCE file (GPL2 or later mandatory) are present
- the licence is compliant wrt external dependencies (e.g. no import of proprietary python module)
- does not break any other licence (e.g. for data providers, etc.) or do any illegal thing
- more info about licencing in our blog post
- if the plugin has a need for external dependency, this it should be clearly stated in the About metadata field
- if some dependencies are not available in OSGeo4w Python, a clear indication of how to install them should be given
- the name of the plugin and the folder name do not repeat the word `plugin`
- finally, the use of plugin builder plugin is recommended, especially for new users.