What GIS Actually Is

A Geographic Information System (GIS) is software built around one core idea: every piece of data is tied to a location on the earth through a coordinate reference system (CRS), such as a state plane coordinate system or UTM zone. Once data is georeferenced, a GIS can store it, display it as a layer on a map, and run spatial analysis on it that a spreadsheet or CAD file alone cannot easily do. For civil, environmental, and site-development engineers, this matters because almost every project decision is spatial: where the parcel boundary sits relative to a floodplain, how stormwater flows across a watershed, where existing utilities conflict with a proposed alignment, or which soil types underlie a building pad.

A typical GIS project stacks many layers on top of a common coordinate system: parcel boundaries, road centerlines, utility networks, floodplain boundaries, soil classifications, zoning districts, and topographic contours. Because every layer shares the same CRS, an engineer can overlay them and ask questions no single layer could answer alone, such as which parcels fall inside both a 100-year floodplain and a proposed sewer service area. Beyond simple overlay, GIS supports true spatial analysis: buffer zones (a 50-foot setback around a wetland), watershed delineation (tracing the contributing drainage area to a point), overlay analysis (combining constraint layers to find buildable land), and viewshed analysis (determining what is visible from a given point, used in siting towers or wind turbines).

The Two Core Data Models: Vector and Raster

Vector Data

Vector data represents discrete features as points, lines, and polygons, each carrying an attribute table of descriptive information. A parcel is stored as a polygon whose attribute table might include owner name, parcel ID, zoning code, and acreage. A road is a line with attributes for classification and speed limit. A fire hydrant is a point with an attribute for flow rate. Vector data is precise, editable at the feature level, and ideal for anything with discrete boundaries or discrete objects: property lines, utility lines, manholes, building footprints, and easements.

Raster Data

Raster data instead represents continuous surfaces as a grid of cells, where each cell holds a single value. A digital elevation model (DEM) is a raster in which every cell stores an elevation value; a satellite image is a raster in which every cell stores a color or reflectance value; a rainfall grid stores precipitation depth per cell. Rasters are the natural model for anything that varies continuously across space rather than being cleanly bounded.

This distinction explains why certain engineering analyses are inherently one type or the other. Watershed and stormwater flow analysis is fundamentally raster-based: software determines flow direction and flow accumulation by comparing the elevation value of each DEM cell to its neighbors, then traces water downhill cell by cell to delineate a watershed or stream network. There is no meaningful way to do this with polygons alone. Conversely, parcel management, utility mapping, and easement tracking are inherently vector-based, because these features have exact, legally defined boundaries and require attribute-level record keeping that a raster grid cannot represent efficiently. Most real GIS projects combine both: a vector parcel layer overlaid on a raster DEM and raster floodplain grid.

ArcGIS vs QGIS: An Honest Comparison

ArcGIS, made by Esri, is the de facto industry standard in civil and environmental engineering practice. ArcGIS Pro is the desktop application, paired with ArcGIS Online for cloud-based web mapping and sharing. Esri's toolboxes cover an enormous range of analysis, from hydrology and network analysis to 3D visualization, and its enterprise geodatabase (stored in SQL Server, Oracle, or PostgreSQL) is built for multi-user editing, versioning, and long-term data governance at the scale a municipality, state DOT, or the U.S. Army Corps of Engineers (USACE) requires. Many government agencies and large civil engineering firms mandate ArcGIS simply because their existing data infrastructure, submission standards, or GIS staff are already built around it, regardless of whether a given task technically requires Esri-specific capability.

QGIS is a free, open-source desktop GIS application, and it has matured into a genuinely capable tool for the large majority of everyday mapping and analysis work: digitizing parcels, symbolizing and printing maps, running buffer and overlay analysis, projecting between coordinate systems, and even watershed delineation, thanks to tight integration with the open-source GRASS and SAGA analysis engines through its Processing Toolbox. QGIS has a large, active plugin ecosystem that extends it into surveying, hydrology, and remote sensing workflows. It is popular with smaller engineering firms, environmental consultancies, academic researchers, NGOs, and individual practitioners who either cannot justify an Esri license cost or simply do not need enterprise geodatabase features.

Where ArcGIS still clearly leads is enterprise geodatabase management with versioned multi-user editing, some of its more specialized Spatial Analyst and Network Analyst toolboxes, seamless integration with other Esri products, and, frankly, its status as a client or agency requirement independent of technical merit. Where QGIS holds its own is cost, transparency of its open-source processing algorithms, and adequacy for the vast majority of standard site analysis and mapping tasks an engineer encounters day to day. Neither platform is simply better in every dimension; the right choice depends heavily on who the deliverable is going to and what data infrastructure a firm already has.

PlatformLicense CostBest ForData Format Support
ArcGIS Pro / OnlineCommercial, subscription or perpetual license, often several thousand dollars per seat per yearEnterprise geodatabase management, agency/DOT submissions, advanced network and 3D analysis, large-team collaborationNative geodatabase (.gdb), shapefile, GeoTIFF, CAD formats, broad web service support (REST, WMS, WFS)
QGISFree, open source (GPL license)Standard mapping and site analysis, smaller firms and academia, budget-constrained projects, transparent/customizable workflowsShapefile, GeoJSON, GeoTIFF, spatial databases (PostGIS, SpatiaLite), and via GDAL/OGR, virtually every common GIS and CAD format

Real Civil and Environmental Engineering Use Cases

  • Floodplain and FEMA mapping analysis: overlaying FEMA Flood Insurance Rate Map (FIRM) data with a site's parcel and grading plan to determine special flood hazard area exposure and finished-floor elevation requirements.
  • Watershed delineation for stormwater design: using a DEM to trace contributing drainage area and flow paths to a proposed detention basin or culvert, feeding directly into hydrologic and hydraulic modeling.
  • Utility mapping and coordination: compiling water, sewer, gas, and fiber utility layers from multiple sources onto one CRS to identify conflicts before design or excavation.
  • Environmental site assessment overlay analysis: stacking wetlands, contaminated site records, soil types, and protected species habitat layers to screen a property before acquisition or permitting.
  • Feeding Civil 3D: GIS output such as shapefiles or geodatabase feature classes (parcels, survey points, existing utilities, contours) is routinely imported into Autodesk Civil 3D to build existing-conditions surfaces and alignments, and finished grading or drainage designs are often exported back out as shapefiles for GIS-based review, permitting submittals, or asset management systems.

Common GIS File Formats

Shapefile (.shp)

The shapefile is the most widely supported vector format in GIS, originally developed by Esri but now read and written by virtually every GIS package, including QGIS. It is technically a multi-file format: a single shapefile requires a .shp file for geometry, a .shx index file, and a .dbf file for the attribute table, plus optional files for projection information (.prj) and spatial indexing. Losing any required companion file breaks the dataset.

GeoJSON

GeoJSON is a lightweight, human-readable vector format built on standard JSON, storing geometry and attributes together in a single text file. It is popular for web mapping applications and data interchange because it is easy to inspect, version-control, and parse in most programming languages, though it is less efficient than a shapefile or geodatabase for very large datasets.

GeoTIFF

GeoTIFF is a raster format that embeds georeferencing information, including the coordinate system and pixel-to-ground transformation, directly inside a standard TIFF image file. It is the standard way to distribute DEMs, orthophotos, and satellite imagery, since the file is self-contained and does not require a separate world file to be positioned correctly on a map.

Choosing a Platform

For an engineer deciding between the two, the practical question is rarely which software is technically superior. It is whether the deliverable target, whether a city planning department, a state DOT, or an internal QA/QC process, requires Esri-native geodatabase files, and whether the firm already has the licensing and staff expertise to support ArcGIS. Absent that requirement, QGIS is a fully legitimate professional tool for parcel mapping, watershed delineation, floodplain overlay, and utility coordination, at zero license cost.