An architect and a city planner can stare at the exact same looking software window and be doing completely different jobs. One is drawing a building. The other is asking why floods keep hitting the same three neighborhoods. Both tools draw shapes on a screen. Only one of them can answer a question.

That's the entire difference between CAD and GIS, and it trips up more beginners than almost anything else in this field.

CAD is essentially a very precise inventory. It knows exactly where a wall starts and ends, down to the millimetre, because engineering tolerances demand it. But ask CAD "which of these hundred plots flood most often" and it has nothing to offer. It was never built to compare, overlay, or reason across features.

GIS trades a little bit of that millimetre precision for something CAD can't do at all: layering. A GIS can stack elevation data, rainfall data, and drainage maps on top of each other and instantly show which zones are at risk. That's spatial analysis, and it's the whole reason GIS exists as its own field.

See the Difference in Practice

Tap through the tabs below. Same real-world scenario, two totally different tools, two totally different answers.

The GIS Family Tree

GIS isn't one single product, it's a category with specialised branches, each one built around a specific type of data. Three you'll run into often:

Every one of these is still a GIS underneath, just tuned for a specific kind of location data. This is also why a genuinely good GIS solution for a city or utility company rarely comes off the shelf; it's shaped around the exact data the client actually has.

CAD tells you what something is. GIS tells you what it means.

Where Trishunya Fits In

Every GIS still needs accurate ground data before it can layer anything meaningful, coordinates, elevations, boundaries, all captured on-site. That's the surveying side of the equation, and it's where field data collection using topography survey methods and modern GPS equipment feeds directly into the GIS layers a planner later analyzes.

Get the field data wrong, and no amount of clever GIS software fixes it later. That's the part most software comparisons skip entirely.

Next time someone calls a drawing "the GIS," you'll know exactly what question to ask back: can it compare, layer, and analyze, or does it just draw accurately? That one question separates the two tools completely.