● high ● elevated ● moderate (off by default)
● live data
Data sources & how areas are defined
Neighbourhood polygons — for the Chicago/NW-Indiana corridor, areas are drawn at neighbourhood
scale (Gary Midtown, Tolleston, Glen Park, Downtown Hammond, Indiana Harbor …) rather than whole city
limits, so a whole city is never written off. These outlines are approximate and hand-placed from
published neighbourhood-level crime reporting — edit or delete any of them.
Live incident data — Chicago publishes incident-level crime with coordinates. When a trip touches
Chicago the app pulls recent violent-crime points and marks only the grid cells that actually cluster.
That's real block-level data, not an estimate. No equivalent open feed exists for Gary or Hammond.
Road classes — motorway/trunk geometry comes from OpenStreetMap so the app can tell an interstate
pass-through from surface-street routing.
City-level circles — the national top-10 entries are still coarse radius markers from FBI-based
rankings; they exist as a backstop for trips outside the detailed corridor.
Optional: OpenRouteService key
Avoidance works with no key. A free
ORS key
adds exact in-engine avoidance, but its limits are tight (zones ≤200 km²/20 km, trips ≤150 km).
Crime data is historical and incomplete; areas vary street to street and change over time. This is a personal
planning aid, not a safety guarantee, and not a judgement about the people who live anywhere. Always use your
own judgement about a route before driving it.
Click to place corners · double-click or press Enter to finish · Esc to cancel