If you’ve been working in surveying or drone operations for more than five minutes, someone has mentioned GIS. You’ve probably nodded along. But if you’re honest with yourself — what does it actually mean, and why does it matter for your workflow?
Here’s a grounded, no-jargon explanation.
What GIS actually is
GIS stands for Geographic Information System. At its core, it’s any system that stores, analyzes, and displays data that has a geographic component — meaning the data is tied to real-world locations.
That could be:
- A point cloud of an underground mine, georeferenced to real-world coordinates
- A GeoTIFF orthophoto showing vegetation health across a farm
- A KML file marking property boundaries
- A simple spreadsheet of GPS coordinates with soil sample results
The “system” part is important. GIS isn’t just data — it’s the combination of the data, the software that processes it, and the workflows that move information from capture to decision-making.
The difference between GIS and mapping
People often use “GIS” and “mapping” interchangeably, but they’re not the same thing.
Mapping is the output — a visual representation of geographic information. A map can be a PNG, a PDF, a 3D model, or an interactive web map.
GIS is the whole system — the capture, storage, analysis, and delivery of the underlying data. A GIS might produce dozens of different maps from the same dataset, or it might never produce a traditional “map” at all.
If you’re delivering a point cloud to a structural engineer, you’re participating in a GIS workflow — even if nobody called it that.
Why surveyors and drone operators are GIS professionals
Here’s the thing most GIS textbooks won’t tell you: if you’re flying drones for survey work, running a LiDAR scanner underground, or producing georeferenced orthomosaics — you’re already doing GIS. You just might not have the title.
The data you capture is spatial data. The software you use (Pix4D, RealityCapture, QGIS, ArcGIS, Potree) is GIS software. The deliverables you produce are GIS outputs.
The gap isn’t technical knowledge — it’s usually the delivery layer. Most surveyors are excellent at capturing and processing spatial data. Where the workflow breaks down is sharing it: getting the data from your machine to your client in a way they can actually engage with.
GIS data formats surveyors commonly work with
| Format | What it is |
|---|---|
| LAS / LAZ | Point cloud from LiDAR or photogrammetry |
| GeoTIFF | Raster image with embedded georeference data |
| KML / KMZ | Google Earth vector data (boundaries, pins) |
| GeoJSON | Web-friendly vector format |
| Shapefile (.shp) | ESRI vector format — still widely used |
| DWG / DXF | AutoCAD — common in as-built deliverables |
| E57 | Terrestrial LiDAR point cloud format |
| GLB / OBJ | 3D mesh models |
The GIS delivery problem
The surveying industry has solved the hard part — capturing accurate spatial data — better than ever. The unsolved part is delivery.
A point cloud in a .las file is useless to a client who doesn’t have CloudCompare installed. A GeoTIFF is useless to a project manager who’s never opened QGIS. And emailing a Dropbox link to a 4 GB file isn’t a professional deliverable — it’s a rough handoff.
Modern GIS delivery means clients can open a browser, click a link, and see their data — without installing anything. That’s what platforms like Swyvl are built for: turning your spatial deliverables into a professional, browser-based experience that clients can actually use.
The bottom line
GIS isn’t a software category — it’s a way of thinking about how geographic data is captured, managed, and delivered. Surveyors and drone operators are at the sharp end of that system: you’re the ones capturing the data that everything else depends on.
Understanding GIS helps you speak the language of the engineers, asset managers, and project owners you’re delivering to — and it helps you deliver data in a way that gets used, not just stored.