Digital Land Information Technology Development Project (R&D)
A geospatial R&D platform developed across both frontend and backend, from GeoDCAT catalog-management APIs to RDF documents, QGIS use, and web-map presentation.
- Role
- Jeongdo UIT · Core Area 3 Full-stack frontend/backend development and V&V/demonstration
- Technology
PUBLIC RUNNING SCREENS
Operational screen record
RELATED RECORDS
Linkage with data from other core areas
Core Area 3 · Converged-data integration and operational validation
Core Area 3 aims to resourceize digital land information systematically and establish a stable, scalable integrated testbed. In Jeongdo UIT’s verified scope, catalog, dataset, distribution, and data-service relationships are represented in GeoDCAT/DCAT-family RDF (Turtle); service distributions pair map layers with documents, while file distributions lead to document and download paths. QGIS can open an RDF/DCAT catalog URL, explore dataset and distribution trees, then add a selected distribution as a map layer.
Core Area 1 · Current-position API
Position data is received through a current-position API, stored as the current record by person ID, and transformed into GeoJSON for map visualization with coordinates, floor, and update time. In the Core Area 3 catalog and metadata structure, this type of position service is a linkage target for discovery, description, and map presentation.
Core Area 2 · Tile-work linkage
Tile work groups catalog distribution files into work units for tile-set generation requests and status checks. Metadata such as title, theme, and spatial extent remains with the work, allowing Core Area 3 catalog records to describe the results as distributions for OGC Tile discovery and map-TOC use.
Core Area 4 · Kafka spatial stream
Kafka-topic messages are normalized by a consumer into GeoJSON Features or FeatureCollections and made available as the latest object per topic. Core Area 3 treats this dynamic spatial information as a linkage target in the context of standard metadata, map visualization, and integrated validation.
Program context and participation period
Project records identify Jeongdo UIT as a participating company in the Hyperconnected Digital Land Information work from April through October 2025. According to the public notice from the Ministry of Land, Infrastructure and Transport and the Korea Agency for Infrastructure Technology Advancement, the full national R&D program runs from April 2022 through December 2026. It includes integrated use and operational validation of converged data, along with dynamic geospatial-information construction using fixed and mobile platforms. This card focuses on the implementation and verification scope in which Jeongdo UIT participated.
Core Area 3 scope
Public program material describes Core Area 3 as a framework for non-spatial-information linkage and integrated operational validation. Jeongdo UIT is identified as the implementing organization for the GeoDCAT-based data-catalog service-management technology, covering standards-based data-management modules, catalog and metadata functions, and management-program demonstration. This record covers only that verified implementation and validation scope; it does not claim sole delivery of the research project.
Core frontend development
• Separate search and management state plus list, detail, input, update, and pagination interfaces for catalogs, datasets, distributions, and data services, built with Vue 3, TypeScript, Vite, and Pinia • Element Plus and Axios handling for metadata validation, multipart distribution-file uploads, file lists and downloads, and success, error, and loading states • OpenLayers 8 layer creation for WMS, WFS, OGC Map Tiles, GeoJSON/GML, CityGML, and WebGL points, synchronized with extent movement, styles, visibility, and the TOC • Search, highlighting, content and URL copy for GeoDCAT RDF/Turtle documents, plus service/file distribution branches and QGIS-plugin catalog exploration and layer-addition flows
Core backend development
• Java 17 and Spring Boot 3.4 Controller–Service APIs with MyBatis and PostgreSQL for CRUD, search, pagination, and relationships across catalogs, datasets, distributions, and data services • PostgreSQL JSONB type handlers for spatial and temporal extents, conformance metadata, and map styles, plus multipart distribution files, downloads, and 2D GIS uploads • Apache Jena assembly of DCAT, DCT, FOAF, and ADMS resources and relationships into UTF-8 text/turtle responses • GeoTools GeoTIFF CRS checks, CityGML validation and tile-work linkage, Kafka-message normalization to GeoJSON with per-topic latest state, current-position APIs, QGIS-plugin repository integration, and integrated-testbed V&V support
Publicly described Core Area 3 framework
• Digital-land-information standards: interoperability models and management systems for converged data, plus automated and visible data-pipeline flows • Non-spatial-information linkage: a use direction that assigns location and attributes to non-spatial information such as CAD/BIM, then maps it to digital land information • Integrated testbed: a stable, scalable environment for experiment and validation of core-area results, with national spatial-platform API linkage as its basis
Core Area 3 operational flow
The catalog demonstration shows the path from catalog review and GeoDCAT metadata mapping to RDF/Turtle document confirmation. It presents WMS service distributions with both a map layer and an RDF document, while file distributions follow a document-and-download path. This is a standard-data discovery and presentation demo, not a claim that the browser itself performs RDF generation, indexing, or ETL.
Standard-linkage expressions verified in the demo
• GeoDCAT catalog: RDF (Turtle) metadata at catalog, data-service, dataset, and distribution levels • Map and document: WMS service data is shown with a map overlay and RDF document, while file data is document-first • Spatial-information linkage: OGC API Tiles, TileMatrixSet, OpenAPI, and Conformance information are reviewed in one screen • 2D visualization: the demo presents collection, parsing, coordinate verification, and layer composition for CityGML- and GeoTIFF-family outputs through GeoJSON and OGC tiles
Implementation scope verified in the running screens
• Catalog and metadata: catalog and address tabs, keyword and OGC Tile conditions, and dataset/data-service detail discovery • Service distribution: placing a service confirmed through the catalog on the map and checking its presentation state in the TOC • RDF document: reviewing catalog, dataset, distribution, and data-service relationships in RDF/TTL for document-driven discovery • QGIS use: loading an RDF/DCAT catalog URL, then reviewing the dataset/distribution tree and standard metadata before adding a layer
Installing GeoDCAT Connector from a custom repository
• Open Plugins → Manage and Install Plugins → Settings in QGIS and add a custom repository • Give the repository a recognizable name and use the latest URL shown by the frontend instead of hard-coding it in this record • Confirm that the repository is enabled, turn on the option to show experimental plugins, and search for GeoDCAT Connector under All • Install the result, then verify the Installed tab, plugin menu, toolbar icon, and persistence after a QGIS restart • Verified distribution source: QGIS 3.0 or later, plugin version 0.1.0, experimental release
GeoDCAT Connector workflow
• Load an RDF/DCAT URL returned as Turtle, RDF/XML, or JSON-LD and accumulate catalog, dataset, distribution, and data-service trees in the local database • Narrow resources by title-and-description, title-only, or full-content search plus modified-date, resource-type, and file/link-data filters • Review standard metadata such as title, description, publisher, downloadURL, and packageformat, then open a link or download a file as appropriate • For spatial files, download and recursively unpack ZIP archives, add active formats such as SHP, DXF, and IMG to QGIS, and manage the save path, extensions, and extent movement in Options • For data services, classify endpointURL with conformsTo/format metadata and connect WMS, WFS, or OGC API Tiles layers • The current source defaults downloads and the local database to Documents\GeoDCAT_Connector; only some V-World downloads may require a login session
From requirements to operational functions
Core Area 3’s standard catalog, data pipeline, and map visualization provide a common context for discovering, distributing, and visualizing Core Area 1 position data, Core Area 2 tile-work outputs, and Core Area 4 dynamic spatial information. The linkage shown here explains the data flow from public material and running implementation; it does not expand into a claim that Jeongdo UIT solely implemented every core-area function.
Verification and disclosure boundary
Public program material presents integrated use and operational validation of converged data as part of the hyperconnected digital-land direction. Within that context, this record distinguishes Jeongdo UIT’s platform implementation, V&V, and demonstration participation. Research data, internal addresses, account information, non-public integration specifications, and unverified individual outcomes are excluded.
Public references
The program scope and participation context are based on the following public sources.