Every year, governments announce billions in infrastructure spending that reshapes which land is valuable and which is not. Every year, developers race to identify the parcels that benefit — the ones near the corridors, inside jurisdictions where density allowances just changed, adjacent to sites already under development.
One of our clients, a development firm with a mixed-use portfolio across a major Canadian metro, asked exactly that question of their data. The data existed. The addresses were on file. The zoning records were current. The infrastructure announcements were public.
Their AI could read all of it. It could not reason about any of it spatially — which parcels were near what, governed by which rules, changed when — without hallucinating. The answer took three analysts two weeks and five spreadsheets joined manually by address.
The AI could read the documents. It could not see the world those documents described.
As an intelligence architect, I did not see a data problem. I saw a structure problem. Their databases held the facts. Nothing connected those facts to the physical world — which properties bordered which, which jurisdictions governed which land, which regulations had changed and when, which corridors carried which implications.
The databases were the organs. Each one stored something important. But there was no nervous system — no structured set of relationships connecting them so the system could reason across them.
That missing layer is spatial intelligence.
The word spatial means more than coordinates or an address in a column. It refers to the relationships between things in physical space: what is adjacent, what falls inside a boundary, what sits near a corridor, what changed around a location, and what it means — commercially, legally, operationally — to be there rather than somewhere else.
Most AI today has no access to those relationships. And most businesses do not realize what that blindness is costing them.
The Dimension Hiding in Plain Sight
It has been widely cited, originally from research by the Environmental Systems Research Institute, that approximately eighty percent of all enterprise data contains a spatial component. Addresses, delivery routes, facility coordinates, service territories, customer locations, asset positions, jurisdictional boundaries. Location is embedded in nearly everything a business records.
The global geospatial analytics market — hardware, software, and services for capturing and analyzing location-based data — reached an estimated $117.2 billion in 2026, according to Grand View Research, and is projected to reach $234 billion by 2033. According to Forrester, eighty-two percent of business and technology decision-makers have already implemented or plan to implement location intelligence capabilities. The investment is massive. The adoption is broad.
Yet in most organizations, location data remains flat. An address is a field in a row. A coordinate is a point plotted on a map. A jurisdiction is a label in a dropdown.
There are no relationships. No system knows that this property is adjacent to that one. No system tracks that a regulatory boundary shifted six months ago and now governs properties it did not govern before. No system connects a facility to the supply corridor it depends on, or a customer cluster to the infrastructure serving it.
Enterprises have location data. They do not have location intelligence.
The difference is the same one I have written about before: information is not intelligence. Data without structure is noise. Having eighty percent of your data tagged with a location means very little if the AI reasoning over that data cannot traverse the relationships between those locations.
Why AI Fails at Space
This is not a theoretical gap. It has been measured.
Research evaluating large language models on spatially explicit tasks found that standard LLMs achieve an accuracy of approximately thirty-seven percent. When those same models were connected to a structured spatial knowledge graph, accuracy jumped to eighty-one percent.
A separate study testing knowledge graph approaches against standard AI retrieval on the U.S. Code of Federal Regulations — dense, cross-referenced regulatory text where getting relationships wrong has consequences — found the graph-based system produced correct answers ninety-five percent of the time. Standard retrieval managed twenty-five percent.
Those numbers did not surprise me. They confirmed what I have seen in every intelligence system I have built.
Organs, Nervous System, Model, Trust Layer
The way I look at intelligence architecture is different from how most people in this industry talk about AI.
Most of the conversation starts with the model. Which model is smartest. Which one has the biggest context window. Should we fine-tune. Should we use retrieval. I think that conversation starts too late.
Before the model ever reasons about anything, someone has already decided what it gets to see — what data matters, how things relate to each other, what gets preserved and what gets lost, what can be trusted and what cannot. The model arrives after the most consequential decisions have already been made.
Here is how I think about it. The databases are the organs. Your CRM holds customer relationships. Your GIS holds property and parcel data. Your document management system holds regulatory filings. Your ERP holds transactions. Each organ does something vital, and each one is completely isolated from the others. They do not talk to each other. They do not know the other exists.
The knowledge graph is the nervous system. It is the layer that connects the entities across those organs — the property to the jurisdiction, the jurisdiction to the regulation, the regulation to the amendment, the amendment to the date it took effect, the date to every parcel it now governs. Without that nervous system, you have a collection of organs with no coordination between them. The AI can reach into one organ and pull a record. It cannot reason across the body.
The model sits on top of that structure. In the systems I architect, we fine-tune models for the client’s specific domain — legal reasoning, regulatory interpretation, operational diagnostics — so the model speaks the language of the business, not generic language. But the model is not where the intelligence lives. The model reasons over whatever structure you give it. Give it flat documents with no relationships, it fills in the gaps with hallucination. Give it a governed knowledge graph where every entity is connected, every relationship is verified, and every answer can trace back to its evidence — and the hallucination drops dramatically.
Stanford research demonstrated this concretely in legal AI: production systems from LexisNexis and Westlaw hallucinate seventeen to thirty-three percent using retrieval alone. Adding a knowledge graph layer reduces that by an additional forty percent or more. Citation verification catches the residual. Each layer does something the others cannot. The organs store. The nervous system connects. The model reasons. The trust layer verifies. Remove any one of them and the system degrades.
That is how I look at every intelligence problem, including spatial. The question is never “which model should we use.” The question is: does the structure underneath the model actually represent the world the model needs to reason about? For spatial intelligence, the answer in almost every enterprise today is no.
Why the Gap Still Exists
A reasonable question follows: if spatial knowledge graphs produce results this dramatic, why does the gap still exist?
The answer is structural, and it goes beyond technology.
Geographic information systems and artificial intelligence have been separate disciplines for decades. They do not share tools. They do not share conferences. They largely do not share vocabulary. The people who understand how physical space works — surveyors, GIS analysts, urban planners, engineers — and the people who understand how AI reasons — machine learning researchers, NLP engineers, data scientists — have been building in parallel, not together.
Esri can perform sophisticated spatial computation but has no native language model reasoning. OpenAI can perform sophisticated language reasoning but cannot compute a spatial join. Each side has depth in its domain and a blind spot where the other lives.
But there is a deeper reason this is emerging now. We are at the same frontier that robotics has been pushing toward for years: teaching machines to understand the physical world, not just the digital one. Robotics confronts this through sensors and actuators — a robot must understand where it is, what is near it, and what happens if it moves. Spatial AI confronts it through knowledge architecture — a system must understand where assets are, what governs them, and what changes around them.
Both are part of the same frontier: computation meeting physical reality. And in both cases, the breakthrough is not a better model. It is a better representation of the world the model needs to reason about.
The bridge between GIS and AI — spatial knowledge graphs that both sides can reason over — is being built right now. Wherobots published a framework for Spatial Graph RAG in June 2026 that constructs knowledge graphs from physical-world data using spatial operations rather than natural language processing. Their insight was sharp: spatial relationships need to be computed, not extracted from paragraphs. Researchers at the University of California, Santa Barbara built KnowWhereGraph, a large-scale geo-knowledge graph that uses space, place, and time to connect data silos that no text-based retrieval system could bridge.
These are not incremental improvements to existing tools. They are the beginning of a new category. And in my experience, the organizations that recognize a new category early and build the architecture for it are the ones that create advantages their competitors cannot reverse-engineer later.
Where the Money Is
The enterprise knowledge graph market is projected to grow from $3.5 billion in 2026 to $13.4 billion by 2033. Gartner projects that by 2028, more than fifty percent of AI agent systems will leverage context graphs as foundational infrastructure. The market recognizes that structured knowledge is not optional.
What the market has not yet fully recognized is that spatial may be the highest-value domain for knowledge graph intelligence. Every industry that makes decisions about things in the physical world is exposed.
Development and real estate. The proptech industry is racing to digitize zoning codes. Companies like Zoneomics, LandLogic, ArchiWise, and Deepblocks are building AI-powered platforms that read zoning ordinances and produce feasibility reports. This is useful work. But digitizing a bylaw is not the same as reasoning about what a bylaw means for a specific property in relation to its neighbors, its regulatory history, and its development potential over time. The question my client could not answer — which parcels benefit from converging government infrastructure spending, density changes, and adjacent activity — requires traversal across spatial, temporal, and regulatory relationships. That is a knowledge graph problem, not a document retrieval problem.
Insurance. Property and casualty insurers already invest heavily in geospatial data for underwriting, claims assessment, and risk modeling. Companies like Ecopia and Cape Analytics provide building footprints, property characteristics, and environmental exposure data. But that data is consumed as individual property records. The spatial relationships between properties, between a property and a shifting regulatory boundary, between a portfolio and a corridor of compounding climate risk, remain manually assembled. An insurer that can traverse from a policy to a property to a parcel to a jurisdiction to a regulatory change to portfolio-wide exposure has a fundamentally different risk intelligence capability than one that evaluates properties in isolation.
Supply chain. An ArcGIS spatial knowledge graph case study demonstrated how connecting supply chain data with geospatial analysis revealed hidden dependencies and regional vulnerabilities that flat tabular data could not surface. In a world where supply chains face regulatory fragmentation, climate disruption, and geopolitical volatility, the ability to reason spatially about facility relationships, corridor dependencies, and regional exposure is not an analytical luxury. It is an operational requirement.
Regulatory compliance. Jurisdictional boundaries are not static. Regulations apply to physical space, and the space they apply to changes. Transit-oriented area designations, environmental protection zones, density overlays, tax incentive districts — these are legal constructs that attach to geography and shift over time. Without a spatial knowledge graph that encodes which rules govern which locations and tracks when those rules changed, compliance is a manual research exercise repeated every time a question is asked.
The Compounding Asset
I have written before about the difference between possessing information and owning an intelligence asset. The same distinction applies here.
A spatial knowledge graph is not a report. It is not a dashboard. It is not a one-time analysis. It is a structured representation of how the physical world connects to the regulatory, commercial, and operational reality of a business.
And it must also encode time. A regulatory boundary that changed eighteen months ago governs different properties than it does today. A zoning designation amended twice in three years tells a different story than one that has been stable for a decade. The graph that captures not only where things are but when the rules governing them changed is the graph that produces intelligence.
Every relationship added — every adjacency mapped, every regulatory boundary encoded, every temporal change tracked — makes the next question cheaper to answer and the next decision more informed. The graph does not start over when a new question is asked. It traverses relationships that already exist and finds paths that were not anticipated when the data was first connected.
That is how intelligence compounds. Day one, the graph answers basic spatial queries. Six months in, it supports multi-hop reasoning across jurisdictions, asset portfolios, and regulatory timelines. A year in, it contains institutional spatial memory that no competitor can buy or retroactively recreate.
The competitor who begins building this capability twelve months from now does not start twelve months behind. They start without the twelve months of relationships, changes, and evidence that the early builder has already accumulated. The spatial knowledge graph, like every form of proprietary knowledge architecture, creates a gap that widens with time.
What We Are Building
This is the work I do as an intelligence architect and the work we are building at Argus AI Labs.
Every system we architect follows the same discipline. The databases are the organs — we identify where the client’s knowledge actually lives, across which systems, in what formats. The knowledge graph is the nervous system — we structure the relationships between those entities so the system can reason across them, not just retrieve from them. The model is fine-tuned for the client’s domain — legal interpretation, regulatory analysis, operational reasoning — so it reasons with precision, not generality. And the trust layer verifies every answer against its evidence, because an AI system that cannot show its work is a liability, not an asset.
We have applied this architecture to legal intelligence, where we built a system that resolves Mexican fiscal law across nine source documents, over 1,800 pages, and a judicial interpretation layer that changes what the law means depending on when, to whom, and under what circumstances. We have applied it to institutional knowledge, where we capture the proprietary expertise that companies lose when experienced people leave — the reasoning, the judgment, the relationships between decisions and outcomes that exist in a senior partner’s memory and nowhere else.
Spatial intelligence is the next domain. The same architectural discipline — organs, nervous system, domain-tuned model, trust layer — applied to the physical world. Where are the assets. What governs them. What connects them. What has changed. What that means for the next decision.
We are not building another mapping tool or another document retrieval system. We are building intelligence architectures that treat spatial relationships as first-class knowledge — structured, governed, temporal, and queryable by AI systems that can reason across them without hallucinating.
The world spends $117 billion a year on geospatial analytics, and most of that spend produces maps and reports. The opportunity is in producing intelligence: structured spatial relationships that compound with use and create a durable advantage no competitor can replicate by purchasing better software.
The Question Your AI Cannot Answer
Ask your AI which assets in your portfolio sit within a shifting regulatory boundary, adjacent to active development, inside a corridor where government infrastructure spending was announced this year.
If the answer takes three analysts and two weeks, you do not have a data problem. You have a spatial intelligence problem.
That is what we build.
Book a consultation with Argus AI Labs →
Sources
- Environmental Systems Research Institute (Esri): esri.com
- Grand View Research, Geospatial Analytics Market 2026-2033: grandviewresearch.com
- Grand View Research, Enterprise Knowledge Graph Market 2026-2033: grandviewresearch.com
- Gross, GeoAI and GraphRAG benchmarks, Graphwise 2026: graphwise.ai
- Knowledge graph vs RAG on CFR, arXiv 2026: arxiv.org
- Magesh et al., Stanford, Legal AI Hallucination Study, JELS 2025
- Wherobots, Spatial Graph RAG, June 2026: wherobots.com
- KnowWhereGraph, UC Santa Barbara, February 2026: onlinelibrary.wiley.com
- ArcGIS, Spatial KG Supply Chain Case Study: storymaps.arcgis.com