GIS Is More Than Making Maps

Ask most people what GIS is for, and they'll describe a map. That's not wrong, but it undersells what the discipline actually does. A map is the output. The real work of GIS is turning location-based data — survey points, LiDAR scans, infrastructure records, incident locations — into something a person can use to make a better decision. The map is just the interface for that decision.

The same underlying skill, three different contexts

Over the course of my career, I've applied geospatial data to three fairly different problems: processing LiDAR and survey datasets for engineering and mapping applications, building geospatial workflows to support civil infrastructure projects, and now coordinating GIS as part of emergency communications infrastructure. On the surface, these look like unrelated jobs. Underneath, they're the same discipline pointed at different questions.

In civil engineering, the question is usually something like: where does this pipe network need to go, and what does the terrain force us to account for? In public safety, the question is: where exactly is this incident, and what's the fastest, safest way to get a unit there? In both cases, GIS is the layer that converts raw spatial data into something actionable — a design decision, a dispatch decision, a resource allocation decision.

Data quality is a decision-making problem, not just a technical one

A dataset can be technically valid and still be operationally useless if it's out of date, mismatched in projection, or missing the field that actually matters for the decision at hand. Geoprocessing tools can catch a lot of that, but the harder part is understanding what "good enough" means for the specific decision the data is feeding. A property boundary that's accurate to the meter might be completely fine for zoning analysis and completely wrong for engineering design. Knowing the difference is where GIS experience actually pays off.

Where this is headed

The tools keep changing — GIS platforms, open-source stacks like QGIS and PostGIS, and now software development directly on top of geospatial data — but the core job hasn't: take messy, real-world spatial data and make it trustworthy enough that someone can act on it with confidence. Building software around that data, instead of only analyzing it inside a GIS platform, is the next natural extension of that same work.