From tracking real-time traffic to mapping underground water pipes, GIS relies on databases that do more than just store data—they enforce rules, adapt to change, and help you avoid messy mistakes. But with so many options—relational, object-oriented, NoSQL—how do you know which one to use, and what sets them apart?
Object-oriented databases in GIS don’t just store attributes—they can actively prevent errors by enforcing real-world rules, like not allowing two pipes of incompatible sizes to connect.
Object-Oriented Database Management Systems (OODBMS)
An object-oriented database management system (OODBMS) extends the traditional database management system by storing data as objects. Each object represents a collection of data with built-in rules and behaviors, making it smarter than a standard row in a relational database.
Objects have two primary characteristics that make them powerful for GIS:
- Inheritance: Objects share properties with their parent types. For example, in a transportation infrastructure system, every road (a “child” object) inherits general properties like “surface type” from its parent object.
- Hierarchy: Objects exist within a structure, such as roads categorized as highways, local roads, or bike paths, each with unique rules for how they interact.
Object-oriented databases enable GIS tools to share rules and behaviors directly in the data, helping you avoid errors and ensure consistency.
In GIS, object-oriented principles prevent errors and ensure data integrity by enforcing rules. For example, a sewage system model won’t let you connect incompatible data, such as putting two-inch pipe and eight-inch pipe together, thereby helping to prevent design mistakes. This rule enforcement gives you a huge advantage when working on large, complex projects such as infrastructure management or environmental monitoring.
A type of database that stores data as objects, each with properties, behaviors, and rules, rather than just rows and columns.
How might enforcing rules directly in your GIS data help you avoid costly mistakes in real-world projects?
Want to go deeper? The science behind object hierarchy in GIS
Object hierarchy isn’t just about neat organization—it reflects real-world relationships and dependencies, allowing GIS models to represent complex networks (like road systems or river basins) with accuracy and integrity. By modeling features as classes and subclasses, GIS tools can apply broad rules to large groups while still letting individual objects have their own specific behaviors.
Comparing Database Types in GIS
Relational, object-oriented, and NoSQL databases each handle data differently, making them suited for different GIS applications. See the table below for a quick comparison of how these database types are structured and used in GIS.
TABLE 6-1 Comparing Database Types
Feature |
Relational (SQL) |
Object-Oriented |
NoSQL |
|---|---|---|---|
How data are stored |
Data are organized in tables with rows and columns. |
Data are stored as objects with properties and relationships. |
Data are stored in a flexible, nontabular format, such as document-based storage (JSON/XML). |
How relationships work |
Uses primary keys (unique IDs) and foreign keys to link tables. |
Objects inherit properties from parent types. |
Does not rely on traditional table relationships; stores loosely connected data that scales efficiently. |
How it works in GIS |
GIS features are stored in related tables to avoid duplication. |
GIS features behave as objects with rules and hierarchy. |
GIS can handle massive, real-time datasets from sensors, social media, or cloud platforms. |
Best for |
Structured data with clear relationships. |
Complex GIS models where features interact. |
Big Data and Internet of Things (IoT) applications. |
- Learned how object-oriented databases store data as objects with built-in rules
- Explored how relational, object-oriented, and NoSQL databases differ in GIS applications
Enhancing Descriptive Information with Object Orientation
On the surface, a geodatabase (Esri’s implementation of OODBMS) looks similar to any relational database. It has tables with columns and rows, and it uses primary and foreign keys to connect tables. But underneath the surface, the geodatabase goes deeper by organizing data into objects with their own set of rules and behaviors.
For example, take a look at infrastructure models:
- A road network object can store attributes like road type and surface material while also containing rules about speed limits and one-way streets.
- A water utility object might store the pipe diameter along with rules to ensure compatibility between connected pipes.
These rules help maintain data integrity by not allowing entries that don’t meet the established rules for the object’s class. If you try to connect a two-way street with a one-way street going against the flow, your GIS will stop you from making a wrong move.
Think of object-oriented GIS as giving your data “street smarts.” Not only does each object store descriptive information, but — with the inclusion of behaviors and relationships — it also knows how it can behave and interact with other objects in the system.
All databases operate the same way and only store data—rules have to be enforced outside the database in the application code.
Object-oriented databases can store not just data but also the rules and behaviors needed to keep GIS data consistent and error-free.
The ability for objects to share properties and behaviors from parent types, streamlining data management and rule enforcement.
How might object-oriented features in a geodatabase make it easier to manage complex infrastructure networks?
In smart cities, object-oriented GIS databases help manage everything from traffic signals to water lines by applying rules directly to each object—preventing design errors before they happen.
Exploring Emerging Data Storage Systems
As GIS continues to expand into new areas like smart cities, the Internet of Things (IoT), and big data, traditional relational databases are no longer enough. The need to handle unstructured data—large, rapidly changing datasets that don’t fit neatly into rows and columns—is here. That’s where NoSQL database management systems come in.
NoSQL (a.k.a. “not only SQL”) databases, like MongoDB or Cassandra, are typically used in applications that have huge amounts of data requiring real-time processing and analysis, like traffic flows, air quality sensor readings, and social media streams. As the name implies, NoSQL databases typically do not use SQL to interact with data and do not rely on relationships (they’re non-relational). Instead, NoSQL allows you to store data in flexible formats with no fixed schema, making it easier to manage large-scale and diverse data.
Cloud storage has also revolutionized GIS, allowing for massive datasets to be accessed, stored, and managed in real-time across the globe. Cloud-based platforms like Google Cloud, Microsoft Azure, and Amazon Web Services (AWS) allow you to store vast amounts of accessible, on-demand data. These systems have proven beneficial in supporting applications in environmental monitoring, smart cities, and more.
Consider the use of NoSQL in your GIS in the following situations: when you’re working with massive, rapidly changing datasets; when your data doesn’t fit well into tables; or when you need to scale fast for new types of data streams.
Practitioners in environmental monitoring increasingly rely on NoSQL and cloud-based systems to analyze sensor data in real time, adjusting strategies as new data flows in.
What advantages might NoSQL systems offer for a GIS project that tracks live data from thousands of sensors across a city?
Object-oriented and NoSQL databases allow GIS to handle complex rules and massive real-time datasets, supporting everything from infrastructure modeling to smart city applications.
What is an object-oriented database (OODBMS)?
Tap to revealA database that stores data as objects with built-in properties, rules, and behaviors, instead of just rows and columns.
What is inheritance in the context of GIS databases?
Tap to revealThe ability of objects to share properties and behaviors from their parent types, making data management more efficient.
When are NoSQL databases typically used in GIS?
Tap to revealWhen handling massive, unstructured, or real-time data streams, such as live sensor feeds or social media data.
Which database type is best suited for handling massive, real-time GIS datasets from sensors or social media?
Identify which type of database would be best for each scenario below:
- Imagine you are designing a GIS for a city’s road network, requiring detailed traffic rules and relationships. Which database model would you choose?
- You’re tasked with building a GIS to handle live feeds from thousands of air quality sensors. Which storage system is best?
- For a GIS tracking library books by author and subject, which database model offers the simplest structure?
Reflect on a GIS problem you’ve encountered or studied. How might choosing the right database system (relational, object-oriented, or NoSQL) have made a difference in solving it?
NoSQL and object-oriented databases make it possible for GIS to scale efficiently, enforce data integrity, and adapt to new data types—giving you the flexibility to tackle today’s most complex mapping challenges.
Object-oriented principles prevent errors and ensure data integrity by enforcing rules, giving you a huge advantage when working on large, complex projects.