Giter Site home page Giter Site logo

qgis-documentation's Introduction

🧪 QGIS tests Docker Status Build Status OpenSSF Scorecard OpenSSF Best Practices 🪟 MingW64 Windows 64bit Build DOI

QGIS is a full-featured, user-friendly, free-and-open-source (FOSS) geographical information system (GIS) that runs on Unix platforms, Windows, and MacOS.

Features

1. Flexible and powerful spatial data management

  • Support for raster, vector, mesh, and point cloud data in a range of industry-standard formats
    • Raster formats include: GeoPackage, GeoTIFF, GRASS, ArcInfo binary and ASCII grids, ERDAS Imagine SDTS, WMS, WCS, PostgreSQL/PostGIS, and other GDAL supported formats.
    • Vector formats include: GeoPackage, ESRI shapefiles, GRASS, SpatiaLite, PostgreSQL/PostGIS, MSSQL, Oracle, WFS, Vector Tiles and other OGR supported formats.
    • Mesh formats include: NetCDF, GRIB, 2DM, and other MDAL supported formats.
    • Point-cloud format: LAS/LAZ and EPT datasets.
  • Data abstraction framework, with local files, spatial databases (PostGIS, SpatiaLite, SQL Server, Oracle, SAP HANA), and web services (WMS, WCS, WFS, ArcGIS REST) all accessed through a unified data model and browser interface, and as flexible layers in user-created projects
  • Spatial data creation via visual and numerical digitizing and editing, as well as georeferencing of raster and vector data
  • On-the-fly reprojection between coordinate reference systems (CRS)
  • Nominatim (OpenStreetMap) geocoder access
  • Temporal support

Example: Temporal animation

Example: Temporal animation

Example: 3D map view

Example: 3D map view

2. Beautiful cartography

  • Large variety of rendering options in 2D and 3D
  • Fine control over symbology, labeling, legends and additional graphical elements for beautifully rendered maps
  • Respect for embedded styling in many spatial data sources (e.g. KML and TAB files, Mapbox-GL styled vector tiles)
  • In particular, near-complete replication (and significant extension) of symbology options that are available in proprietary software by ESRI
  • Advanced styling using data-defined overrides, blending modes, and draw effects
  • 500+ built-in color ramps (cpt-city, ColorBrewer, etc.)
  • Create and update maps with specified scale, extent, style, and decorations via saved layouts
  • Generate multiple maps (and reports) automatically using QGIS Atlas and QGIS Reports
  • Display and export elevation profile plots with flexible symbology
  • Flexible output direct to printer, or as image (raster), PDF, or SVG for further customization
  • On-the-fly rendering enhancements using geometry generators (e.g. create and style new geometries from existing features)
  • Preview modes for inclusive map making (e.g. monochrome, color blindness)

Example: Map of Bogota, Colombia in the style of Starry Starry Night, by Andrés Felipe Lancheros Sánchez

Map of Bogota, Colombia in the style of Starry Starry Night

For more maps created with QGIS, visit the QGIS Map Showcase Flickr Group.

QGIS Map Showcase

3. Advanced and robust geospatial analysis

  • Powerful processing framework with 200+ native processing algorithms
  • Access to 1000+ processing algorithms via providers such as GDAL, SAGA, GRASS, OrfeoToolbox, as well as custom models and processing scripts
  • Geospatial database engine (filters, joins, relations, forms, etc.), as close to datasource- and format-independent as possible
  • Immediate visualization of geospatial query and geoprocessing results
  • Model designer and batch processing

Example: Travel isochrones

Example: Travel isochrones

Example: Model designer

Example: model designer

4. Powerful customization and extensibility

  • Fully customizable user experience, including user interface and application settings that cater to power-users and beginners alike
  • Rich expression engine for maximum flexibility in visualization and processing
  • Broad and varied plugin ecosystem that includes data connectors, digitizing aids, advanced analysis and charting tools, in-the-field data capture, conversion of ESRI style files, etc.
  • Style manager for creating, storing, and managing styles
  • QGIS style hub for easy sharing of styles
  • Python and C++ API for standalone (headless) applications as well as in-application comprehensive scripting (PyQGIS)

Example: Style manager

Example: Style manager

Example: Plugins

Example: Plugins

5. QGIS Server

Headless map server -- running on Linux, macOS, Windows, or in a docker container -- that shares the same code base as QGIS.

  • Industry-standard protocols (WMS, WFS, WFS3/OGC API for Features and WCS) allow plug-n-play with any software stack
  • Works with any web server (Apache, nginx, etc) or standalone
  • All beautiful QGIS cartography is supported with best-in-class support for printing
  • Fully customizable with Python scripting support

Example: QGIS server WMS response

Example: QGIS Server response to a WMS request

Example: QGIS server WFS response

Example: QGIS Server response to a WFS Feature request

Under the hood

QGIS is developed using the Qt toolkit and C++, since 2002, and has a pleasing, easy to use graphical user interface with multilingual support. It is maintained by an active developer team and supported by vibrant community of GIS professionals and enthusiasts as well as geospatial data publishers and end-users.

Versions and release cycle

QGIS development and releases follow a time based schedule/roadmap. There are three main branches of QGIS that users can install. These are the Long Term Release (LTR) branch, the Latest Release (LR) branch, and the Development (Nightly) branch.

Every month, there is a Point Release that provides bug-fixes to the LTR and LR.

Free and Open Source

QGIS is released under the GNU Public License (GPL) Version 2 or any later version. Developing QGIS under this license means that you can (if you want to) inspect and modify the source code and guarantees that you, our happy user will always have access to a GIS program that is free of cost and can be freely modified.

QGIS is part of the Open-Source Geospatial Foundation (OSGeo), offering a range of complementary open-source GIS software projects.

Installing and using QGIS

Precompiled binaries for QGIS are available at the QGIS.org download page. Please follow the installation instructions carefully.

The building guide can be used to get started with building QGIS from source.

For installation of QGIS Server, see its getting started documentation.

Documentation

A range of documentation is available. This includes:

Help and support channels

There are several channels where you can find help and support for QGIS:

  • Using the QGIS community site
  • Joining the qgis-users mailing list
  • Chatting with other users real-time. Please wait around for a response to your question as many folks on the channel are doing other things and it may take a while for them to notice your question. The following paths all take you to the same chat room:
    • Using an IRC client and joining the #qgis channel on irc.libera.chat.
    • Using a Matrix client and joining the #qgis:osgeo.org room.
  • At the GIS stackexchange or r/QGIS reddit, which are not maintained by the QGIS team, but where the QGIS and broader GIS community provides lots of advice
  • Other support channels

Get involved with the community

Bug reporting and bug fixing

You can help us by submitting bug reports or fixing bugs in the QGIS bug tracker.

New features and enhancements

If you wish to contribute patches you can:

  1. fork the project
  2. make your changes
  3. commit to your repository
  4. and then create a pull request.

The development team can then review your contribution and commit it upstream as appropriate.

If you commit a new feature, add [FEATURE] to your commit message AND give a clear description of the new feature. The label Needs documentation will be added by maintainers and will automatically create an issue on the QGIS-Documentation repo, where you or others should write documentation about it.

For large-scale changes, you can open a QEP (QGIS Enhancement Proposal). QEPs are used in the process of creating and discussing new enhancements or policy for QGIS.

Translations

Please help translate QGIS to your language. At this moment about forty languages are already available in the Desktop user interface and about eighty languages are available in transifex ready to be translated.

The translation process is managed by the Translation Team and all the activities are done under the Transifex platform.

Other ways to contribute

If you are not a developer, there are many other possibilities that do not require programming skills to help QGIS to evolve. Check our project homepage for more information.

qgis-documentation's People

Contributors

agiudiceandrea avatar alexbruy avatar anitagraser avatar benoitdm-oslandia avatar capooti avatar dassau avatar delazj avatar dependabot[bot] avatar diethard2 avatar digro avatar dragons8mycat avatar elpaso avatar felixfeckler avatar ghtmtt avatar gustry avatar havatv avatar jean-roc avatar junek avatar m-kuhn avatar mach0 avatar pblottiere avatar pcav avatar rduivenvoorde avatar rosaguilar avatar selmavh1 avatar srnetochan avatar timlinux avatar tudorbarascu avatar yjacolin avatar yoichigmf avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

qgis-documentation's Issues

[Vector chapter] move symbol configuration out of renderers section

Currently symbol creation is inside the renderers subsubsection in the Style subsection (vector properties chapter).

Symbol creation is rather important and complex. We should move this part outside even in a specific chapter/setion or in a specific subsection in the working with vector file -> Properties Section.

This ticket is here to have a discussion and keep history. The code changes will be link to it if any.

Should We Include Blank Space for Notes/Answers?

@jj0hns0n has included left in (in his excellent re-write of the database-related modules) blank space for end-users to hand-write solutions to questions: is this something we want to do throughout the docs? Or should we use the "Check Your Results" links to link to an explained answer on the answers page (as per current)?

My feeling is that this is a training rather than testing manual and that the white space impacts the layout and usability of the docs, especially when rendered in HTML.

However, a lot of the questions relate to structuring SQL queries and allowing the end-user to hand-write possible solutions could be very helpful.

CC

@timlinux @rduivenvoorde

Update

As pointed out by @jj0hns0n, the blank spaces were already there, so the proposition is that we remove them and replace with "Check Your Results" links.

Task: Update All Image Links

Problem

Links to screenshots currently point to e.g. _static/img.png. They should point to e.g. static/img.png.

Solution

As we update the manual content, we need to make sure all images point to the correct location.

Notes

During the build process, the relevant static files (relevant to build localisation) are copied into /static/.

10.2.2: OpenLayers Plugin

The section on OpenLayers plugin says that the plugin is accessible at:
Plugins -> OpenLayers plugin -> OpenLayers overview

It seems that the OpenLayers plugin menu is now under:
Web -> OpenLayers plugin ...

Web client better explained and updated

In chapter QGIS as OGC Data Server there is outdated part regarding web clients and plugin for web. Needs to be better explained maybe in separate chapter.

[training] Wrong path for the picture

File: source/docs/training_manual/processing/batch_modeler.rst
Two pictures are not found:

  • WARNING: image file not readable: docs/training_manual/processing/img/batch_modeler/dialog.png
  • WARNING: image file not readable: docs/training_manual/processing/img/batch_modeler/filled.png

such directory doesn't exist.

APT key has expired

The QGIS documentation mentions an old key for the APT repository:

http://qgis.org/en/site/forusers/alldownloads.html#debian

It still mentions key 997D3880 for "Quantum GIS Archive Automatic Signing Key (2012) [email protected]".

It should mention the new key 47765B75 for "Quantum GIS Archive Automatic Signing Key (2013) [email protected]".

But when you add either of these keys, APT complains about expired keys:

W: GPG error: http://qgis.org sid Release: The following signatures were invalid: KEYEXPIRED 1376750759 KEYEXPIRED 1376750759 KEYEXPIRED 1376750759

Rationalize section numbering system in training manual

Section numbers are a good idea, but something is up with the training manual, as section numbers change depending on what page you're looking at:

You can see this quickly from the main TOC, where Section 9 has subsections 9.1, 9.2, 9.3, but Section 10 only has 1,2,3.

So when you go to Section 10.1, it looks like Section 1 all over again. This is confusing.

9.1: http://docs.qgis.org/2.0/en/docs/training_manual/complete_analysis/raster_to_vector.html
10.1: http://docs.qgis.org/2.0/en/docs/training_manual/qgis_plugins/fetching_plugins.html

I can't build it myself to test (see #207), but as far as I am aware, a single use of :numbered: at the root of the doc build should cascade the numbering system all the way down. Perhaps the extra instances of :numbered: are messing with the counter?

Incremental compiling of documentation?

The instructions in the README suggest the following workflow:

  • run ./scripts/post_translate.sh en locally to build the english docs
  • edit/update the rst files with the english documentation from ./source/docs/user_manual/
  • run ./scripts/post_translate.sh en locally again to check your changes

However, the third step recompiles the entire documentation from scratch, not just the file that has been changed. This takes over 2 minutes on my laptop and makes it hard to check as I'm working.

Is there a way to do incremental updates when recompiling?

10.2.1: Raster Terrain Analysis Plugin - move to earlier in book

The chapter detailing plugin installation, specifically the Raster Terrain Analysis Plugin, is out of sequence with the tutorial that uses the Raster Terrain Analysis Plugin (chapter 8.3). It seems reasonable to cover plugins after covering core functionality, as is currently the case. Is there some way to reduce the duplication in the book regarding the Raster Terrain Analysis Plugin?

Task: Update Theme

Problem

The Training Manual has not properly inherited the qgis.org theme and the layout is consequently not perfect.

Solution

Ensure that all required CSS files are properly built with the training manual

Some dead links, one typo in QGis cookbook.

When reading the QGis cookbook, I found some dead links and typos, plus an error. Is this the right place to report them? I refer to the documentation: http://docs.qgis.org/testing/en/docs/pyqgis_developer_cookbook/intro.html

Dead links:

page: http://docs.qgis.org/testing/en/docs/pyqgis_developer_cookbook/intro.html
section: Intersection
dead links (marked with [link]) in sentence:
"There are some resources about programming with PyQGIS on [QGIS blog]. See [QGIS tutorial ported to Python] for some examples of simple 3rd party apps."

page: http://docs.qgis.org/testing/en/docs/pyqgis_developer_cookbook/canvas.html
section: Using Map Canvas
dead links (marked with [link]) in sentence:
If not, please make sure to read the [overview of the framework].

Errors in cookbook:

page: http://docs.qgis.org/testing/en/docs/pyqgis_developer_cookbook/intro.html
section: Python console
error: Command layer.getLayerID() (shown on screenshot) does not compile (AttributeError: 'QgsVectorLayer' object has no attribute 'getLayerID'). According to forum http://osgeo-org.1560.x6.nabble.com/How-get-the-ID-of-active-layer-in-python-td5095979.html, this method has been renamed to id().

page: http://docs.qgis.org/testing/en/docs/pyqgis_developer_cookbook/vector.html#modifying-vector-layers-with-an-editing-buffer
section: Modifying Vector Layers with an Editing Buffer
This sentence contains typo (marked as [typo]. Should be beginEditCommand() instead of beginEndCommand()):
The [beginEndCommand()] will create an internal “active” command and will record subsequent changes in vector layer.

Module 14: PostgreSQL - Update English Content

Task

We need to port Module 6 of the training manual to QGIS 2.0

Link to Current

http://manual.linfiniti.com/en/postgres/index.html

Subtasks

  • Lesson 1: Text
  • Lesson 1: Screenshots - @Erve1879
  • Lesson 2: Text
  • Lesson 2: Screenshots - @Erve1879
  • Lesson 3: Text
  • Lesson 3: Screenshots - @Erve1879
  • Lesson 4: Text
  • Lesson 4: Screenshots - @Erve1879
  • Lesson 5: Text
  • Lesson 5: Screenshots - @Erve1879
  • Lesson 6: Text
  • Lesson 6: Screenshots - @Erve1879

Update Training Manual Cadastrals

We need to update the training manual cadastrals so that they use OSM data sources and can be easily replaced with localised data sets

Missing file REQUIREMENTS.txt

The installation instructions say:

You can install all tools in one go via the REQUIREMENTS.txt here in the root of this repo:
pip install -r REQUIREMENTS.txt

There's no REQUIREMENTS.txt in the repository.

mentionning a second time that the « Add PostGIS Layer... » option is in the Layer menu

Re : mentionning a second time that the « Add PostGIS Layer... » option is in the Layer menu

Hello, Bonjour,

(I have 1 single comment about one page, and I do not know exactly where to contribute and I do not want to enthrall me into rst or GitHub for the time being.)

In the page « Supported Data Formats »
In chapter « PostGIS Layers »
in the section « Loading a PostGIS Layer »
http://www.qgis.org/en/docs/user_manual/working_with_vector/supported_data.html?#loading-a-postgis-layer

It would be good to add a wording that would be similar to the one in the previous section « Creating a stored Connection » *, to mention that the Add PostGIS Layer... option is in the Layer menu.

(I am not familiar with QGIS, so this summary would help me when I read only this section without reading again the first one...)


  • Creating a stored Connection

http://www.qgis.org/en/docs/user_manual/working_with_vector/supported_data.html?#creating-a-stored-connection

This sections states :
« The first time [...] »
« selecting the Add PostGIS Layer... option from the Layer menu »

Section 8.3.3: incorrect photo (slope settings not depicted)

The screen capture for the DEM (Terrain models) toolkit in section 8.3.3 does not depict the settings for Slope. Rather, Hillshade is still visible, perhaps from the previous section.

Please update the image for section 8.3.3 to display the settings for Slope.

Can't build project on Windows

Looks like the Makefile is Linux-specific. Creating a make.bat (or otherwise making the build platform-agnostic) would allow for Windows users to more effectively contribute to the documentation effort.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.