Record · Verify · Map road crashes
CrashMap Rwanda
A road-crash record and map for Rwanda: police record and verify crashes, analysts find the places where they cluster, and the public sees a map with personal details removed.
Building this now. Nobody is using it for real yet. First customers help shape it and get founding pricing.
The problem
What this is actually for
Crash records sit on paper forms and in spreadsheets, so nobody can see that the same junction keeps appearing.
Crash data is shared by emailing a file, and afterwards nobody knows who holds a copy of whose personal details.
Someone who witnesses a crash has no way to report it that reaches the right police unit.
Each unit reports differently, so a drop in crashes and a drop in reporting look the same.
Who it is for
- Traffic police units and supervisors
- Road-safety and road-authority analysts
- Researchers
- Members of the public reporting a crash
- Built for
- Rwanda
- Runs on
- Web, Android
See it
Shown running, on invented data
This holds people’s personal details, so the public half of it stays offline until it can go live for real. On a call we show the running system on synthetic crashes, and every screen carries a banner saying the data is invented.
What we would show you
- The public map, and the signed-in map with exact locations and filters
- The statistics dashboard, and reporting performance per police unit
- A public crash notification being verified, merged with a duplicate, and logged
- An export, and the record it leaves of who took it
- The same crash layer opened in QGIS
Test data throughout. Nothing we show you is a real customer’s record.
Where it stands
What is built, and what is not
The left column exists and we can show it to you running. The right does not exist yet.
Built
- A public crash map with personal details removed, and a signed-in map with exact locations and full filters
- A statistics dashboard: trends, the sectors with the most crashes, where they concentrate, and reporting per police unit
- Search and export to CSV, Excel and GeoJSON, with every export logged against the person who made it
- Search by number plate, through an audited lookup
- Crash notifications from the public, routed by district to be verified, marked as duplicates or merged — switched off until officers are monitoring them
- Printable reports, admin screens and in-app alerts
- Roles enforced in the database itself, not only in the app
- A standard map feed (OGC API Features) that QGIS and ArcGIS open directly
Not built yet
- The officer app for recording a crash at the scene. Offline storage is built; the form, location, photos, vehicles and people are not
- The crash report form itself, which stays a draft until the police confirm it
- Kinyarwanda, from a professional translator, and a reviewed French translation. English is the only finished language
- Email, SMS and push alerts
- Connections to police, road-authority and hospital systems
- A live deployment with real data. Everything today is synthetic
The order these get built in is not fixed. It is one of the things a first customer gets a say in.
Be one of the first to use it
CrashMap Rwanda is not finished, and we are not going to pretend otherwise. What early customers get is real influence over what gets built and in what order, founding pricing that we will not raise on you, and us on the end of a phone. What we get is someone telling us where it is wrong.
Not this one? The other six — or tell us what you actually need.