{"canonical_url":"https://engineer.company/glossary/gis/","content_markdown":"# GIS\n\n## What it is\n\nA GIS, short for geographic information system, is the combination of data,\nsoftware and working habits that lets people store, analyse and draw things that\nhave a position on the Earth. The QGIS project's own introduction to the subject\nis careful to say that the term covers more than a program: it lists the digital\ndata and the computers alongside the software, and treats GIS as everything\ninvolved in managing and using geographic data. The field took shape in the\n1970s on equipment that only universities and large companies could afford.\nToday a laptop runs a desktop GIS, and a phone shows a web map built on the same\nideas.\n\nEvery GIS works with two kinds of data.\n\n- **Vector data** records a feature as geometry: a point for a well, a line for\n  a road, a polygon for a parish. Each feature carries a row of attributes, so a\n  road knows its name, its surface and its speed limit, and the map can be\n  coloured by any of them.\n- **Raster data** records a grid of cells, each holding one value: the colour of\n  a pixel in an aerial photograph, the height of the ground in an elevation\n  model, the rainfall over a month. Zoom in far enough and the cells show as\n  blocks.\n\nFeatures of one kind are grouped into layers, and layers are stacked on top of\none another. That stacking is where most of the value comes from. Rivers over\nproperty parcels over a flood model answer a question that none of the three\nanswers alone.\n\nWhat lets the layers line up is the coordinate reference system. Every layer has\none, and it tells the software how the numbers relate to real places, whether\nthey are degrees of latitude and longitude or metres east and north of a\nnational origin. A desktop GIS can reproject layers on the fly, so that data\ncaptured in different systems is drawn in one, but it can only do that for a\nlayer whose system is declared correctly.\n\nAround those ideas sit four kinds of work: capturing data by survey, GPS,\ndigitising or laser scanning; storing it in files or in a spatial database;\nanalysing it with operations such as buffers, overlays and interpolation; and\npresenting it as a printed map, a web map or a report.\n\n## Why it matters\n\nThe first useful decision is whether a question is spatial at all. Plenty of\ndata has a location column without needing a GIS: counting orders per city is a\ngroup-by on a text field. A question becomes spatial when the answer depends on\nwhere things are relative to one another, so that moving one of them would\nchange the answer. Which households lie inside the flood extent, which customers\nare more than half an hour's drive from every depot, which stretches of a power\ngrid serve the most new connections: those need geometry, a coordinate reference\nsystem and operations that understand both.\n\nOnce a question is spatial, the next decision is how much GIS to build, and\nthere are roughly three levels. A web map that shows pins and outlines from a\nfile needs a map library and little else. A product that answers spatial\nquestions for its users needs a spatial database underneath, so that the\nquestions run where the data lives. An organisation that captures and maintains\nits own geographic data, correcting it, versioning it and publishing it to\nothers, needs analysts, desktop tools and written rules for data quality,\nbecause the data has become an asset in its own right. Each level costs more\nthan the one before, and each is wasted if the question never needed it.\n\nA map also exposes data problems that tables hide. A customer address geocoded\ninto the middle of the North Sea passes every check in a spreadsheet and is\nobvious the moment it is drawn. That alone makes a quick look at the data on a\nmap worth doing before any spatial analysis is trusted.\n\n## What it looks like in practice\n\nThe breadth of the field shows across\n[more than thirty made-to-measure GIS projects](/portfolio/led-30-gis-projects-from-build-to-support/)\nthat were built, deployed and then supported in production. Their stack lines up\nwith the parts of a GIS described above. PostgreSQL with PostGIS stored the\nspatial data. GDAL/OGR moved it between formats, among them shapefiles, GeoJSON,\nGeoTIFF, KML and vector tiles. QGIS and JOSM handled the data work itself, and\nthe part people saw was a web map drawn with Mapbox GL and Leaflet. The work ran\nfrom 2D and 3D mapping through LiDAR processing, georectification and\nvectorisation to indoor mapping and navigation.\n\nGIS can also be the product rather than the tooling behind it. A SaaS platform\nfor tracking renewable energy assets such as solar panels and wind turbines\nlacked the geospatial side its clients needed to see where those assets stood\nand how they performed.\n[A GIS map application was built into the platform](/portfolio/led-a-gis-map-application-to-10x-revenue-growth/)\non a modular architecture of open-source GIS libraries, chosen to keep the\nsystem light enough for a small team to run. It grew from a basic prototype into\na cornerstone of the platform, with analytics and custom dashboards, and drove a\n10x increase in revenue through upsells, data licensing and new customers.\n\n## Where it goes wrong\n\n**Layers that should overlap sit apart.** Roads from one supplier run beside the\nparcels from another instead of along their edges, or a whole layer appears in\nthe wrong part of the world. The cause is nearly always a coordinate reference\nsystem that is missing or wrong: a shapefile delivered without its `.prj` file,\na spreadsheet of coordinates with no word on what they mean, or data on one\ndatum labelled as another. On-the-fly reprojection can only move a layer whose\nsystem it knows. Fix it at import: record the system of every incoming layer\nexplicitly, reproject everything into one working system for analysis, and check\nthe result against a point whose position on the ground is known.\n\n**Measured areas disagree with the land register.** A field or a building plot\nmeasured on the map comes out larger than its official figure, and the gap grows\nwith distance from the equator. The measurement was taken in the projection used\nfor display. Web maps commonly use a Mercator variant, which keeps angles and\nshapes correct locally and pays for it by distorting area. Measure in an\nequal-area projection or in the national grid made for that region, or let a\nspatial database compute the area on the ellipsoid.\n\n**Neighbouring polygons leave gaps and overlaps.** Municipal boundaries,\ndelivery zones or fields digitised one at a time do not quite meet: thin slivers\nopen between them, or two zones both claim the same strip. Lines that should\njoin stop short or run past each other, which QGIS calls undershoots and\novershoots, and a route search then treats the road network as broken at that\nspot. The features were captured independently with no topology rules. Digitise\nwith snapping to existing vertices, run a topology check that flags gaps and\noverlaps, and keep each shared border as one shared line.\n\n**Attribute names arrive cut short.** A layer exported as a shapefile comes back\nwith `population_density` renamed `population` and a second column renamed\n`populati_1`. The format keeps attributes in a dBASE file, which limits a field\nname to 10 characters and supports only integers, reals, strings and dates, so\ntimes of day and lists are lost as well. Exchange data as GeoPackage, an OGC\nstandard that stores layers and attributes in one SQLite file, and keep\nshapefiles for the tools that accept nothing else.\n\n## Further reading\n\n- [A Gentle Introduction to GIS](https://docs.qgis.org/latest/en/docs/gentle_gis_introduction/)\n  — the QGIS project's free course, from vector and raster data to map\n  production and spatial analysis.\n- [Coordinate Reference Systems](https://docs.qgis.org/latest/en/docs/gentle_gis_introduction/coordinate_reference_systems.html)\n  — the chapter on projection families, what each preserves, and reprojection on\n  the fly.\n- [Topology](https://docs.qgis.org/latest/en/docs/gentle_gis_introduction/topology.html)\n  — gaps, overlaps, undershoots, overshoots and the snapping distance that\n  prevents them.\n- [Shapefile driver](https://gdal.org/en/stable/drivers/vector/shapefile.html) —\n  GDAL's notes on the format's field-name, type and size limits.\n- [GeoPackage](https://www.geopackage.org/) — the OGC encoding that carries\n  vector layers, tiles and attributes in one SQLite file.\n\n\u003chttps://engineer.company/glossary/gis/\u003e\n","date_modified":"2026-10-20T21:59:50Z","description":"What a GIS is beyond the map on screen, how to tell whether a question needs one, and the mistakes that put layers, areas and borders in the wrong place.","formats":{"gemtext":"https://engineer.company/glossary/gis/index.gmi","gopher":"https://engineer.company/glossary/gis/gophermap","html":"https://engineer.company/glossary/gis/","json":"https://engineer.company/glossary/gis/index.json","markdown":"https://engineer.company/glossary/gis/index.md","pdf":"https://engineer.company/glossary/gis/index.pdf"},"kind":"page","language":"en","title":"What is GIS?","url":"https://engineer.company/glossary/gis/","version":1}