Releases: J-e-i/SafePath
v0.1.0 Initial Release
#Summary
Initial public version of SafePath: crime-aware routing for Chicago with safety-optimized alternative paths.
##Features
Direct vs optimized routing (avoids crime proximity buffers)
Crime data fetch (last 1000 incidents; filtered types)
Dynamic map with markers and route overlay
Automatic risk-buffer generation using Turf.js (union of incident buffers)
Address geocoding (start & destination)
Avoidance polygon routing (OpenRouteService)
Basic UI: route form + map display
##Tech Stack
Next.js (App Router),
React,
TypeScript,
Leaflet / react-leaflet,
Turf.js, Tailwind CSS,
Axios.
##External Data / APIs
Chicago Crime Data (Socrata)
Nominatim (OpenStreetMap) for geocoding
OpenRouteService (directions)
OSM raster tiles
Security / Notes
OpenRouteService key currently hard‑coded (needs server proxy + env var later)
No caching or rate-limit handling yet
No authentication or user persistence
Known Issues / Limitations
Geocoding done client-side (rate limit risk)
API key exposed in client bundle
No error UI (failures logged only)
Route optimization simplistic (uniform buffer radius)
Lacks accessibility review
Planned (Roadmap)
Secure server API for routing + geocode proxy
Adjustable safety sensitivity (buffer radius weighting)
Risk heatmap layer
Incident type weighting model
Caching & retry logic
User accounts + saved routes
Mobile layout improvements
##Tag
v0.1.0