Wiki-Editable Cycling Navigation Where Riders Can Flag And Permanently Reroute Around Road Segments They Know Are Dangerous

mobile app real project • single request

Cyclists say bike-navigation apps route them onto roads locals know are death traps, with no way to correct it: you can see the bad route but you can't tell the app to never send anyone down that segment again. Existing community features add scenic points of interest, not safety corrections to the routing engine itself. The opportunity is OpenStreetMap-style routing where riders edit segment safety wiki-style and those edits reshape everyone's routes.

builder note

The trap is cold-start: a safety wiki with zero edits routes exactly like plain OSM and gives riders no reason to return. Seed it by importing BikeMaps.org crash data and municipal bike-incident open data for one city, so the map is already useful on day one, then let rider edits accrete on top.

landscape (4 existing solutions)

Cycling apps either show static danger icons or additive scenic POIs; none treat rider-submitted segment safety as editable data that actually changes the routes other people get.

Komoot Community Highlights are additive scenic POIs and surface notes; they don't let a rider down-rank or blacklist a dangerous segment inside the routing engine.

Ride with GPS Community Highlights surface local services and POIs, not hazard corrections, and routing stays heuristic with no rider-sourced safety layer.

Cyclers Shows danger warnings along a route, but they are read-only data; riders can't add, correct, or override them.

BikeMaps.org Collects crash and hazard reports as research data but is not a routing app, so the rider-sourced safety knowledge never reaches anyone mid-trip.

sources (1)

hn https://news.ycombinator.com/item?id=45509339 "no way to correct a route because one stretch is a death trap" 2025-10-09

cyclingnavigationopenstreetmapcrowdsourcedsafety