Malaysia/Administrative boundaries import in Peninsular Malaysia

From OpenStreetMap Wiki
Jump to navigation Jump to search

This is an import of a dataset from Sinar Project which provided administrative boundaries covering several states across Peninsular Malaysia.


Adding sub-administrative (district and local administrative) boundaries and updating administrative boundaries (state-level) with better accuracy in some states of Malaysia.


No fixed schedules. Could take between a few hours' time, or might even a whole week. Hopefully work can begin by September.

Import Data


Data source site:
Data license: ODbL, stated explicitly
Type of license: ODbL
Link to permission: E-mail exchange from the owner of the data
OSM attribution:
ODbL Compliance verified: yes

OSM Data Files

Files will be obtained from source and will be handled through JOSM.

Import Type

A one-time import using JOSM and manual adjustments.

Data Preparation

Data Reduction & Simplification

Duplicates (way) in boundary data will be detected and removed. Some of its metadata (i.e. tags) which may not be used widely in OSM would also be scrapped. Ways with more than 2000 nodes will be further split.

Tagging Plans

The primary tag would be boundary=administrative.

Per Template:Admin_level, adjustments would be made accordingly. Insights from the local community have been sought.

Changeset Tags

Data Transformation

JOSM has a GeoJSON plugin which just works: simply drag and drop; and data inspection can be made.

Data Transformation Results

Expected final results: zipped file.

Data Merge Workflow

This import will be managed by User icon 2.svgAkuAnakTimur (on osm, edits, contrib, heatmap, chngset com.). With an import-specific user account, the import will be done on a state-by-state basis.

  1. Some cleanup on the current boundary data, for example: mapped elements that share the same ways with current boundary relation members will be split first.
  2. Load current related boundary relations from OSM.
  3. Open transformed JSON files into JOSM.
  4. Carefully retain relation histories during merge process. If possible, in simpler cases, way histories may be preserved.
  5. QA using inbuilt validation tools (splitting complex relations very carefully), before finalising the upload.


KeepRight to catch slipped mistakes.

See also