GIS & planning · 2022–2026

FloriPlan

GIS-based operational planning: maps, objects, plans and a mobile companion.

Back to all projects
Role
Vue 3 migration & GIS
Timeframe
2022–2026
Context
Product team · five main developers
Technologies
Vue 3PrimeVueOpenLayersNode.jsExpressGraphQLRESTSocket.IOSequelizePostgreSQLPuppeteerHandlebarsGhostscriptFlutterMyEvoSysDockerPM2Bitbucket Pipelines

FloriPlan digitises operational planning: capture objects, maintain maps, create plans and make them available in the field. I have helped shape the web platform since 2022 and the mobile app since 2023: 1,770 of 7,850 web commits are mine, making me the second-largest contributor. I led the migration from Vue 2/Vuetify/Leaflet to Vue 3/PrimeVue/OpenLayers and substantially extended the map editor, water-infrastructure planning and cantonal PDF output. On the app I am lead contributor with 189 of 332 commits.

01

Context

Operational planning was often fragmented: maps, addresses, object information and documents lived in different tools.

FloriPlan brings this information into one shared, map-based application — for planning, preparation and response.

02

My contribution

  • Led the migration from Vue 2/Vuetify/Leaflet to Vue 3/PrimeVue/OpenLayers — including the planning wizard and map editor, without interrupting ongoing product development.
  • Substantially extended the OpenLayers map editor: drawing and editing text, lines, routes, polygons, circles, freehand shapes and icons, route arrows, image overlays, SwissTopo search and OSM building import.
  • Implemented water-infrastructure planning with hydrants, pumps and pipe sections, pressure-loss calculation, versions and PDF output.
  • Helped build 45 print layouts across four layout families and the server-side PDF pipeline with Puppeteer/Handlebars for the layouts plus Ghostscript for PDF import and editing; extended the data model, 188 migration files on master and tenant-specific configurations.
  • Shaped the FloriPlan app as lead contributor: map layers via FloriPlan proxy, QR-code and deep-link entry, cross-organisation access switching and PDF/photo viewer.
  • Localised the FloriPlan app into five languages (DE/EN/FR/IT/RO), maintained releases and helped shape the deliberately read-only proxy access to maps, plans and documents.
03

Architecture & delivery

  • npm workspaces monorepo with packages/, client/, server/ and share/; modular client with eight modules and server with 17 modules.
  • Vue 3, PrimeVue and OpenLayers on the frontend; Node.js, Express and a GraphQL-first API with REST endpoints for the app and sharing.
  • Sequelize/PostgreSQL with 76 models, 368 migrations and 103 seeders; tenant-specific cantonal configurations.
  • Server-side PDF and print pipeline: 45 HTML layouts across four layout families, Puppeteer/Handlebars for the layouts, Ghostscript for PDF import and editing, and PDF merging.
  • MyEvoSys SSO, Socket.IO cluster, PM2 and S3/MinIO; a deliberately reduced, read-only Flutter companion using FloriPlan proxy endpoints.
System design From map to plan
Sources
Map & planning
Access & companion
Data & export
GIS sources SwissTopo · OSM · WMS
OpenLayers map editor
Plan wizard objects · water
API GraphQL · REST
PDF pipeline 45 layouts
FloriPlan App read-only proxy
MyEvoSys SSO OIDC
PostgreSQL 76 models
S3 / MinIO files
WMS / XYZ Puppeteer PDF Proxy OIDC

OpenLayers carries the map editor and planning, the plan wizard creates objects and water transports, and the PDF pipeline renders printable operational plans. The FloriPlan app reads the same state through a deliberately read-only proxy.

Design decisions
  • OpenLayers as the shared map foundation for editor, planning and app proxy.
  • 45 print layouts across four layout families, rendered with Puppeteer and Handlebars.
  • The app only reads through proxy endpoints and cannot modify plans.

Scroll horizontally to see the full design.

04

The hard parts

01

Migration without downtime

Move a mature Vue 2 application with Vuetify and Leaflet to Vue 3, PrimeVue and OpenLayers while planning workflows remain in production. The migration had to happen incrementally without losing data or interaction logic.

02

Maps are not tables

OpenLayers interactions, WMS/WMTS/XYZ layers, geometries and coordinates must work together with the data model and permissions. A click on the map is a data access, not just a visual detail.

03

One plan, many cantons

Cantonal requirements produce 45 print layouts across four layout families. The same planning data must be reproducible, to scale and in the expected form as PDF or print.

05

Outcome

  • Migrated the web platform from Vue 2 to Vue 3 and continued with PrimeVue and OpenLayers.
  • The map editor covers drawing, routes, image overlays and OSM building import — backed by permissions and the data model.
  • Water-infrastructure planning with pressure loss, versions and cantonal PDF output in production.
  • A mobile companion for maps, objects and documents; 189 of 332 app commits are mine.

Contact

Let's talk about the next role.

I am looking for a position where I can take responsibility for systems and teams as a tech lead, software architect or senior full-stack engineer. Ideally where reliability, data and real-world workflows meet.