Small Public Facility Management System

PUBLIC RUNNING SCREENS

Operational screen record

Full entry screen of the Small Public Facility Management System with global search and links to facility, planning, construction, dashboard, and archive workflows. — Unified entry screen · Global search by map, address, facility, or construction name leads into facility management, medium-term planning, construction, statistics, and archive workflows.

Full facility-management screen with a bridge selected from the left list, its geometry and location highlighted on the map, and the detail drawer open on the right. — Facility-management Web GIS · Selecting a facility from the left search list automatically zooms to and highlights its spatial layer while the right drawer presents its ledger, safety-inspection, and medium-term-plan details.

Full statistics dashboard showing facility status, category counts, maintenance status, and a district-level choropleth map. — Statistics dashboard · General, managed, high-risk, and excluded facility counts, category summaries, and annual maintenance status are visualized with charts and a district-level choropleth map.

Overview

This project brings the location, attributes, inspection, and maintenance information of small public facilities into connected map and workflow screens. The intended flow runs from understanding facility conditions to medium-term maintenance plans and construction progress.

Core frontend development

• Menu layouts, loading and selection state, and facility, inspection, maintenance-plan, construction, and compensation workflows built with Vue 3, TypeScript, Vite, and Pinia • WMS/WFS layers, facility-geometry query and editing, zoom and area selection, road view, feature inspection, distance and area measurement, and profile analysis built with OpenLayers 8 and the in-house GIS module • Split-map and swipe comparison plus layer trees, CQL filters, opacity, overview maps, and map-print state • Element Plus input and validation interfaces, Axios API integration, ECharts dashboards, and HWP, Excel, and PDF download flows

Core backend development

• Controller–Service APIs on Java 8 and Spring Boot 2.7, with MyBatis and PostgreSQL persistence for facilities, inspections and risk, medium-term plans, construction, land loss, and compensation • Transactional handling of facility geometry and attribute history, status changes, yearly volume and cost aggregation, dashboards, and composite compensation records • Spring Security and OAuth2 authentication plus user, role, and access-history management, with KRAS, K-Geo, and MapStudio linkage • Excel, HWP, and PDF template output using Apache POI, hwplib, and iText, including image insertion, document merging, and file upload and download APIs

Functions verified in the running screens

• Map navigation tools for overview, zoom, box zoom, view history, and full extent while reviewing an area • Field-context lookup through road view and feature information for a selected location • Distance and area measurement, profile analysis, and reset for spatial review • Horizontal split, swipe comparison, and map settings for comparing and controlling layers • Map print plus facility search and registration by map, address, type, and status • Maintenance-plan specifications, priorities, yearly volume, and cost management • Construction, land-loss, and compensation work screens • Dashboards for facility, maintenance-plan, and risk-facility status • Safety-inspection and risk-assessment report management in the resource library

Scope defined in the requirements

The defined scope covers users, roles, and access history; facility geometry and attribute history; spatial links such as cadastral and land-register data; safety inspection and risk designation; medium-term and implementation plans with form output; emergency, delegation, and civil-service work; and external-system and mobile use. Items requiring further agreement were tracked separately.

Contribution note

As a member of Development Team 2, I developed across the Vue administrative frontend, OpenLayers Web GIS, Spring Boot operational APIs, MyBatis data processing, and administrative-document generation. The technologies and functions are grounded in the supplied source while describing shared team delivery rather than claiming sole implementation.