Ask what it actually takes to give a low-altitude operator - a survey team, an inspection crew, a logistics run - a genuine, trustworthy picture of the airspace they're about to enter, and the honest answer is uncomfortable: no single data source, however good, gets you there. A real operational picture is a synthesis problem before it is a data-access problem, and in Nigeria and West Africa specifically, both halves of that problem are still substantially unsolved.
Four Layers, Not One
A genuinely complete low-altitude picture is built from at least four structurally different kinds of information, each answering a different question:
- Regulatory and temporal awareness - what has been formally notified as active, and when. This is the NOTAM layer: time-bound, authoritative, but only as good as the feed publishing it.
- Ground risk - who and what is beneath the operating area. Population density and building footprint data answer this, and both depend entirely on how well a given territory has actually been surveyed or digitized.
- Vertical obstacle awareness - what stands in the way, and how tall it is. Masts, towers, cranes, and structures near the operating ceiling. This is consistently the least mature layer globally, and particularly so in fast-growing urban environments where construction outpaces any formal survey.
- Airspace structure - the classification framework itself: which volumes carry which rules, and at what altitude those rules change.
Mature aviation markets have spent decades building institutions and data infrastructure around each of these layers independently, then more recently begun integrating them into unified low-altitude traffic management systems as uncrewed operations have grown. That integration work - not any single dataset - is the actual technical achievement.
Why This Is Harder Here Than It Looks Elsewhere
The honest constraint in Nigeria and across much of West Africa isn't a lack of interest or regulatory intent - real certification and permitting frameworks for commercial drone operations already exist. The constraint is that the four layers above rarely exist in the same place, in the same format, or on the same timeline. Some information is held by different institutions entirely. Some exists only in analog or semi-digital form. Some is commercially held, for entirely legitimate reasons, by organizations whose core business isn't aviation data at all. And in several cases, the underlying survey work simply hasn't been done comprehensively yet, at any price.
The gap here isn't one missing dataset - it's the absence of a single place where the four layers are actually made to agree with each other.
Synthesis Is the Actual Hard Problem
It's worth being precise about where the real engineering difficulty sits, because it's easy to assume the challenge is simply "getting access." In practice, even where individual data sources are obtainable, they arrive in incompatible formats, at different resolutions, updated on different schedules, and described using inconsistent identifiers for the same real-world features. Turning that into one coherent, checkable operational picture - the kind an operator can actually trust their flight plan against - is a genuine synthesis problem: reconciling, cross-referencing, and continuously validating disparate sources against each other, not simply piping one feed into a map.
This is precisely the layer where regional, on-the-ground expertise matters more than raw data volume. Knowing which sources are actually reliable for a given part of the region, how to reconcile conflicting information, and how to build systems that degrade honestly rather than silently when a layer is incomplete, is a different skill from simply having access to more data.
Where This Is Heading
Commercial low-altitude operations across West Africa - industrial inspection, agricultural monitoring, logistics, emergency response - are growing faster than the region's data infrastructure for supporting them safely. That gap is real, and it is closing more slowly here than in markets that began this integration work years ago. We think the organizations that actually close it - carefully, layer by layer, with honest handling of what remains incomplete - will end up providing something genuinely foundational to how this industry operates in the region, not just another map.
That is the problem we are actively building toward.