Skip to main content

Architecture

Theory​

LuciadFusion consists of:

  • LuciadFusion Platform: the server-side application platform
  • LuciadFusion Studio: the web-based management UI
  • published service endpoints such as WMS, WMTS, WFS, WCS, OGC 3D Tiles, LTS, HSPC, ECWP, File Server, and CSW/catalog APIs.

LuciadFusion is based on the Spring framework and uses YAML profile-based configuration, making it suitable for environment-specific deployment such as development, staging, and production.

LuciadRIA is a browser-side mapping SDK and application stack built around MVC-style concepts such as models, layers, and views. It is used to render data from services like WMS and WFS, and can also be embedded in a custom web application built with webpack/npm-based packaging.

Practical architecture for this CCR​

Recommended architecture

  • Client browser runs LuciadRIA
  • LuciadRIA calls LuciadFusion service endpoints
  • LuciadFusion runs behind reverse proxy / HTTPS
  • LuciadFusion Studio is used by administrators/data managers
  • Backend authentication is handled through Spring Security and enterprise identity integration if required
  • Optional multi-node setup can be used for availability and scale

Example architecture statement for CCR​

LuciadFusion 2026.x will be deployed as the centralized geospatial data and service platform. LuciadFusion Studio will be used for data onboarding, metadata management, product definition, and service publishing. LuciadRIA 2026.x will be used as the browser-based client application for visualization and interaction with LuciadFusion-hosted services such as WMS and WFS. Production deployment will use profile-based YAML configuration, HTTPS, and reverse proxy integration.