GSoC 2025 Midterm Update: Temporary Road Closures Database and API

Project Overview

I’m excited to share the midterm progress on my Google Summer of Code 2025 project: Temporary Road Closures Database and API for OpenStreetMap. This project aims to create a centralized platform where users can submit and retrieve real-time information about temporary road closures, enabling OSM-based navigation apps to provide better routing around construction, accidents, and other events.

• Mentor: Simon Poole and Ian Wagner
• Organization: OpenStreetMap
• Project Duration: 12 weeks (175 hours)

🎉 Midterm Evaluation Status: PASSED

I’m thrilled to announce that I’ve successfully passed the midterm evaluation! The project is progressing well and is currently on schedule with several components ahead of the original timeline.

Progress Summary

Completed Components (Weeks 1-8)

1. Geospatial Database & Core Infrastructure

• PostgreSQL + PostGIS setup with Docker containerization
• SQLAlchemy models for Users and Closures with spatial geometry support
• Database initialization scripts and sample data loading
• PostGIS spatial indexing for efficient geospatial queries

2. RESTful API Service (FastAPI)

• Complete CRUD operations for road closures
• Spatial query endpoints supporting bounding box and coordinate-based filtering
• Authentication & Authorization with JWT tokens and OAuth2
• Input validation and error handling
• Swagger UI documentation with integrated authentication

3. OpenLR Integration

• OpenLR encoding/decoding service integrated into the API
• Location referencing endpoints for map-agnostic road segment encoding
• Validation endpoints for OpenLR data integrity
• Closure service enhancement with automatic OpenLR generation

4. DevOps & Infrastructure

• Docker containerization for easy deployment
• Environment configuration management
• AGPL-3.0 licensing for open-source compliance
• Comprehensive documentation and setup instructions

Currently In Progress (Weeks 9-10)

Web UI Development

• Next.js frontend application setup and configuration
• Interactive map component using Leaflet.js with OSM tiles
• User authentication pages (login/register) with backend integration
• Closure submission forms with step-by-step modal interface
• Real-time closure visualization on the map
• Responsive layout components and navigation

Technical Achievements

Backend Architecture

🏗️ FastAPI + PostgreSQL/PostGIS + OpenLR

├── 🔐 JWT Authentication & OAuth2

├── 🗺️ Spatial queries with PostGIS

├── 📍 OpenLR location referencing

├── 🐳 Docker containerization

└── 📚 Auto-generated API documentation

Key Features Implemented

• Spatial Querying: Efficient bounding box and coordinate-based closure retrieval
• OpenLR Compliance: Industry-standard location referencing for cross-platform compatibility
• Security: JWT-based authentication with password hashing and token validation
• Scalability: Dockerized deployment with proper database indexing
• Documentation: Comprehensive API documentation with interactive Swagger UI

Frontend Progress

• Modern Stack: Next.js + React + TypeScript + Tailwind CSS
• Interactive Maps: Leaflet.js integration for closure visualization
• User Experience: Intuitive forms and responsive design
• State Management: React Context for closure and authentication state

Metrics & Performance

• API Endpoints: 15+ fully functional endpoints
• Database Schema: Optimized with spatial indexing
• Test Coverage: Core business logic tested
• Docker Build: < 30 seconds deployment time
• API Response: Sub-100ms for spatial queries

Next Steps (Weeks 11-15)

Immediate Priorities

1. Complete Web UI (Week 10)
   • Finalize closure submission workflow
   • Implement real-time closure updates
   • Add user dashboard and closure management
2. OsmAnd / Valhalla Integration (Weeks 11-12)
   • Research Valhalla API plugin
   • Implement closure data consumption in Valhalla
   • Create prototype navigation with closure-aware routing
3. Testing & Optimization (Weeks 13-14)
   • End-to-end testing and performance optimization
   • Documentation finalization
   • Community feedback integration

Challenges & Solutions

Challenge: OpenLR Integration Complexity

Solution: Successfully integrated the openlr-python library with custom validation logic for OSM data compatibility.

Challenge: Spatial Query Optimization

Solution: Implemented PostGIS spatial indexing and optimized SQL queries for sub-100ms response times.

Challenge: Authentication Architecture

Solution: Built a robust JWT-based system with refresh tokens and proper security middleware.

Community Engagement

• Regular mentor sync-ups with Simon Poole (OpenStreetMap) and Ian Wagner (Stadia Maps)
• Active GitHub development with 80+ commits
• OSM community feedback on project direction
• Documentation-first approach for future contributors

Repository & Demo

• GitHub Repository: OSM Temporary Road Closures
• API Documentation: Available via Swagger UI
• Live Demo: Coming soon with frontend completion

Reflection

The first half of GSoC has been incredibly rewarding! I’ve successfully built a robust backend infrastructure that exceeds the initial requirements. The integration of OpenLR was particularly challenging but rewarding, as it ensures our platform can work seamlessly with any OSM-based navigation system.

The project is well-positioned for the second half, where I’ll focus on user experience through the web interface and real-world validation through OsmAnd or Valhalla integration. I’m excited to see this system help the OSM community navigate around road closures more effectively!

Special thanks to my mentors for their guidance and the OSM community for their support and feedback.