An open brief · Geodata MY · November 2026
What Malaysia’s road data actually looks like, measured.
Malaysia keeps returning to the same question: can we stand on our own geodata? Not licensed from abroad, not maintained elsewhere: ours, complete, current, and usable. This note is a contribution to that question, not a proposal. We measured the national road network end to end from public data, and every step is reproducible. No ask is attached. Take it, check it, use it, or tell us where it is wrong.
The baseline, today
38.3% of vehicle roads carry a name. 1.9% carry a speed limit. 49,508 places hold a complete 3-part address, against a 12M+ National Address System target. Measured across all 16 states and territories, plus 15 cities in depth.
1,392
6,982PPJ · MyGOS · OSM
Three records, three different maps
Three public layers each describe Putrajaya’s road network, and none agrees with the others. Even LLM’s public ArcGIS registry carries two corridors under one code (E1, E8, E19, E33). Merging custodian data without measuring it does not resolve that disagreement. It hides it.
A gap you can close cheaply
Unnamed OSM vehicle ways in Putrajaya within 25 m of a named PPJ segment: 92.2%. Candidate corrections recoverable from public data alone. ISPRS measured OSM road naming at 59% in 2018; our re-run says 61.4%. Eight years, +2.4 points. Attention has not moved it. Instrumentation might.
Who this is for
Why the numbers matter
Sovereign geodata is not won by licensing. It is won when the data is complete, current, routable and verifiable by Malaysians, today. That is an engineering property, and engineering properties can be measured. If Malaysia is to stand on its own base map, the distance between “custodian-held” and “nation-usable” is exactly what these figures describe: per state, per city, per corridor, with the method attached.
Three ways in
Open the interactive map →
See Method & Sources →
Browse the queues →
This is a shared problem with a shared upside. Take any of it: the method, the queues, the scorecards. It exists to be used.
If you see something wrong, missing or worth doing differently, we want to hear it. Every number here has a reproducible trail, and corrections ship in the open. If you want to compare notes with the people behind this, the door is open: khanster.net.