Skip to content

Auriga

View or edit on GitHub

This page is synchronized from trase/data/indonesia/spatial/boundaries/auriga/readme.md. Last modified on 2026-02-03 10:30 CET by Jason J. Benedict. Please view or edit the original file there; changes should be reflected here after a midnight build (CET time), or manually triggering it with a GitHub action (link).

{% docs indonesia_spatial_boundaries_auriga %}

Spatial Boundaries for Indonesia (Kabupaten and Provinces) — Auriga

This dataset provides administrative boundaries for Indonesia (Kabupaten and Provinces), sourced from Auriga. It is used for spatial analysis in our SEI-PCS Indonesia model and for generating geometry layers on trase.earth map tools.

The data is for 2023 boundary from Badan Informasi Geospatial that has been crosschecked with the information from The Ministry of Home Affairs by Auriga.

What the dataset contains

A shapefile containing:

  • 548 administrative boundaries for Indonesia (Kabupaten and Provinces)
  • Each feature represents an individual administrative unit with its name, multiple identification codes, and polygon geometry. Feature attributes include:
  • OBJECTID: Unique feature ID
  • NAMOBJ: Administrative name (e.g., Kabupaten name)
  • FCODE: Feature code
  • REMARK: Remarks
  • METADATA: Metadata code
  • SRS_ID: Spatial reference ID
  • KDBBPS, KDCBPS, KDCPUM, KDEBPS, KDEPUM, KDPBPS, KDPKAB, KDPPUM: Various administrative codes
  • LUASWH: Area (possibly in hectares or square kilometers)
  • TIPADM: Administrative type code
  • WADMKC, WADMKD, WADMKK, WADMPR: Names of the administrative units (city, district, regency, province)
  • WIADKC, WIADKK, WIADPR, WIADKD: Alternative/legacy codes or names
  • SHAPE_Leng: Perimeter length
  • SHAPE_Area: Polygon area

Known issue: There are inconsistencies in the kabupaten/province hierarchy. For example, kabupaten 9109 is under province 94, but is expected to be a child of province 91.

How we use the dataset in Trase

  • SEI-PCS Model (Indonesia)
  • Spatial metrics and overlays
  • Geometry layers on trase.earth map tools

How to fetch the data from the source

  • Source: Ultimately the data came from Badan Informasi Geospatial, but it was provided to use by Auriga. We asked them to fetch the data and validate it, then upload it to S3.
  • Update frequency: Ad-hoc
  • Last updated: 2023
  • Date received: 2025
  • S3 location: s3://trase-storage/indonesia/spatial/BOUNDARIES/auriga/in/q3_2025/Batas_administrasi_2023.shp

The script that is used to process/clean the dataset.

Various R scripts located in trase/data/indonesia/spatial/boundaries/auriga.

History

  • 2025-09: Dataset received from Auriga, sent to Adelina directly
  • Jason received an earlier file s3://trase-storage/indonesia/spatial/BOUNDARIES/auriga/in/administrative_boundaries_trase.shp. That has different attributes which he used to create the file s3://trase-storage/indonesia/spatial/BOUNDARIES/auriga/out/kabupaten_boundaries_2023.geojson.

{% enddocs %}