Ožbej Bohanec
← Back to projects

Optical Cable Web GIS Platform

Plain-English summary: I built an authenticated Web GIS platform for optical cable planning, map-based editing, and PostGIS-backed operational visibility.

Executive summary

Designed a Web GIS system that combines a Next.js/Leaflet map workspace, FastAPI backend, and PostgreSQL/PostGIS persistence for optical cable infrastructure planning.

PostgreSQL PostGIS SQLAlchemy GeoAlchemy2 Alembic FastAPI Next.js Leaflet

Technical Architecture

Problem

  • Fragmented optical cable planning data needed a map-based workspace instead of disconnected files and manual geometry handling.
  • Inconsistent geometry types and missing auditability of edits.
  • Cable, node, area, institution overlay, and attachment data needed a consistent API-backed persistence path.

What I built

  • Built an authenticated Next.js/Leaflet map workspace for cable and node editing.
  • Connected frontend save/load behavior to FastAPI endpoints and PostGIS-backed persistence.
  • Modeled projects, layers, cables, nodes, areas, attachments, and change history with migration discipline.
  • Kept spatial indexing and geometry consistency as reliability controls for infrastructure planning.

My role

  • I handled full-stack architecture across Next.js, Leaflet, FastAPI, and PostgreSQL/PostGIS.
  • I defined migration strategy and data integrity conventions.
  • I translated operational planning requirements into map editing, API, and persistence workflows.

Constraints

  • Needed to stay compatible with operational workflows and existing planning assets.
  • Had to support long-term maintainability and incremental change without unsafe rewrites.
  • Detailed infrastructure specifics are intentionally kept private.

Outcomes

  • Cleaner planning-to-execution handoff for field and office teams.
  • Higher confidence in reported lengths and area-based summaries.
  • Better foundation for internal Web GIS planning, API-backed editing, and reporting layers.

Architecture decisions

  • Frontend, API, and spatial schema designed as one internal Web GIS system.
  • Audit-ready structures for long-term change tracking.
  • Spatial indexing and geometry consistency as core reliability controls.

Public evidence

This public page documents the system shape, technology choices, and responsibility boundary. No operational map, infrastructure dataset, or private repository is exposed.

Proof limits

The page does not publish cable routes, customer or institution data, active infrastructure, deployment details, or measured business impact. Outcome statements are qualitative.