Scope
Designed a normalized GIS data model covering projects, layers, cable segments, splice nodes, zones, attachments, and audit trails. Built migration-safe schemas for long-term operations and incremental change.
Fiber / Optical Cable GIS Database
Plain-English summary: I built a structured GIS/PostGIS database foundation for fiber planning, technical auditing, and operational reporting workflows.
Project Visuals
Technical Architecture
Problem/Context
- Fragmented optical planning data across spreadsheets and ad hoc files.
- Inconsistent geometry types and missing auditability of edits.
- No reliable way to synchronize derived cable length metrics.
What I Built
- Defined constrained geometry columns with explicit SRID handling.
- Added GIST indexing strategy for spatial lookup and map operations.
- Implemented migration/version discipline with Alembic revision flow.
- Introduced automated cable-length synchronization path to reduce manual drift.
Responsibilities
- I handled data modeling and geospatial schema structure design.
- I defined migration strategy and data integrity conventions.
- I translated operational planning requirements into a maintainable persistence layer.
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.
Outcome/Value
- Cleaner planning-to-execution handoff for field and office teams.
- Higher confidence in reported lengths and area-based summaries.
- Better foundation for future API/reporting layers.
System Concepts
- Schema built to be consumed by service/API layers without re-modeling.
- Audit-ready structures for long-term change tracking.
- Spatial indexing and geometry consistency as core reliability controls.