ID — Bahasa Indonesia

Muhamad Irga

Purwokerto, Central Java

Updated

WebGIS Desa — Village Spatial Data Platform

A WebGIS for villages and districts: boundaries down to hamlet, RW, and RT, roads, contours, flood hazard, land cover, PTSL parcels, and monuments, with KMZ import and embeddable maps per village code.

See the service: Village Information Systems

Screenshots

WebGIS map of Cilacap with the Sikampuh village boundary on satellite imagery and the district and village area list
Main application view · Open image for full resolution
Layer browser listing boundaries, roads, contours, and hazard layers
Application view 2 · Open image for full resolution
Area management with KMZ import per village
Application view 3 · Open image for full resolution
Public landing page of the regional GIS
Application view 4 · Open image for full resolution

Overview

What this system does.

WebGIS Desa gathers a region’s spatial data in one place. Administrative boundaries go down from the village to the hamlet, RW, and RT, and are joined by roads, topographic contours, flood hazard zones, land cover, PTSL land parcels, and monuments.

Operators import KMZ files per area and can remove a whole area’s import in one step. Each village code gets an embeddable map and an embeddable import page, so the same data can appear inside a village website. A layer browser, spatial maps per district and village, area types, role and permission management, and an activity log round out the administration side.

The application is built with Laravel 11, Livewire 3 with Volt, PostGIS, and OpenLayers, with GeoServer publishing layers. It is a Pustekno team project where I contributed alongside the lead developer.

Feature inventory

Highlights

11 capabilities verified against the project source.

  • Boundaries for village, hamlet, RW, and RT
  • Road, contour, flood hazard, land cover, PTSL, and monument layers
  • KMZ import per area
  • Bulk delete of an area’s imported data
  • Embeddable map per village code
  • Embeddable import page per village code
  • Layer browser
  • Spatial maps per district and village
  • Area type management
  • Role and permission management
  • Activity log

Tech stack

Built with 10 technologies.

  • Laravel 11
  • Livewire 3
  • Volt
  • PostgreSQL
  • PostGIS
  • OpenLayers
  • GeoServer
  • Spatie Permission
  • Tailwind CSS
  • Alpine.js

Common questions

What people usually ask.

Where does the spatial data come from?

Operators import KMZ files prepared in desktop GIS tools; the application stores them in PostGIS and publishes them as layers.

Can a village website show the map?

Yes. Each village code has an embeddable map, so a village website can include its own boundaries and layers without copying data.

Why PostGIS?

Spatial queries such as which RT a point falls into or how areas overlap run inside the database, which keeps the application simple and fast.

Same field

Need something like this?

Send a short brief and I’ll come back with scope, approach, and an honest timeline.