{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihq3yp63jfytvqoulh3lnj7fnbvmgeghs6d4qi5aa4xhi5vmenjwe",
    "uri": "at://did:plc:4tuge3k3comfj4nfvqnwkemn/app.bsky.feed.post/3mj25mw5kedv2"
  },
  "path": "/user/FajrAl/diary/408485",
  "publishedAt": "2026-04-08T15:02:36.000Z",
  "site": "https://www.openstreetmap.org",
  "textContent": "Mapping administrative boundaries in Indonesia can tricky especially when dealing with overlapping names. Here is my simplified workflow for preparing this data:\n\n### 1. Data Sourcing\n\nFirst, download the official spatial data from **Peta Rupa Bumi** by Badan Informasi Geospasial. This serves as the primary geometry source.\n\n### 2. Extracting Place Nodes\n\nSince the source data is in polygon format, I use **QGIS** to extract the centroids (points). These points are essential for creating the `place=*` tags that represent the center of each administrative area.\n\n### 3. The Importance of Kemendagri Codes\n\nThe polygons include **Kemendagri reference codes**. These are vital for:\n\n  * **Conflation:** Ensuring data matches across different sets.\n\n  * **Identification:** Many villages (admin_level 7 or 8) share the same name. The code helps distinguish them within a Regency or Province.\n\n\n\n\n### 4. Enriching Metadata\n\nUsing spreadsheet tools and conflation techniques, I cross-reference the data to add:\n\n  * `wikidata` and `wikipedia` tags.\n\n  * Multilingual names (`name:en`, etc.).\n\n\n\n\n### 5. Geometry Processing\n\nTo follow OSM best practices, I convert the polygons into **independent ways (polylines)**.\n\n  * This allows adjacent areas to share a single boundary line via a **multipolygon relation**.\n\n  * Once converted, I export the result as a `.geojson` file.\n\n\n\n\n### 6. Final Tagging\n\nFinally, I use the previously extracted **place nodes** to quickly copy and paste the relevant tags into the new multipolygon relations in my OSM editor.",
  "title": "Preparing Indonesian Admin Boundaries for OSM Made Simple"
}