Why informal addressing systems in MENA break standard geocoders
A real delivery address that no official database has ever seen — and why the failure is structural, not a data-quality bug.
A driver in Jeddah receives a delivery address: "Behind the water tank, second alley past the fish market, Briman neighborhood." Google Maps returns nothing. Standard geocoding tools fail here because they match against official address databases — and informal settlements were built without formal street registration. There are no database entries to resolve against.
This post explains why the failure is structural, and what purpose-built MENA geocoders do differently.
Why standard geocoders fail in informal addressing environments
Standard geocoding tools work by matching input text against a reference database of known addresses. The geocoder parses the input, looks for street names, building numbers, postal codes, and administrative identifiers, then maps those tokens to coordinates in its database.
This process fails at two distinct points in informal areas.
Streets in Cairo's ashwiyyat — unplanned settlements that grew outside formal urban development — often have no official names, or names assigned locally that never appeared in any government registry.
Formal addressing assigns numbers sequentially along officially surveyed streets. Informal buildings went up as residents could afford them, often room by room, and were registered years later, if at all.
In Jeddah, Saudi Arabia's National Address system has improved formal coverage in KSA's urban centers substantially. The limitation is the National Address system's reach: informal zones and rapidly expanding peri-urban neighborhoods at the city's edge often haven't been surveyed or assigned codes. An address requires official assignment to be in the system; addresses outside that coverage are simply not resolvable through it.
A geocoder can only match what a registry already holds.
Cairo's ashwiyyat grew outside formal development; streets carry local names that never entered any registry.
Informal buildings went up room by room and were registered late, if ever — sequential numbering needs a survey that never happened.
How geocoding failures appear in delivery operations
When a geocoder cannot resolve an address, the outcome depends on how the tool handles the failure.
All three outcomes produce the same result: a failed delivery, a re-delivery attempt, and a frustrated customer. Centroid fallback is the most operationally dangerous, because the failure is invisible in the log — it only surfaces in delivery outcomes, or when you audit results against confidence scores.
Standard geocoding success rates aggregate across all address volume. Strong performance on formal urban addresses masks the failure rate in informal districts. Segment your results by neighborhood and the gap becomes visible.
Standard vs. MENA-specific geocoders: how they handle informal addresses
The two approaches diverge at every stage — from the reference data they draw on to how their coverage grows over time.
How purpose-built MENA geocoders resolve informal addresses
Geocoders built for MENA use approaches global tools do not have — drawing coordinates from the data that does exist in informal areas.
What this means for delivery operations in MENA markets
In Cairo, a large share of delivery addresses in Giza, Shubra, Imbaba, and Ard al-Liwa fall in categories that standard geocoders handle poorly. In Jeddah, neighborhoods beyond the National Address system's formal survey reach face the same problem. For operators working across both markets, this is a routine occurrence, not an edge case.
The practical implication: if your geocoding tool is returning null results or centroid fallbacks on a noticeable percentage of your address volume, the problem is probably not data-entry quality. The addresses your customers submit are the actual addresses they have. Customers in Ard al-Liwa do not have a National Address system code to provide. The question is whether your geocoder resolves the format in which those addresses actually exist.
Check your geocoding failure rate by district, not in aggregate. That breakdown will show where informal-area failures are accumulating — and the aggregate success rate is not.
Some do. Cairo's older ashwiyyat, such as Imbaba and Ard al-Liwa, have partial street naming from retrospective mapping efforts. Coverage is uneven and incomplete, and a geocoder built on official datasets will still fail on a significant share of addresses there even where some formal naming exists.
The National Address system has improved formal address coverage in Saudi Arabia's urban centers significantly. The limitation is reach. Newly developed peri-urban zones and areas settled before the National Address system rollout often have not been assigned codes. An address must be in the system to be resolved through it — and many informal and peri-urban areas in Jeddah and other KSA cities are not.
Most geocoders fall back to district-level or partial matches when they cannot resolve a specific address. These outputs appear as successful geocodes in the log but produce incorrect delivery coordinates. The failure only surfaces when you audit delivery outcomes against confidence scores rather than resolution rates.
In most cases, no. Customers in informal areas submit the actual addresses they have — landmarks, local names, and proximity descriptions rather than formal street numbers. There is no formal address to provide. The fix is a geocoder capable of resolving how those addresses are actually written.
Segment your geocoding results by neighborhood for your actual delivery address volume. Compare null rates and confidence scores in informal-area districts (Ard al-Liwa, Shubra, Imbaba in Cairo; older peri-urban zones in Jeddah) against your city-wide average. That segmented view shows what the aggregate hides.