[TeMPOraL]

I need the inverse of that - an app that predicts how badly a given street will be baked by the sun at current or near-future time, will there be any shadow zone from the buildings, how far will the usable extent of it reach (e.g. not much use of shadow if my head or body stick up beyond the shaded volume). Ideally available on a smartphone. Bonus points for being able to route navigation paths to minimize direct sun exposure.

Motivation: I hate it when it's hot, but my kid has actual issues with heat/sun exposure, and e.g. I had to navigate our way around the city through shaded zones today, just so she doesn't get exhausted in under 30 minutes.

Plenty similar apps are made to sell people photovoltaics, but I'd love to see something to help humans avoid sun.

[abejfehr]

There’s a few sites that do what I think you’re asking for, not navigation though. This is one I’ve used recently: https://shademap.app/

[josters]

This is exactly what I am working on for my city (Berlin). Right now it gives you sun/shade times for outside areas of cafes and restaurants as well as heatmaps for public parks and playgrounds.

The idea is to eventually offer a sun or shadow mode and the app will then surface areas, squares, and streets with more sun or shade and eventually offer walking and biking routes with more or less sun.

[waterproof]

This could also be a legitimate lifesaver in places like India where extreme heat is common but delivery and gig workers have to travel outdoors.

[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...