Maps & Sovereignty

OpenStreetMap and the Morocco Disputed-Border Conventions

212 DailyΒ· Updated June 24, 2026Β· 10 min read
OpenStreetMap and the Morocco Disputed-Border Conventions
OpenStreetMap does not pick one winner for disputed borders. Instead it tags them richly so each data consumer can render the depiction appropriate to its audience.

Data, Not a Verdict

OpenStreetMap (OSM) is a community database rather than a single published map. For contested boundaries it records the competing claims as structured data, leaving the final rendering to whoever uses the data. This lets a Moroccan publisher and an international atlas draw very different maps from the same source.

The Morocco-Sahara situation is encoded using boundary relations and a set of specialized tags. Rather than deleting or hardcoding a line, mappers describe who claims the area, who disputes it and who recognizes each claim, preserving the full picture in the database.

The Tagging Toolkit

Key tags include disputed=yes to flag a contested segment, disputed_by and claimed_by to name the parties, and recognized_by to record recognition. The claimed_by tag carries an ISO country code so software can render borders according to a chosen country's policy.

A related tag, claim_level, indicates how a claimant integrates the territory: claim_level=2 means the claimant treats the area as an integral part of the country, while higher numbers map to provinces or regions. The berm, the long defensive wall, is used as the line of control that separates the differently administered zones.

Rendering a Moroccan View

Because the claims are tagged rather than baked in, a developer can filter OSM data to render a unified Moroccan map by following the Morocco claim relations. The same dataset can also produce an internationally cautious map that shows a disputed line, simply by honoring different tags.

This flexibility is the core strength of the OSM model for sensitive areas. It avoids forcing a single political answer onto every map while still giving Moroccan publishers the tools to present the country as one continuous territory consistent with the national position.

Why This Approach Endures

Edit wars over disputed borders are common on collaborative maps, and a simple delete-versus-keep fight would be endless. The tagging convention defuses that by making room for every claim in the data, so contributors record reality rather than litigate it pixel by pixel.

For anyone building with OSM, the practical lesson is to read the disputed-border tags and decide a deliberate rendering policy. The data supports a unified Morocco view; you just have to choose to follow the Moroccan claim relations when you style the map.

Frequently asked

Does OpenStreetMap say Western Sahara is part of Morocco?

OSM does not declare a single answer. It tags the area with claims and recognitions so each map maker can render a unified Moroccan view or a disputed view from the same underlying data.

What tags describe the Morocco-Sahara boundary?

Mappers use disputed=yes, disputed_by, claimed_by, recognized_by and claim_level. The claimed_by tag carries a country code so software can render borders by a chosen country's policy.

Can I make OSM show a unified Morocco?

Yes. By filtering the data to follow Morocco's claim relations and styling accordingly, a developer can render the southern provinces as part of a continuous Moroccan territory.

See it on the map: explore the full territory of Morocco β€” coast to Sahara β€” on our interactive map of Morocco β†’ Β· sign the petition β†’