Parkwarn München

live
|Started Oct 2026|Updated Oct 2026

A map-based web app that warns Munich residents about upcoming temporary parking bans and construction near their parked car — built on the city's open data and OpenStreetMap, no account needed yet.

ViteTypeScriptLeafletNetlifyOpenStreetMapClaude Code
parkingmunichmapscivic datafounder
Screenshot of Parkwarn München

What it’s about

Munich publishes temporary parking bans and construction zones as open data, but there’s no good way for residents to know when a ban is about to hit their street until it’s too late — meaning a towed or fined car. Parkwarn München puts that data on a map: set a location and radius, see what’s coming up over the next 7–30 days. The functional idea is borrowed from “Parkwache Ulm”, a similar project for a different city — design and implementation are built from scratch.

Approach

It’s a rapid-prototyping project in the truest sense: idea to live deployment took no more than three hours. Stack: Vite + TypeScript + Leaflet, OpenStreetMap tiles, a Netlify Function proxying Munich’s open “Baustellen” dataset. No backend, no accounts, no personal data — location, radius and time window are chosen in the browser and matched against the dataset, classified by how likely they actually affect parking. Address search runs through Photon (OpenStreetMap-based). Bilingual UI (DE/EN), dark/light mode, and SEO/GEO basics (sitemap, JSON-LD, robots, llms.txt) are in from the start. The only tracking is minimal, anonymized and cookieless, through a self-hosted Matomo instance — just enough to see whether the idea gets used at all, as a signal for whether it’s worth building further.

What’s next

Notifications are the priority: email and web push for saved locations. That means a real backend (Supabase, EU region) to store opt-ins and run a daily scheduler, plus picking an EU email provider and a proper legal review of the privacy policy before any of that ships.

Learnings

  • working with messy municipal open data: no stable IDs, inconsistent fields, dates without times
  • building a notification product means the backend and legal work start before the first feature ships, not after
  • reusing someone else’s product idea (Parkwache Ulm) while building the implementation independently