{"canonical_url":"https://engineer.company/glossary/qgis/","content_markdown":"# QGIS\n\n## What it is\n\nQGIS is a desktop application for looking at, editing and analysing map data.\nThe project started in May 2002 under the name Quantum GIS, and its first goal\nwas modest: a viewer for spatial data. It has since grown into a full geographic\ninformation system that opens layers from files, spatial databases and web map\nservices, draws them together on one map, edits their geometry and attributes,\nruns analysis over them and lays the result out as a printed map, an atlas or a\nreport.\n\nIt is an official project of the Open Source Geospatial Foundation, released\nunder the GNU General Public License, written in C++ on the Qt toolkit, and it\nruns on most Unix platforms, Windows and macOS. A new release comes out roughly\nevery four months. Every third one, a pattern that began with 2.8, becomes a\nlong-term release, which the project keeps maintaining until the next one\nreplaces it, while the latest release gets a bug-fix point release each month.\nAt the time of writing those are 3.44.15 and 4.2.3.\n\nQGIS reads a great deal through other projects. Vector files come in through the\nGDAL drivers, which is why the list of formats it opens is so long, and rasters\narrive the same way. Tables in PostGIS, SpatiaLite, SQL Server and Oracle are\nread in place, and the project's own feature list makes the point that data is\nshown in its own format and projection, with no conversion to an internal one.\n\nFour further pieces matter once QGIS is shared by a team.\n\nThe project is the unit of work. A `.qgs` file is XML listing every layer's data\nsource with its style, labels, forms and the print layouts; a `.qgz` file is a\nzip archive that holds that XML together with a `.qgd` file of auxiliary data. A\nproject can also be stored inside a GeoPackage or a PostgreSQL database, beside\nthe layers it describes.\n\nProcessing is the analysis framework: a toolbox of algorithms from QGIS's own\nprovider and from GDAL, with GRASS available as a further provider, a model\ndesigner that chains algorithms into a graph, a batch interface, and a history\nof every run. The same algorithms run without the desktop through a command-line\ntool, `qgis_process`:\n\n```sh\nqgis_process run native:reprojectlayer -- \\\n  INPUT=roads.shp TARGET_CRS=EPSG:25832 OUTPUT=roads.gpkg\n```\n\nPyQGIS is the Python interface behind plugins, the built-in console and\nstandalone scripts. And QGIS Server publishes a project file over the web as\nstandard OGC services, WMS, WFS, WCS and OGC API Features, running behind a web\nserver as a FastCGI or CGI application.\n\n## Why it matters\n\nSome spatial work stays manual however good the pipeline is: deciding whether a\nparcel boundary is wrong or the aerial photo under it is, tracing a footprint\nfrom a LiDAR surface, looking over a client's delivery before it is loaded. The\ndecision QGIS bears on is which tool that judgement happens in, and what is left\nbehind once it has been made.\n\nLicence and platform settle the first half. There is no seat to buy, and the\nsame release installs on Linux, macOS and Windows, so a contractor, the client's\nown staff and a build server can all run the version the project was made in.\nEsri's commercial desktop, ArcGIS Pro, runs on Windows only.\n\nThe second half is about what survives the session. QGIS reads PostGIS directly,\nso an edit lands in the table the application serves from and there is no export\nto reconcile later. The Processing history records each algorithm with its\nparameters, and any entry can be copied out as a Python command or as a\n`qgis_process` command. A correction that was worked out by hand in a dialog can\nbecome a line in a script that runs on every delivery after it. A project file\ncan go further and be served as it stands by QGIS Server, so the styling a\nperson set up on the desktop is the styling a web client receives over WMS.\n\nThe costs are mostly about discipline. A project points to data it does not\ncontain, so it is only as portable as the paths it stores. Choosing between the\nlong-term and the latest release is a real choice: one changes slowly, the other\nbrings features every four months.\n\n## What it looks like in practice\n\nOn this site QGIS shows up as the place where spatial data was looked at and\nrepaired by hand, beside the tools that did the bulk work.\n\nFrom 2015 to 2022, the GIS Software Development Team Lead role ran\n[more than thirty GIS projects](/portfolio/led-30-gis-projects-from-build-to-support/)\nend to end, building, deploying and then supporting each one once it was live.\nIn that stack QGIS and JOSM were where the hands-on data work was done, while\nPostgreSQL with PostGIS held the data, GDAL/OGR moved it between shapefiles,\nGeoJSON, GeoTIFF, KML and vector tiles, and the Mapbox GL and Leaflet web maps\ndisplayed it. Between the 2D and 3D digital mapping at one end of those projects\nand the indoor mapping and navigation at the other came LiDAR processing,\ngeorectification and vectorisation.\n\nFrom 2022 to 2024, as a Data Engineer on a large-scale geospatial analytics\nproject, the job was finding and fixing\n[over 1,000 issues in geographical and time-series data](/portfolio/resolved-1000-issues-in-geographical-data/).\nSpatial errors were diagnosed and corrected with GDAL, QGIS and ArcGIS together,\nand the cleaning tasks that kept recurring were automated in Bash scripts.\nPostGIS carried the spatial queries and indexing, and the work contributed to a\n35% reduction in spatial query run times.\n\n## Where it goes wrong\n\nThe desktop makes spatial data look right on screen, and that is where most of\nthe trouble hides.\n\n**A layer lands in the wrong place.** QGIS reprojects every layer on the fly to\nthe project's coordinate reference system, so layers in different systems\noverlay cleanly, provided each layer declares its own system correctly. A\nshapefile that arrives without its `.prj` file declares none, and depending on a\nsetting under Options, QGIS leaves it unknown, prompts for a system, or quietly\napplies the project's or a default one. The repair depends on which mistake was\nmade. When the coordinates are right and only the label is wrong, Assign\nprojection or Define projection change the label and leave every vertex where it\nis. When the coordinates really are in another system, Reproject layer converts\nthem. Find projection, in the same toolbox group, lists the systems in which a\nlayer's extent would fall over a chosen area, which turns a guess into a short\nlist.\n\n**Areas come out in square degrees.** The expression language has two area\nfunctions that look interchangeable. `$area` follows the project's ellipsoid and\nunit settings, so with an ellipsoid set it returns an ellipsoidal area in the\nunit chosen. `area($geometry)` is always planimetric in the layer's own system\nand returns that system's units, so on a layer stored in longitude and latitude\nit returns square degrees, a small decimal that looks plausible in a table. Use\n`$area` for any figure a person will read, or reproject the layer to a projected\nsystem suited to the area before measuring.\n\n**A project opens with half its layers missing.** A project stores where each\nlayer's data lives, not the data. Move the folder, rename a file or open the\nproject on a colleague's machine and the stored paths stop resolving. QGIS then\nshows the Handle Unavailable Layers dialog; choosing to keep them opens the\nproject with those layers listed but drawing nothing until each source is\nrepaired. Saving paths relative to the project file, a project property, lets a\nfolder of project and data move as one. For shared work, storing the project in\nthe same PostgreSQL database or GeoPackage as its layers keeps the two together.\n\n**The same correction is clicked through again next month.** A fix made in a\ndialog leaves the data right and the method in someone's memory. The next\ndelivery with the same fault is fixed by hand again, slightly differently. Copy\nthe run out of the Processing history as a `qgis_process` command the first time\nit works, and put it in the script that loads the delivery.\n\n## Further reading\n\n- [Foreword](https://docs.qgis.org/latest/en/docs/user_manual/preamble/foreword.html)\n  — the project's own account of what QGIS is, where it started and the licence\n  it is released under.\n- [Road Map](https://www.qgis.org/resources/roadmap/) — the release cycle, how\n  long-term releases are chosen and the current schedule.\n- [Working with Projections](https://docs.qgis.org/latest/en/docs/user_manual/working_with_projections/working_with_projections.html)\n  — on-the-fly reprojection and what QGIS does with a layer that has no\n  coordinate system.\n- [Working with Project Files](https://docs.qgis.org/latest/en/docs/user_manual/introduction/project_files.html)\n  — the `.qgs` and `.qgz` formats, projects stored in databases and the repair\n  of broken paths.\n- [Using processing from the command line](https://docs.qgis.org/latest/en/docs/user_manual/processing/standalone.html)\n  — `qgis_process`, its commands and how to pass parameters.\n- [Introduction](https://docs.qgis.org/latest/en/docs/server_manual/introduction.html)\n  — the QGIS Server manual's overview of the services it publishes from a\n  project.\n\n\u003chttps://engineer.company/glossary/qgis/\u003e\n","date_modified":"2026-10-20T21:59:50Z","description":"Where QGIS fits beside a spatial database, why its project files and Processing history matter, and the CRS, area and broken-path traps on the desktop.","formats":{"gemtext":"https://engineer.company/glossary/qgis/index.gmi","gopher":"https://engineer.company/glossary/qgis/gophermap","html":"https://engineer.company/glossary/qgis/","json":"https://engineer.company/glossary/qgis/index.json","markdown":"https://engineer.company/glossary/qgis/index.md","pdf":"https://engineer.company/glossary/qgis/index.pdf"},"kind":"page","language":"en","title":"What is QGIS?","url":"https://engineer.company/glossary/qgis/","version":1}