[TeMPOraL]

Update: I just vibe coded myself one, gave me an excuse to play with Antigravity (and then cleaned up/improved with Claude Code). Not posting a link yet because it serves 12MB worth of geo JSON up to the client on first page load, and I'm not eager to wake up tomorrow with a bill for upload traffic spike. But it pretty much does its job as well as it could given quality of available data (OSM), so now I'm looking at improving the data itself.

It currently runs A* for routing between two points on map (no address lookups yet), using either local A* or an OSMR endpoint for base path, and then A* for shadow-aware routing, and shows both, + stats (total time exposed, how much it saves in sunlight exposure and loses in time relative to base), plus has a bunch of debugging overlays so I can validate and diagnose pathfinding and data quality. But I tested it live today, and it mostly checks out with reality (big gap: no data on trees).

[ben_w]

If you hadn't already, I would have suggested vibe coding this.

I've done a different thing also with OSM data (isochrone rather than point-to-point routing) and put it on github to avoid needing to care about bandwidth on my domain, because also around ten megabytes for Berlin's data, despite having a step to convert JSON to a much more compact form with only the data I needed:

https://github.com/BenWheatley/Isochrone

https://benwheatley.github.io/Isochrone/web/?region=berlin&n...