Click on a forest stand in a GIS map, and a small window pops up: species, age, height, soil type. That window didn't magically appear. It's the output of a filing system running quietly behind every single point, line, and polygon on the map. GIS has tried five different filing systems over the decades, and only one really won.

Open Each Drawer

Tap a drawer below to see how each filing system actually works, in the order GIS software adopted them over time.

Notice the pattern: hierarchical and network models tried to force real-world relationships into rigid structures, and both mostly failed to catch on in GIS. The relational model won because geography rarely fits one tidy hierarchy, a plot of land might relate to its owner, its zoning district, and its flood risk zone all at once, and a relational table handles that without forcing a single parent-child structure.

See the Link Yourself

This is the actual mechanic behind the relational model. Tap a map feature ID on the left, then tap the attribute row on the right that shares its key. That shared ID is the entire trick.

That shared ID column is called the primary key, and it's the entire reason relational databases work so well for GIS solutions. Add a new attribute column tomorrow, and every feature that shares that ID picks it up automatically, no restructuring needed.

Attributes Aren't Just Text

Attribute data also comes in a measurement scale, not just a data type. Whether an attribute is nominal, ordinal, interval, or ratio changes what kind of maths you're allowed to do with it later.

Where This Shows Up in Real Projects

A well-built GIS dashboard for a city or utility client is really a relational database wearing a map as its face. Every layer a user toggles on screen is pulling from a table joined by ID, exactly like the drawer system above, just running invisibly and instantly.

The map shows where. The relational table remembers everything else.

Next time a map pop-up shows you a dozen neatly organized facts about one point, remember what's happening underneath, a table, a shared key, and decades of trial and error to land on this exact system.